QA escapes: FR translation + minor changes to EN #446
Conversation
✅ Deploy Preview for i18n-drafts ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
|
@clavoline thank you very much for useful edits to the english ! I haven't looked at the French yet because the netlify link didn't work. @xfq is it possible to fix that? (If not, i'll install the text in a local file to check it.) |
|
@clavoline i have now looked at the French translation and it looks good, with one caveat: near the beginning you translated the Unicode name for a character, U+00A0 ESPACE INSÉCABLE. It's normal to leave the uppercase name exactly as it appears in the standard, however, i know that there is a French version of the Unicode Standard which does have translated character names (and by memory i think you have the right name). Therefore this may not be a problem. I just wanted to check with you that you were aware. Just let me know, and if you want to keep it as is then i'll merge and announce the translation. |
|
Thank you Richard, that's a good question.
Is this the French version of the Unicode Standard you were referring to: http://hapax.qc.ca/Tableaux-15.0.htm?
Note: there are two more Unicode character names in the text, which I translated as well ("U+200F MARQUE DROITE-À-GAUCHE" and "U+3123 LETTRE BOPOMOFO EN"). The names match the recommendations from the Hapax website.
I went through every French article I could find on Google with "site:https://www.w3.org/International/questions" and only one article included Unicode character names: https://www.w3.org/International/questions/qa-html-css-normalization.fr.html
In this article, the names have been translated as "U+00E1 Lettre minuscule latine A accent aigu", "U+0061 Lettre minuscule latine A" and "U+0301 Diacritique accent aigu". These names match the recommendations from the Hapax website.
Do you know whether Unicode character names appear in other French translations?
Based on that translation, for consistency purposes, it would make sense to use the French names (but follow French capitalization rules). However, if you'd rather use the English names (and add a French translation or explanation for each of them), I don't mind.
Thank you,
Gwen
------- Original Message -------
…On Wednesday, February 15th, 2023 at 15:55, r12a ***@***.***> wrote:
***@***.***(https://github.com/clavoline) i have now looked at the French translation and it looks good, with one caveat: near the beginning you translated the Unicode name for a character, U+00A0 ESPACE INSÉCABLE. It's normal to leave the uppercase name exactly as it appears in the standard, however, i know that there is a French version of the Unicode Standard which does have translated character names (and by memory i think you have the right name). Therefore this may not be a problem. I just wanted to check with you that you were aware. Just let me know, and if you want to keep it as is then i'll merge and announce the translation.
—
Reply to this email directly, [view it on GitHub](#446 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/A4X7JM57NK7F6NG6OS6JVVDWXTU5XANCNFSM6AAAAAAUZR4ARI).
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Thanks for pointing that out. I'll change that page. I was indeed referring to the Hapax page, which is the work of Patrick Andries. Patrick only uses lowercase on that page for notes: the actual character names are all in majuscule. So if that's where you got your translations from then i think we're already good to go, and i should just merge this. I'll wait for your reaction before doing so. |
|
Thank you! To be transparent, I found those translations on Wikipedia, but they match the Hapax recommendations.
I might have one more change to make. I found a Unicode glossary that translated "supplementary characters" as "caractères complémentaires" (rather than "caractères supplémentaires, which I used in the article - in 4-5 instances). Should I use this term instead or are you fine with either?
Thank you,
Gwen
------- Original Message -------
…On Thursday, February 16th, 2023 at 15:14, r12a ***@***.***> wrote:
> In this article, the names have been translated as "U+00E1 Lettre minuscule latine A accent aigu", "U+0061 Lettre minuscule latine A" and "U+0301 Diacritique accent aigu". These names match the recommendations from the Hapax website.
Thanks for pointing that out. I'll change that page.
I was indeed referring to the Hapax page, which is the work of Patrick Andries. Patrick only uses lowercase on that page for notes: the actual character names are all in majuscule. So if that's where you got your translations from then i think we're already good to go, and i should just merge this. I'll wait for your reaction before doing so.
—
Reply to this email directly, [view it on GitHub](#446 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/A4X7JM4AZNTKCMBBIBSNLV3WXYY5XANCNFSM6AAAAAAUZR4ARI).
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
|
I just checked Patrick's book on Unicode and he does refer to 'plans complémentaires'. So i stand corrected. :-) |
|
I understand, I didn't think twice about that term because of all the time and energy spent on "surrogate code points" in the same paragraph :)
Do you want me to make the changes?
…------- Original Message -------
On Thursday, February 16th, 2023 at 18:04, r12a ***@***.***> wrote:
I just checked Patrick's book on Unicode and he does refer to 'plans complémentaires'. So i stand corrected. :-)
—
Reply to this email directly, [view it on GitHub](#446 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/A4X7JM4D4PE4NNLNDTTRNILWXZMZDANCNFSM6AAAAAAUZR4ARI).
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
You're the translator; i rely on your judgement. ;-) |
|
@r12a Hi, I made the changes we discussed, but since I'm new to Git, I might have skipped a step. Is there anything else I need to do? |
|
@clavoline thanks for the prompt. Looks good to me. I think we're ready to publish. I'll take it from here, thanks. |
Submitting a French translation of "questions/qa-escapes" and a few changes to the English version.
<span class="leading">and</span>with<strong class="leading">and</strong>in two instances<code>and</code>around character references in four instancesAdded a link to a section on the same page
Replaced three obsolete links
Modified two links that pointed to different pages but had the same anchor text