Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Definition of modal verbs in IETF RFC 2119 (developer_guide.md) #100

Closed
apertamono opened this issue Aug 16, 2018 · 3 comments
Closed

Definition of modal verbs in IETF RFC 2119 (developer_guide.md) #100

apertamono opened this issue Aug 16, 2018 · 3 comments

Comments

@apertamono
Copy link

This one sentence in the Code of Conduct is a challenge for translators:

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

That's RFC 2119 of the Internet Engineering Task Force.

The most important purpose of RFC 2119 is to specify that rules containing the words MUST, SHALL or REQUIRED are compulsory, while rules containing the words SHOULD or RECOMMENDED can be ignored when there are valid reasons to make an exception.

Our German translation refers to an unofficial German translation of RFC 2119. That's a reasonable solution if one is available, but I'd prefer a different solution: the translation should define which words in the translation are equivalent to MUST/SHALL etc. in RFC 2119.

Other existing translations are suboptimal. The French version simply translates the text literally. The Russian text keeps the capitalized words in English, which is correct but not useful. The Italian translation invites the reader to compare the English source text to RFC 2119. And in the Spanish translation of contributing.md, the word 'no' appears:

no deben ser interpretadas como esta descrito en el RFC 2119

Based on my passive knowledge of the language of Cervantes, I conclude that this means the opposite of the source text. And esta should be spelled está, by the way.

I propose that existing translations are updated during or after updates.

@apertamono
Copy link
Author

apertamono commented Aug 16, 2018

For example, the type of localization I'm proposing is the following text for French (not sure about the Dutch translation for 'should' yet):

Les mots clé "DOIT", "EXIGE" et "DEVRA", dans le présent document sont à interpréter comme "MUST" dans la RFC 2119, "NE DOIT PAS" et "NE DEVRA PAS" comme "MUST NOT", "DEVRAIT" et "RECOMMANDÉ" comme "SHOULD", "NE DEVRAIT PAS" comme "SHOULD NOT" et "PEUT" et "FACULTATIF" comme "MAY".

There are only five categories in RFC 2119, so not all synonyms need to be mentioned in English. And of course, we MUST translate these terms consistently in the rest of the Code of Conduct.

I couldn't translate a whole page to French, but it looks like the existing translations DEVRAIT for SHALL and DEVRA for SHOULD are the wrong way around. And in Danish, SKAL is used for both SHALL and SHOULD, so that the reader doesn't see the difference between obligatory rules and recommendations. There's a reason why these terms are defined. Could you please check your translations?

Paging translators: @erciccione @el00ruobuob @cryptobench @monerorus @ordtrogen @rodolfo912 @woodyjon @cryptochangements34

@Josexv1
Copy link
Contributor

Josexv1 commented Aug 17, 2018

About the Spanish translation, there's a PR with the fixed words. I'm trying to get it finish ASAP.

@anonimal
Copy link
Collaborator

anonimal commented Sep 7, 2018

NOTICE: THIS ISSUE HAS BEEN MOVED TO GitLab. Please continue the discussion there. See #102 for details.

@anonimal anonimal closed this as completed Sep 7, 2018
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

No branches or pull requests

3 participants