| 1 |
<!-- doc/src/sgml/README.non-ASCII --> |
| 2 |
|
| 3 |
Representation of non-ASCII characters |
| 4 |
-------------------------------------- |
| 5 |
|
| 6 |
Find non-ASCII characters using: |
| 7 |
|
| 8 |
grep --recursive --color='auto' -P '[\x80-\xFF]' . |
| 9 |
|
| 10 |
Convert to HTML4 named entity (&) escapes |
| 11 |
----------------------------------------- |
| 12 |
|
| 13 |
We support several output formats: |
| 14 |
|
| 15 |
* html (supports all Unicode characters) |
| 16 |
* man (supports all Unicode characters) |
| 17 |
* pdf (supports only Latin-1 characters) |
| 18 |
* info |
| 19 |
|
| 20 |
While some output formatting tools support all Unicode characters, |
| 21 |
others only support Latin-1 characters. Specifically, the PDF rendering |
| 22 |
engine can only display Latin-1 characters; non-Latin-1 Unicode |
| 23 |
characters are displayed as "###". |
| 24 |
|
| 25 |
Therefore, in the SGML files, we can only use Latin-1 characters. We |
| 26 |
can use UTF8 representations of Latin-1 characters, or HTML entities of |
| 27 |
Latin-1 characters, e.g., Álvaro. |
| 28 |
|
| 29 |
Do not use UTF numeric character escapes (&#nnn;). |
| 30 |
|
| 31 |
When building the PDF docs, problem characters will appear as warnings. |
| 32 |
|
| 33 |
HTML entities |
| 34 |
official: http://www.w3.org/TR/html4/sgml/entities.html |
| 35 |
one page: http://www.zipcon.net/~swhite/docs/computers/browsers/entities_page.html |
| 36 |
other lists: http://www.zipcon.net/~swhite/docs/computers/browsers/entities.html |
| 37 |
http://www.zipcon.net/~swhite/docs/computers/browsers/entities_page.html |
| 38 |
https://en.wikipedia.org/wiki/List_of_XML_and_HTML_character_entity_references |