OASIS XML Localisation Interchange File Format (XLIFF) TC

 View Only
  • 1.  Version Control Commit by David.Filip

    Posted 03-31-2014 22:01
    Author: David.Filip Date: 2014-03-31 22:02:23 +0000 (Mon, 31 Mar 2014) New Revision: 505 Web View: https://tools.oasis-open.org/version-control/browse/wsvn/xliff/trunk/?rev=505&sc=1 Added: trunk/xliff-20/xliff-core-v2.0-cs01.html trunk/xliff-20/xliff-core-v2.0-cs01.pdf trunk/xliff-20/xliff-core-v2.0-cs01.xml Removed: trunk/xliff-20/schemas.zip Modified: trunk/PR03_CommentsDisposal/extendedchars.txt trunk/xliff-20/attributes/type.xml trunk/xliff-20/core/schema.xml trunk/xliff-20/merge.bat trunk/xliff-20/modules/candidates/schema.xml trunk/xliff-20/modules/candidates/specification.xml trunk/xliff-20/modules/change-tracking/schema.xml trunk/xliff-20/modules/fs/schema.xml trunk/xliff-20/modules/glossary/schema.xml trunk/xliff-20/modules/metadata/schema.xml trunk/xliff-20/modules/resourcedata/schema.xml trunk/xliff-20/modules/size_restriction/schema.xml trunk/xliff-20/modules/validation/schema.xml trunk/xliff-20/modules/validation/specification.xml trunk/xliff-20/stylesheets/oasis-specification-fo-a4.xsl trunk/xliff-20/xliff-20.zip trunk/xliff-20/xliff-core-v2.0-wd04.html trunk/xliff-20/xliff-core.html trunk/xliff-20/xliff-core.pdf trunk/xliff-20/xliff-core.xml trunk/xliff-20/xliff20.xml Log: cs01 printout ---------------- last remaining issue "?196?141" characters corrupted as "#" in pdf only


  • 2.  Re: [xliff] Version Control Commit by David.Filip

    Posted 03-31-2014 22:28
    This is amazing, 2014, Unicode 7, and we are still struggling with printing/sending properly the "c" character.. I have never seen this sort of corruption "?196?141" instead of "c", Apache FOP making the usual "#" seems stellar compared to  "?196?141" 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 http://www.cngl.ie/profile/?i=452 mailto: david.filip@ul.ie On Mon, Mar 31, 2014 at 11:02 PM, < workgroup_mailer@lists.oasis-open.org > wrote: Author: David.Filip Date: 2014-03-31 22:02:23 +0000 (Mon, 31 Mar 2014) New Revision: 505 Web View: https://tools.oasis-open.org/version-control/browse/wsvn/xliff/trunk/?rev=505&sc=1 Added:    trunk/xliff-20/xliff-core-v2.0-cs01.html    trunk/xliff-20/xliff-core-v2.0-cs01.pdf    trunk/xliff-20/xliff-core-v2.0-cs01.xml Removed:    trunk/xliff-20/schemas.zip Modified:    trunk/PR03_CommentsDisposal/extendedchars.txt    trunk/xliff-20/attributes/type.xml    trunk/xliff-20/core/schema.xml    trunk/xliff-20/merge.bat    trunk/xliff-20/modules/candidates/schema.xml    trunk/xliff-20/modules/candidates/specification.xml    trunk/xliff-20/modules/change-tracking/schema.xml    trunk/xliff-20/modules/fs/schema.xml    trunk/xliff-20/modules/glossary/schema.xml    trunk/xliff-20/modules/metadata/schema.xml    trunk/xliff-20/modules/resourcedata/schema.xml    trunk/xliff-20/modules/size_restriction/schema.xml    trunk/xliff-20/modules/validation/schema.xml    trunk/xliff-20/modules/validation/specification.xml    trunk/xliff-20/stylesheets/oasis-specification-fo-a4.xsl    trunk/xliff-20/xliff-20.zip    trunk/xliff-20/xliff-core-v2.0-wd04.html    trunk/xliff-20/xliff-core.html    trunk/xliff-20/xliff-core.pdf    trunk/xliff-20/xliff-core.xml    trunk/xliff-20/xliff20.xml Log: cs01 printout ---------------- last remaining issue "?196?141" characters corrupted as "#" in pdf only --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail.  Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php


  • 3.  RE: [xliff] Version Control Commit by David.Filip

    Posted 03-31-2014 22:37
    Actually "?196?141" is a bit better because you can trace it back to the c, (it's the two byte values for the UTF-8 encoding of c). With # you are a bit more in the fog. Maybe you should just change the text of the example to not have c... -ys From: xliff@lists.oasis-open.org [ mailto:xliff@lists.oasis-open.org ] On Behalf Of Dr. David Filip Sent: Monday, March 31, 2014 4:27 PM To: xliff@lists.oasis-open.org Subject: Re: [xliff] Version Control Commit by David.Filip This is amazing, 2014, Unicode 7, and we are still struggling with printing/sending properly the "c" character.. I have never seen this sort of corruption "?196?141" instead of "c", Apache FOP making the usual "#" seems stellar compared to "?196?141" 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 http://www.cngl.ie/profile/?i=452 mailto: david.filip@ul.ie On Mon, Mar 31, 2014 at 11:02 PM, <workgroup_mailer@lists.oasis-open.org> wrote: Author: David.Filip Date: 2014-03-31 22:02:23 +0000 (Mon, 31 Mar 2014) New Revision: 505 Web View: https://tools.oasis-open.org/version-control/browse/wsvn/xliff/trunk/?rev=505&sc=1 Added: trunk/xliff-20/xliff-core-v2.0-cs01.html trunk/xliff-20/xliff-core-v2.0-cs01.pdf trunk/xliff-20/xliff-core-v2.0-cs01.xml Removed: trunk/xliff-20/schemas.zip Modified: trunk/PR03_CommentsDisposal/extendedchars.txt trunk/xliff-20/attributes/type.xml trunk/xliff-20/core/schema.xml trunk/xliff-20/merge.bat trunk/xliff-20/modules/candidates/schema.xml trunk/xliff-20/modules/candidates/specification.xml trunk/xliff-20/modules/change-tracking/schema.xml trunk/xliff-20/modules/fs/schema.xml trunk/xliff-20/modules/glossary/schema.xml trunk/xliff-20/modules/metadata/schema.xml trunk/xliff-20/modules/resourcedata/schema.xml trunk/xliff-20/modules/size_restriction/schema.xml trunk/xliff-20/modules/validation/schema.xml trunk/xliff-20/modules/validation/specification.xml trunk/xliff-20/stylesheets/oasis-specification-fo-a4.xsl trunk/xliff-20/xliff-20.zip trunk/xliff-20/xliff-core-v2.0-wd04.html trunk/xliff-20/xliff-core.html trunk/xliff-20/xliff-core.pdf trunk/xliff-20/xliff-core.xml trunk/xliff-20/xliff20.xml Log: cs01 printout ---------------- last remaining issue "?196?141" characters corrupted as "#" in pdf only --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php


  • 4.  Re: [xliff] Version Control Commit by David.Filip

    Posted 04-01-2014 09:45
    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 "c" ), 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.  "r", "e", "ž" to name just a few on top of the "c" 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 http://www.cngl.ie/profile/?i=452 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 c, (it's the two byte values for the UTF-8 encoding of c). With # you are a bit more in the fog. Maybe you should just change the text of the example to not have c... -ys From: xliff@lists.oasis-open.org [mailto: xliff@lists.oasis-open.org ] On Behalf Of Dr. David Filip Sent: Monday, March 31, 2014 4:27 PM To: xliff@lists.oasis-open.org Subject: Re: [xliff] Version Control Commit by David.Filip This is amazing, 2014, Unicode 7, and we are still struggling with printing/sending properly the "c" character.. I have never seen this sort of corruption "?196?141" instead of "c", Apache FOP making the usual "#" seems stellar compared to "?196?141" 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 http://www.cngl.ie/profile/?i=452 mailto: david.filip@ul.ie On Mon, Mar 31, 2014 at 11:02 PM, < workgroup_mailer@lists.oasis-open.org > wrote: Author: David.Filip Date: 2014-03-31 22:02:23 +0000 (Mon, 31 Mar 2014) New Revision: 505 Web View: https://tools.oasis-open.org/version-control/browse/wsvn/xliff/trunk/?rev=505&sc=1 Added:    trunk/xliff-20/xliff-core-v2.0-cs01.html    trunk/xliff-20/xliff-core-v2.0-cs01.pdf    trunk/xliff-20/xliff-core-v2.0-cs01.xml Removed:    trunk/xliff-20/schemas.zip Modified:    trunk/PR03_CommentsDisposal/extendedchars.txt    trunk/xliff-20/attributes/type.xml    trunk/xliff-20/core/schema.xml    trunk/xliff-20/merge.bat    trunk/xliff-20/modules/candidates/schema.xml    trunk/xliff-20/modules/candidates/specification.xml    trunk/xliff-20/modules/change-tracking/schema.xml    trunk/xliff-20/modules/fs/schema.xml    trunk/xliff-20/modules/glossary/schema.xml    trunk/xliff-20/modules/metadata/schema.xml    trunk/xliff-20/modules/resourcedata/schema.xml    trunk/xliff-20/modules/size_restriction/schema.xml    trunk/xliff-20/modules/validation/schema.xml    trunk/xliff-20/modules/validation/specification.xml    trunk/xliff-20/stylesheets/oasis-specification-fo-a4.xsl    trunk/xliff-20/xliff-20.zip    trunk/xliff-20/xliff-core-v2.0-wd04.html    trunk/xliff-20/xliff-core.html    trunk/xliff-20/xliff-core.pdf    trunk/xliff-20/xliff-core.xml    trunk/xliff-20/xliff20.xml Log: cs01 printout ---------------- last remaining issue "?196?141" characters corrupted as "#" in pdf only --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail.  Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail.  Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php


  • 5.  RE: [xliff] Version Control Commit by David.Filip

    Posted 04-01-2014 14:30
    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-20docbookxslfoinline.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 Sent: Tuesday, April 01, 2014 05:44 AM To: Yves Savourel Cc: xliff@lists.oasis-open.org Subject: Re: [xliff] Version Control Commit by 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 "c" ), 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.  "r", "e", "ž" to name just a few on top of the "c" 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 http://www.cngl.ie/profile/?i=452 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 c, (it's the two byte values for the UTF-8 encoding of c). With # you are a bit more in the fog. Maybe you should just change the text of the example to not have c... -ys From: xliff@lists.oasis-open.org [mailto: xliff@lists.oasis-open.org ] On Behalf Of Dr. David Filip Sent: Monday, March 31, 2014 4:27 PM To: xliff@lists.oasis-open.org Subject: Re: [xliff] Version Control Commit by David.Filip This is amazing, 2014, Unicode 7, and we are still struggling with printing/sending properly the "c" character.. I have never seen this sort of corruption "?196?141" instead of "c", Apache FOP making the usual "#" seems stellar compared to "?196?141" 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 http://www.cngl.ie/profile/?i=452 mailto: david.filip@ul.ie On Mon, Mar 31, 2014 at 11:02 PM, < workgroup_mailer@lists.oasis-open.org > wrote: Author: David.Filip Date: 2014-03-31 22:02:23 +0000 (Mon, 31 Mar 2014) New Revision: 505 Web View: https://tools.oasis-open.org/version-control/browse/wsvn/xliff/trunk/?rev=505&sc=1 Added:    trunk/xliff-20/xliff-core-v2.0-cs01.html    trunk/xliff-20/xliff-core-v2.0-cs01.pdf    trunk/xliff-20/xliff-core-v2.0-cs01.xml Removed:    trunk/xliff-20/schemas.zip Modified:    trunk/PR03_CommentsDisposal/extendedchars.txt    trunk/xliff-20/attributes/type.xml    trunk/xliff-20/core/schema.xml    trunk/xliff-20/merge.bat    trunk/xliff-20/modules/candidates/schema.xml    trunk/xliff-20/modules/candidates/specification.xml    trunk/xliff-20/modules/change-tracking/schema.xml    trunk/xliff-20/modules/fs/schema.xml    trunk/xliff-20/modules/glossary/schema.xml    trunk/xliff-20/modules/metadata/schema.xml    trunk/xliff-20/modules/resourcedata/schema.xml    trunk/xliff-20/modules/size_restriction/schema.xml    trunk/xliff-20/modules/validation/schema.xml    trunk/xliff-20/modules/validation/specification.xml    trunk/xliff-20/stylesheets/oasis-specification-fo-a4.xsl    trunk/xliff-20/xliff-20.zip    trunk/xliff-20/xliff-core-v2.0-wd04.html    trunk/xliff-20/xliff-core.html    trunk/xliff-20/xliff-core.pdf    trunk/xliff-20/xliff-core.xml    trunk/xliff-20/xliff20.xml Log: cs01 printout ---------------- last remaining issue "?196?141" characters corrupted as "#" in pdf only --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail.  Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail.  Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php  


  • 6.  Re: [xliff] Version Control Commit by David.Filip

    Posted 04-01-2014 14:36
    Thanks, Tom, I will now concentrate on redoing the cs01 package with the new schema listings. We can discuss what with those corrupted characters in the TC meeting.. Rgds 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 http://www.cngl.ie/profile/?i=452 mailto: david.filip@ul.ie On Tue, Apr 1, 2014 at 3:31 PM, Tom Comerford < tom@supratext.com > wrote: 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-20docbookxslfoinline.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 Sent: Tuesday, April 01, 2014 05:44 AM To: Yves Savourel Cc: xliff@lists.oasis-open.org Subject: Re: [xliff] Version Control Commit by 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 "c" ), 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.  "r", "e", "ž" to name just a few on top of the "c" 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 http://www.cngl.ie/profile/?i=452 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 c, (it's the two byte values for the UTF-8 encoding of c). With # you are a bit more in the fog. Maybe you should just change the text of the example to not have c... -ys From: xliff@lists.oasis-open.org [mailto: xliff@lists.oasis-open.org ] On Behalf Of Dr. David Filip Sent: Monday, March 31, 2014 4:27 PM To: xliff@lists.oasis-open.org Subject: Re: [xliff] Version Control Commit by David.Filip This is amazing, 2014, Unicode 7, and we are still struggling with printing/sending properly the "c" character.. I have never seen this sort of corruption "?196?141" instead of "c", Apache FOP making the usual "#" seems stellar compared to "?196?141" 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 http://www.cngl.ie/profile/?i=452 mailto: david.filip@ul.ie On Mon, Mar 31, 2014 at 11:02 PM, < workgroup_mailer@lists.oasis-open.org > wrote: Author: David.Filip Date: 2014-03-31 22:02:23 +0000 (Mon, 31 Mar 2014) New Revision: 505 Web View: https://tools.oasis-open.org/version-control/browse/wsvn/xliff/trunk/?rev=505&sc=1 Added:    trunk/xliff-20/xliff-core-v2.0-cs01.html    trunk/xliff-20/xliff-core-v2.0-cs01.pdf    trunk/xliff-20/xliff-core-v2.0-cs01.xml Removed:    trunk/xliff-20/schemas.zip Modified:    trunk/PR03_CommentsDisposal/extendedchars.txt    trunk/xliff-20/attributes/type.xml    trunk/xliff-20/core/schema.xml    trunk/xliff-20/merge.bat    trunk/xliff-20/modules/candidates/schema.xml    trunk/xliff-20/modules/candidates/specification.xml    trunk/xliff-20/modules/change-tracking/schema.xml    trunk/xliff-20/modules/fs/schema.xml    trunk/xliff-20/modules/glossary/schema.xml    trunk/xliff-20/modules/metadata/schema.xml    trunk/xliff-20/modules/resourcedata/schema.xml    trunk/xliff-20/modules/size_restriction/schema.xml    trunk/xliff-20/modules/validation/schema.xml    trunk/xliff-20/modules/validation/specification.xml    trunk/xliff-20/stylesheets/oasis-specification-fo-a4.xsl    trunk/xliff-20/xliff-20.zip    trunk/xliff-20/xliff-core-v2.0-wd04.html    trunk/xliff-20/xliff-core.html    trunk/xliff-20/xliff-core.pdf    trunk/xliff-20/xliff-core.xml    trunk/xliff-20/xliff20.xml Log: cs01 printout ---------------- last remaining issue "?196?141" characters corrupted as "#" in pdf only --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail.  Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail.  Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php