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.

Sign up for GitHub

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

Jump to bottom

French translation of QA Byte Order Mark #477

Merged
merged 5 commits into from
Jul 28, 2023
Merged

French translation of QA Byte Order Mark #477

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
17f98a6
French translation of QA Byte Order Mark
clavoline May 30, 2023
29dd41f
French translation of article on RTL scripts
clavoline Jul 15, 2023
d1d4b18
Changes requested by r12a
clavoline Jul 18, 2023
d0cb108
Changes requested by r12a part 2
clavoline Jul 18, 2023
be788ad
Changes requested by r12a part 3
clavoline Jul 21, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 9 additions & 9 deletions questions/qa-byte-order-mark.en.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@

// AUTHORS AND TRANSLATORS should fill in these assignments:
f.thisVersion = { date:'2016-04-20', time:'11:10'} // date and time of latest edits to this document/translation
f.contributors = 'Albert Lunde, Asmus Freytag, Björn Höhrmann, Henri Sivonen, John Cowan, Leif Halvard Silli, Norbert Lindenberg' // people providing useful contributions or feedback during review or at other times
f.contributors = 'Albert Lunde, Asmus Freytag, Björn Höhrmann, Henri Sivonen, John Cowan, Leif Halvard Silli, Norbert Lindenberg, Gwendoline Clavé' // people providing useful contributions or feedback during review or at other times
// also make sure that the lang attribute on the html tag is correct!
f.sources = '' // describes sources of information

Expand Down Expand Up @@ -53,10 +53,10 @@ <h1>The byte-order mark (BOM) in HTML</h1>
<aside id="sidebarExtras">
<section>
<h2 class="notoc">Quick check</h2>
<form action="https://validator.w3.org/i18n-checker/" method="get" class="quickcheck">
<form action="https://validator.w3.org/i18n-checker/check" method="get" class="quickcheck">
<p>Check for byte-order marks in a page</p>
<p>
<input type="text" value="URI of page to check" name="docAddr" onfocus="this.value=''">
<input type="text" value="URI of page to check" name="uri" onfocus="this.value=''">
</p>
<p>
<button type="submit">Check</button>
Expand Down Expand Up @@ -135,11 +135,11 @@ <h3> What do I need to know about the BOM?</h3>

<p>In HTML5 browsers are required to recognize the UTF-8 BOM and use it to detect the encoding of the page, and recent versions of major browsers handle the BOM as expected when used for UTF-8 encoded pages.</p>

<p>The UTF-8 BOM offers reliable encoding detection, since it is extremely short and stable, works in XML and HTML, and works whether your page is read over the network or not (unlike HTTP declarations). However, bear in mind that it is always a good idea to declare the encoding of your page using the meta element, in addition to the BOM, so that the encoding is apparent to people looking at the source text. </p>
<p>The UTF-8 BOM offers reliable encoding detection, since it is extremely short and stable, works in XML and HTML, and works whether your page is read over the network or not (unlike HTTP declarations). However, bear in mind that it is always a good idea to declare the encoding of your page <a href='/International/questions/qa-html-encoding-declarations#nutshell'>using the <code class="kw" translate="no">meta</code> element</a>, in addition to the BOM, so that the encoding is apparent to people looking at the source text. </p>

<p>Also there are a number of situations where the BOM, particularly because it is invisible, may cause a problem. See the section below for more information about those. </p>
<p>Also there are a number of situations where the BOM, particularly because it is invisible, may cause a problem. See the section <a href="#problems">Potential issues with the UTF-8 BOM</a> below for more information about those. </p>

<p>If you use a UTF-16 encoding for your page (and we strongly recommend that you don't), there are some <a href="#bytheway">additional considerations</a>.</p>
<p>If you use a UTF-16 encoding for your page (and we strongly recommend that you don't), there are some <a href="#additionalinfo">additional considerations</a>.</p>
</section>


Expand All @@ -156,7 +156,7 @@ <h3>Detecting the BOM</h3>
<div class="sidenoteGroup">
<p>You can try looking for a UTF-8 signature in your content in your editor, but if your editor handles the BOM correctly you probably won't be able to see it. With a binary editor capable of displaying the hexadecimal byte values in the file, the UTF-8 signature displays as EF BB BF.</p>
<div class="sideinfonote">
<p class="info">If your editor or browser applies the wrong character encoding to a UTF-8 encoded file with a BOM, you are likely to see a sequence of bytes at the start of the file. These are the bytes that compose BOM represented as the characters those bytes represent in that encoding. With the Latin 1 (ISO 8859-1) character encoding, the signature displays as characters .</p>
<p class="info">If your editor or browser applies the wrong character encoding to a UTF-8 encoded file with a BOM, you are likely to see a sequence of bytes at the start of the file. These are the bytes that compose BOM represented as the characters those bytes represent in that encoding. With the Latin 1 (ISO 8859-1) character encoding, the signature displays as characters <code></code>.</p>
</div>
</div>

Expand Down Expand Up @@ -225,7 +225,7 @@ <h4>HTTP precedence</h4>
</div>
<!--p>According to the HTML specification, the HTTP header overrides any in-document encoding. However, some browsers ignore the HTTP header encoding declaration if the file starts with a BOM, and they assume that the file is encoded as UTF-8.</p-->

<p>In <a href="https://www.w3.org/International/tests/repository/html5/the-input-byte-stream/results-basics#precedence">browsers where the HTTP header still overrides the byte-order mark</a> and the server is declaring pages to have a non-Unicode character encoding, you are likely to find unexpected characters at the start of the page (such as  in a page labelled in HTTP as ISO 8859-1) as well as problems displaying non-ASCII characters on the page.</p>
<p>In <a href="https://www.w3.org/International/tests/repository/html5/the-input-byte-stream/results-basics#precedence">browsers where the HTTP header still overrides the byte-order mark</a> and the server is declaring pages to have a non-Unicode character encoding, you are likely to find unexpected characters at the start of the page (such as <code></code> in a page labelled in HTTP as ISO 8859-1) as well as problems displaying non-ASCII characters on the page.</p>
</section>


Expand All @@ -239,7 +239,7 @@ <h4>Other issues</h4>

<p>If you use applications or scripts in the back end of your site you should check that they are also able to recognize and handle the BOM.</p>

<p>We strongly recommend that you don't change the encoding of a UTF-8 file from a Unicode encoding to a non-Unicode encoding, but if, for some exceptional reason, you do you must ensure that the BOM is removed. If you don't, either the browser will continue to treat your content as UTF-8, or you will see strange characters at the beginning of the page.</p>
<p>We strongly recommend that you don't change the encoding of a UTF-8 file from a Unicode encoding to a non-Unicode encoding, but if you do (for some exceptional reason), you must ensure that the BOM is removed. If you don't, either the browser will continue to treat your content as UTF-8, or you will see strange characters at the beginning of the page.</p>
</section>
</section>

Expand Down
Loading