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

[French] Update “Personal names around the world” #262

Merged
merged 9 commits into from Sep 27, 2021

Conversation

arkhi
Copy link
Contributor

@arkhi arkhi commented Sep 8, 2020

Hello,

@r12a: Thanks for your addition in English within the translated text, it was helpful not having to search. :)
@notabene: Proof‑reading is welcome!

This PR includes a couple of things. Let me know if you’d rather have the commits in separate PR or if some changes are a problem. You can visualize the diff without white-space changes to reduce the noise.

Here’s a summary:

  • Fix typo in English version: repesents to represents.
  • Translate to French:
    • Add non‑breakable space character before punctuation () in description.
    • Translate English paragraphs to French.
    • Translate two titles which were in English.
  • Remove quotes around single character text stylized with qchar; It was leading to two types of quotes around a single letter.
  • Reformat markup:
    • Remove trailing spaces.
    • Remove line‑breaks around <mark> as they were breaking the flow of sentences before punctuation (. or ,).
    • Remove space in emtpy tags: <tag> </tag> to <tag></tag>.
    • Remove stray tab!
    • Indent lines consistently.
    • Make blocks breath a bit.
    • Remove type attribute.
    • Escape closing tags in JS string.

Closes #261

questions/qa-personal-names.fr.html Outdated Show resolved Hide resolved
</section>
<section>
<h3 id="middleinitial"><a href="#middleinitial">Initiales au milieu</a></h3>
<p>Les américains écrivent souvent leur nom avec une initiale au milieu, par exemple <b class="highlight">John Q. Public</b>. Les formulaires conçus aux États-Unis considèrent fréquemment cette pratique comme normale, alors qu'au Royaume-Uni, où les gens ont souvent un ou plusieurs seconds prénoms, elle est vue comme une approche très américaine. Dans d’autres pays, les personnes avec plus de deux noms et qui ne les écrivent pas habituellement en initiales, peuvent ne pas savoir comment remplir ce type de formulaires. De plus il faut bien comprendre que de nombreuses personnes qui utilisent des initiales les mettent au début de leur nom.</p>
<p>Filipinos also write their name with a middle initial, but it represents the mother's name before marriage rather than a given name. For example, in <b class="highlight">Maria J. Go</b>, the initial repesents Jimenez, the previous family name of Maria's mother. (In fact, an initial may represent more than one name: 'D' may stand for 'Dela Cruz' when the name is written in full.)</p>
<p>Les Philippins écrivent également leur nom avec une initiale au milieu, mais celle‑ci représente le nom de naissance de la mère. Par exemple, pour <b class="highlight">Maria J. Go</b>, l’initiale représente Jimenez, le nom de naissance de la mère de Maria. Une initiale peut même représenter plus d’un seul nom&nbsp;: <span class="qchar">D</span> peut signifier ‘Dela Cruz’ lorsque le nom est écrit dans son intégralité.</p>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<p>Les Philippins écrivent également leur nom avec une initiale au milieu, mais celle‑ci représente le nom de naissance de la mère. Par exemple, pour <b class="highlight">Maria J. Go</b>, l’initiale représente Jimenez, le nom de naissance de la mère de Maria. Une initiale peut même représenter plus d’un seul nom&nbsp;: <span class="qchar">D</span> peut signifier Dela Cruz lorsque le nom est écrit dans son intégralité.</p>
<p>Les Philippins écrivent également leur nom avec une initiale au milieu, mais celle‑ci représente le nom de naissance de la mère. Par exemple, pour <b class="highlight">Maria J. Go</b>, l’initiale représente Jimenez, le nom de naissance de la mère de Maria. Une initiale peut même représenter plus d’un seul nom&nbsp;: <span class="qchar">D</span> peut signifier «&nbsp;Dela Cruz&nbsp;» lorsque le nom est écrit dans son intégralité.</p>

(I know I used single quotes here and there, but come to think of it it's not very correct, typography-wise, in French. @arkhi I'll let you decide whether keeping single quotes everywhere or changeing everything to double French quotes.)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think I’ll let you answer first next time. :}

I was surprised about all those single quotes so I appreciate you’re bringing this up. I’ll change to double‑quotes.

Does anybody have any objection to using Unicode characters instead of HTML entities?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Based on my previous comment, I would replace those quotes by italic unless one has reasons not to.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, why not, I'm ok with it. But maybe @r12a has something to say.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@r12a: I tried to apply changes to the document in its entirety and went a bit mad. :}

