F Wolff wrote: > Op Wo, 2009-06-10 om 13:57 +0800 skryf Aijin Kim: > >> Hi Friedel, >> >> F Wolff wrote: >> >>> Op Ma, 2009-06-08 om 11:04 +0800 skryf Aijin Kim: >>> >>> >>>> Thank you Friedel! >>>> I'll try the patch once I get it and let you know the result. >>>> >>>> Thanks, >>>> Aijin >>>> >>>> >>> Hallo Aijin >>> >>> Did you make any change to the file? I just looked again through the >>> specifications, and it seems that our old handling of whitespace was >>> actually correct all along. >>> >>> >> The file has not been changed. >> >> >>> My understanding is that unless xml:space="preserve" is specified, the >>> application can do what it wants (the XLIFF specification talks about >>> "default white-space processing modes" of the application). In the case >>> of xml:space="preserve" the application must do what we have been doing >>> all along anyway. For now I think we will start to specify >>> xml:space="preserve" more often in the files we create, but we will >>> probably not be changing our behaviour yet, unless there seems to be >>> good motivation. >>> >>> Where does this file come from? My guess is that XLIFF files should >>> always specify the spacing as they want it to be interpreted, otherwise >>> it will be left to the application's default behaviour. >>> >>> >> The file is for OO.o documentation project. I guess it was extracted >> from the OO.o documentation wiki page. >> >> Is there any possibility to prevent display of whitespaces and '\n's >> during Pootle online translation? If they are not translatable strings >> and should always be preserved, display of them could make translators >> confused. >> >> Thanks, >> Aijin >> > > The file currently specifies xml:space="preserve", so even if I change > the code to ignore the whitespace in the default settings, it would > still not make a difference for that file, because the file explicitly > says that spacing should be preserved. > > This is why I am asking where the file comes from so that we can try to > find the program that created it, and figure out if they really wanted > to say xml:space="preserve" and if we can try to reach some better > interoperability. >
Thanks Friedel, Asgeir for your comments. The file was created with an internal tool which extracts wiki content and creates English xliff file. I've asked to a developer of the tool if xml:space="preserve" should be kept. I'll let you know once I get a reply. If the file specifies xml:space="default", can we ignore the whitespaces and with applying modified TT codes? Or shall we need any other setting or condition? Thanks, Aijin > Keep well > Friedel > > -- > Recently on my blog: > http://translate.org.za/blogs/friedel/en/content/google-chrome-uses-hunspell > > > ------------------------------------------------------------------------------ > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensing option that enables unlimited > royalty-free distribution of the report engine for externally facing > server and web deployment. > http://p.sf.net/sfu/businessobjects > _______________________________________________ > Translate-pootle mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/translate-pootle > ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ Translate-pootle mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/translate-pootle
