Victor,
I noticed from your commt that the 'country-name's had lost their
spaces, e.g., MACEDONIA,THEFORMERYUGOSLAVREPUBLICOF.
I don't know whether this was in the original, but it certainly reads
awkwardly.
fop.xsd also includes 2-letter language codes. However, the 3-letter
language codes are the ones we need. They have terminology and
bibliographic variants (the terminology variant is normative for XSL)
which occasionally differ. Many languages have the legacy 639-1
2-letter as well, and it is useful to keep them about the place, as they
are frequently used, e.g. en_US. See ISO 639-2T, ISO 639-2B, ISO 639-1
<http://www.loc.gov/standards/iso639-2/>
In conf/xml-lang.xml (under tag FOP_0-20-0_Alt-Design, naturally) I have
included these variants as optional attributes in the language entries.
E.g. the following consecutive entries:
<language terminology="zho" bibliographic="chi" iso639-1="zh"
EnglishName="Chinese"
FrenchName="chinois"/>
<language terminology="chk"
EnglishName="Chuukese"
FrenchName="chuuk"/>
fop.xsd has no "script" entries. xml-lang.xml contains script codes
according to the latest version of the ISO 15924 draft that I could find.
Chuck, if you want me to post a copy of the file to you, let me know.
Peter
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord, to whom shall we go?"
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
- fop.xsd Peter B. West
- Re: fop.xsd Peter B. West
- RE: fop.xsd Victor Mote
- RE: fop.xsd Victor Mote
- RE: fop.xsd Peter B. West
- RE: fop.xsd Victor Mote
- RE: fop.xsd Victor Mote
