[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xliff] Version Control Commit by David.Filip
David, I’ve dug further into the issue, and tried many ways of resolving the characters. Unfortunately I’ve had no success. I haven’t done anything more with AntennaHouse because of the differences in formatting. Within xliff-20\docbook\xsl\fo\inline.xsl there’s a block of code for processing <foreignphrase>; it has choice blocks for language codes ‘ja’ and ‘ar’, allowing specific fonts to be selected. I added a block for ‘cs’ and tried a variety of fonts but with no success. Perhaps you have a font available on your system that includes the full Czech character set. If you find a font that works, we’d need to ensure it’s embedded or at least subsetted so the required glyphs are in the PDF; otherwise the PDF reader will substitute a font and it won’t display properly. So the font licence would have to allow embedding. Hope that helps. The alternative might be a quote without that particular character. Regards, Tom From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf Of Dr. David Filip Thanks, Yves, I see, the FOP pretends to understand and gives me the completely wrong character (only being too well used to this kind of corruption I know that it was supposed to be a "č" ), while the SVN tells me what exactly it did not understand, which is more "honest" but still appalling in 2014. It is an example of a quote/inline citation and the quote cannot be changed without actually stopping being the quote. I provided the example in Czech as 1) a localization format standard should contain examples in different languages 2) I am native Czech speaker, so can guarantee correctness Unfortunately, it is quite hard to avoid extended characters that are not included in the ANSI set in a properly spelled Czech sentence. "ř", "ě", "ž" to name just a few on top of the "č" that is currently being butchered by the printing and SVN infrastructures. If anyone wants to provide a replacement example in an ANSI language please go ahead. I just feel very bad about us, a localization interchange format committee, giving up an example just because of internationalization issues of the infra. Cheers dF Dr. David Filip ======================= LRC | CNGL | LT-Web | CSIS University of Limerick, Ireland telephone: +353-6120-2781 cellphone: +353-86-0222-158 facsimile: +353-6120-2734 mailto: david.filip@ul.ie On Mon, Mar 31, 2014 at 11:36 PM, Yves Savourel <ysavourel@enlaso.com> wrote: Actually "?\196?\141" is a bit better because you can trace it back to the č, (it's the two byte values for the UTF-8 encoding of č). With # you are a bit more in the fog.
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]