I wonder if we should better get the ball rolling; I can submit a different PR with those changes and include more needed updates, like changing all &nbsp; to narrow non‑breakable spaces (&#8239;), etc.


If I understand properly the usage of <i>, idiomatic text would be used for most of the text that is not in the language of the article and is not used as the name of the person itself. That means a lot of the text could be updated with:

<i class="foreign" lang="[…]">[…]</i>

In the following example, only the first appellidos is used as an idiomatic text, alhtough I understand <i> should wrap all occurrences. I would change <span> to <i class="foreign" lang="es"> if that was just me, but I guess this was thought out before and I would prefer not to break anything (and learn about why).

<i class="foreign" lang="es">apellidos</i>, sont Pérez Quiñones parce que les <span lang="es">apellidos</span> de son père sont Pérez Rodriguez et les <span lang="es">apellidos</span> […]

All text in a foreign language should also be marked with its lang attribute, I guess? Am I too extreme to think so? :)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My 2cts: I always add lang attributes, for accessibility's sake.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All apellidos should indeed be surrounded by <i class="foreign" lang="en">...</i>. I have changed this in the english version. Foreign language text should have lang attributes.

questions/qa-personal-names.fr.html Outdated Show resolved Hide resolved
@r12a
Copy link
Contributor

r12a commented Sep 8, 2020

@arkhi thanks for pointing out the 'represents' typo and the http -> https. I have just committed a new version of the english file with those things corrected, so you can remove the en file changes from your PR.

@arkhi
Copy link
Contributor Author

arkhi commented Sep 8, 2020

@r12a: My pleasure; I would have rather just left my history alone but I’ll rebase once all comments and changes are agreed upon. ;)

Fabien Basmaison added 5 commits September 11, 2020 20:27
- Add non‑breakable space in description;
- Translate English paragraphs to French;
- Translate two titles which were in English.
- Remove line‑breaks around `<mark>` as they were breaking the flow of sentences before punctuation (`.` or `,`).
- Remove space in emtpy tags: `<tag> </tag>` to `<tag></tag>`.
- Remove stray tab!
- Indent lines consistently.
- Make blocks breath a bit.
- Remove `type` attribute.
- Escape closing tags in string.
@r12a
Copy link
Contributor

r12a commented Apr 7, 2021

This seems to have dropped under the radar. What's the current status ?

@arkhi
Copy link
Contributor Author

arkhi commented Apr 7, 2021

Hello @r12a. I was suggesting we could move forward and I could make another PR with more changes later on. That is, if you think it’s OK to do so.

I think my previous comment summarise what could be done. Your feedback on it would be most welcome.

@notabene
Copy link
Member

notabene commented Apr 7, 2021

Hi @r12a — fine by me whatever @arkhi says. I have no spare time at the moment but he and I date a long way back and I trust him completely just to be clear. :)

@r12a
Copy link
Contributor

r12a commented Sep 24, 2021

@arkhi I just came across this again in some old email lists. Can we merge it? Looks like a conflict has crept in that will need to be cleared. If you can fix that, i'm happy to merge it.

@arkhi
Copy link
Contributor Author

arkhi commented Sep 24, 2021

@r12a: Sure. I’ll check tomorrow. Thanks for checking in!

@arkhi
Copy link
Contributor Author

arkhi commented Sep 25, 2021

@r12a: Conflicts are gone and the PR is ready to be merged.

@r12a r12a merged commit 7ecea89 into w3c:gh-pages Sep 27, 2021
@r12a
Copy link
Contributor

r12a commented Sep 27, 2021

Et voilà ! Thanks for sticking with this to the end. I'll now upload to the w3c site, too.

@r12a
Copy link
Contributor

r12a commented Sep 27, 2021

Ok, main location at https://www.w3.org/International/questions/qa-personal-names.en now synched, and 'needs update' banner removed.

Merci, encore une fois.

@arkhi
Copy link
Contributor Author

arkhi commented Sep 27, 2021

Avec plaisir. :)

I’ll make another PR or PRs with the typographic changes we mentioned with @notabene next.

Also incoming potential cross‑translations changes I saw while dealing with the merge conflicts.

@r12a
Copy link
Contributor

r12a commented Sep 27, 2021

Btw, i think you used NBSP before punctuation. I think NNBSP might be better(?)  

Just a suggestion.

@arkhi
Copy link
Contributor Author

arkhi commented Sep 28, 2021

Btw, i think you used NBSP before punctuation. I think NNBSP might be better(?)  

Completely agreed; that’s part of the plan. :)

@r12a
Copy link
Contributor

r12a commented Sep 28, 2021

Great. Btw, would you be happy use hex numbers in escapes, rather than decimal? I'm so used to the former that it keeps throwing me off because i don't recognise the numbers.

@arkhi
Copy link
Contributor Author

arkhi commented Sep 28, 2021

I would not be unhappy. :)

With Slightly Smiling Face Emoji as example, I understand you mean using &#x1F642; (🙂) instead of &#128578; (🙂); am I correct?

I was planning to simply use the unicode characters.

For example, for narrow no‑break space instead of &#x202F;, &#8239; or any existing HTML entity.

Would that be a problem or is it better to use the hex version in all cases? The downsides I see is they are less explicit and probably harder to input for people with non‑friendly OS.

@arkhi
Copy link
Contributor Author

arkhi commented Sep 28, 2021

Nevermind, I continued reading and found the answer to my question. I will use escapes for invisible characters.

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.

[questions/qa-personal-names] Additional translation needed
3 participants