Skip to content

Occitan: Corrections udhr_lnc.xml#141

Open
Mejans wants to merge 1 commit into
eric-muller:mainfrom
Mejans:patch-1
Open

Occitan: Corrections udhr_lnc.xml#141
Mejans wants to merge 1 commit into
eric-muller:mainfrom
Mejans:patch-1

Conversation

@Mejans
Copy link
Copy Markdown

@Mejans Mejans commented Jan 5, 2026

Some corrections and improvements
Note that the subtag for languedocien Occitan is lengadoc, thus oc_lengadoc.
For Auvergnat it's auvern
For Provençal it's provenc
Source: https://www.iana.org/assignments/language-subtag-registry/language-subtag-registry

Some corrections and improvements
@eric-muller
Copy link
Copy Markdown
Owner

Thanks a lot for you help. I have no competency in Occitan (other than being a native French speaker), so please bear with me.

There is room for multiple translations in the "same" language, and we already have a few cases of that. The line I am trying to draw is this: if there is an obvious typo, then it's fine to fix it; if it is a matter of style, or a more modern way of saying something, then it's a different translation. Of course, they are gray areas. May be a way to ask the question is: would the original translator agree that there is typo? I prefer to err on the side of new translation, if only out of respect for the original translation (and to avoid purists' battles...)

Also bear in mind that the file identifiers (auv, lnc, prv) were inherited from the OHCHR work, and that their labeling is sometime misleading. For all I know, our [lnc] translation may actually be Gascon or Limousin, or even something that does not have a BCP47 subtag.

With that in mind, how would you characterize your changes?

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants