This was most likely done intentionally to prevent translation. It's not necessarily right, though.

@zero-24

Correct this is expected behavior at this place.

So why have one way with hyphens and one without? Surely stick to one way or the other even if it’s not going to be translated?

So why have one way with hyphens and one without? Surely stick to one way or the other even if it’s not going to be translated?

Sorry i can not follow you?

The text on the TAB and the text on the fieldset both have hyphens

The text on the field doesnt have hyphens

Yes because the texts on the fieldset comes from the XML file and the seccond one from a language string? The ?? vs. ** is just showing when language debug is enabled right?

yes language debug is enabled in that screenshot

I guess you need to choose one - and all three should be the same. It makes no sense to have 2 with hyphens and one not.

yes language debug is enabled in that screenshot

Yes that is the reason ;) Please disable language debug and check again.

The ?? vs ** comes from whether that string is comming from the XML or via language string and is only showed in language debug.

Yes that is the reason

No its not.

You dont seem to understand.

Im not concerned now about ?? or **

The Tab is Content-Security-Policy (CSP) with Hyphens - between the words
The fieldset is Content-Security-Policy (CSP) with Hyphens - between the words
The field label is Content Security Policy (CSP) with Spaces between the words

They should all be the same, either with or without spaces, either with or without Hyphens -

Ah ok sorry so it is good that i have asked. Can you give us the suggestion form a native speaker what to choose best here?

As a title it has no hyphen https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP

As a response header it has a hyphen https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy

So in this case none of the strings highlighted by Phil should be hyphenated.

RFC7762 uses spaces "Content Security Policy" throughout when using the term in sentences and titles.

"Content-Security-Policy" is the name of the HTTP Header (with hyphens)

Therefore in all places referring to "Content Security Policy" in text, spaces should be used, except if talking specifically about the header values.

lol we wrote the same thing at the same time

With this being the case though, I dont see why "Content Security Policy" (with spaces) used in text cannot and should not be translated, as its just a sentence... Im no language expert, but Im guessing other languages refer to it in their own language?

as a header value, with hyphens - it should not be translated.

For example - Spanish = "Política de seguridad de contenido" is used at https://developer.mozilla.org/es/docs/Web/Security/CSP/Introducing_Content_Security_Policy

I forgot - The hyphenation comes from when all the headers were defined in the plugin

The thinking was that these were not regular labels that were descriptive and therefore translatable but that they were the specific response headers.

So maybe the strings in the global config (my screenshots) should be translated and the strings used in the HTTP Headers plugin should be left as they are, untranslated and with hyphens.

unless the component option field refers to the response header eg the same as x-frame-options in which case that should have the hyphens added. (not at computer to check code)

but 100% agree the tab and field group should not have the hyphen

Correct - at all times, except when directly referring to the exact header, the "Content Security Policy" (with spaces) should be used and should be translatable.

So maybe the strings in the global config (my screenshots) should be translated and the strings used in the HTTP Headers plugin should be left as they are, untranslated and with hyphens.

Ok great can you send a PR to fix it?

Correct - at all times, except when directly referring to the exact header, the "Content Security Policy" (with spaces) should be used and should be translatable.

I personaly dont agree that this technical term should be translated but i will let the native speaker decide on that.

The help page just makes it worse - so inconsistent in its use of spaces and hyphen versions

https://help.joomla.org/proxy?keyref=Help40:Components_CSP_Reports_Options&lang=es

The same conversation can be had over this screenshot now.. :-( :-(

I wouldnt translate them either

ok so lets not translate them (until someone else asks) but at least lets use the spaces and not the hyphen versions of these ...

I cannot speak for non-English speakers - Im English I speak one language badly.

Having googled though I see a lot of results and articles for "Política de seguridad de contenido" so I assume that some (Spanish) people know the feature by that ...

maybe invite some more non-english (technical people) speakers to comment here ?

The help page just makes it worse - so inconsistent in its use of spaces and hyphen versions

https://help.joomla.org/proxy?keyref=Help40:Components_CSP_Reports_Options&lang=es

Well as this page is written by an non native speaker (me) feel free to correct it this is what the wiki is about.

The same conversation can be had over this screenshot now.. :-( :-(

Sure and the same applies ;) please choose the correct english term and send a PR to correct it.

See in French here:
It can be translatable as long imho as we add (CSP) after the translation.
“Stratégie de sécurité du contenu (CSP)”

haha that makes it more confusing for my poor head :)

Stratégie de sécurité du contenu = SSC :-)

ok so lets not translate them (until someone else asks) but at least lets use the spaces and not the hyphen versions of these ...

I cannot speak for non-English speakers - Im English I speak one language badly.

Having googled though I see a lot of results and articles for "Política de seguridad de contenido" so I assume that some (Spanish) people know the feature by that ...

maybe invite some more non-english (technical people) speakers to comment here ?

Well my personal opinion is that we should not translate it for one simple reason. It is an technical term that does not change. When you go and try to set „inhalts-sichereheits-richtlinie“ via htaccess it does not work right? Also all docs i saw until now only mention the correct technical term so to me it does not make sense translate it other than confusing people maybe thats just me?

Using the string with or without - is in my opinion up to the english native speaker to decide so please choose and send a PR so we use the correct term.

CSP is the accepted technical short, and yes, it is based on the English term.

See in French here:

It can be translatable as long imho as we add (CSP) after the translation.

“Stratégie de sécurité du contenu (CSP)”

As mention even in the language file comments i personally would not recommend to translate it as it is a technical term.

https://developer.mozilla.org/fr/docs/Web/HTTP/CSP

There are two things.

1. The technical header name - this MUST NOT be translated and is always hyphenated. This is used when referring directly to the name of the header output in the response.

2. When you talk about that header, as a subject of a conversation, in a paragraph or as a heading, then its not a "technical term", its the name of the concept, you are discussing the topic, and its title should be translated and with space.

Simple.

This describes exactly my point:

Exactly!

Ok feel free to send a PR than.

Closing as we have PR
#29768

Reopening as #29768 is closed.

Closing as the general consensus is that no one wants this translated.

Should't we do the unification with or without - for the options screen as mention above? Or has this been canceled too?