search

lvapeab / m4loc

Automatically exported from code.google.com/p/m4loc
GNU Lesser General Public License v3.0
0 stars 0 forks source link

tikal leveraging with ASCII input leads to Windows-1252 encoded XLIFF file #16

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
1. tikal.bat -xm .\t\languagetool.xlf
2. copy .\t\languagetool.xlf.en-us .\t\languagetool.xlf.fr-fr
3. tikal.bat -lm .\t\languagetool.xlf

Observation: first line of resulting languagetool.out.xlf is:
<?xml version="1.0" encoding="windows-1252"?>[...]
File encoding is ASCII/Windows-1252 (no characters outside ASCII range in file)

Expected:
File to be UTF-8 encoded - first line:
<?xml version="1.0" encoding="utf-8"?>

The file encoding can be forced by adding the option -oe utf8 to the tikal 
command in line 3.

Original issue reported on code.google.com by Achi...@gmail.com on 8 Mar 2011 at 8:06

GoogleCodeExporter commented 9 years ago 
Changed Type to "Enhancement" as the output is a valid XML file. Issue in 
external tool Okapi - enter bug there if this is still a problem.

Original comment by Achi...@gmail.com on 17 Feb 2012 at 8:46