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. 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. For reference: http://docs.oasis-open.org/xliff/v1.2/os/xliff-core.html#xml_space http://www.w3.org/TR/REC-xml/#sec-white-space Any comments? Asgeir? 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
