>From: OmegaT@yahoogroups.com [mailto:OmegaT@yahoogroups.com]On Behalf Of
>Sent: Wednesday, May 09, 2012 5:42 PM
>Subject: [OmT] Default encoding and extension change in OmegaT-2.3.0-7
>1. In Edit Filter dialog, both the Source File Encoding and Translated File
Encoding for Text Files are by default set as <auto> whose drop down menue
gives also some other encoding options. What's the philosophy behind this?
With regard to the fact that UTF-8 endcoding already covers almost all
languages, why isn't it the default file encoding for plain text files in
Because the operating systems of the majority of users do not create text
files in UTF-8 by default.
>2. Is it OK if I change the said default <auto>, in both the Source File
Encoding and Translated File Encoding columns for *.txt (Text Files), to
Yes, as long as you supply text files in UTF-8.
>Does this mean OmegaT-2.3.0-7 will always automatically change both the
encoding and extension of a given imported source ANSI encoded *.txt file to
UTF-8 endcoded *.utf8 file for both source and translated files thereafter,
so that I won't be forced to to this manually every time?
Do not confuse the name of the file and the character set.
(And you do not need to rename the source file.)
Not that way.
If you want that to happen (automatic change of ANSI to UTF-8 *and*
automatic change of name from *.txt to *.utf8), you have to:
Use <auto> for the source file encoding.
Use UTF-8 for the target file encoding.
This will take care of the conversion of the character set.
Change the Translated Filename Pattern to
This will rename the file as you wish.