> Hi Igor
> isn¹t there an easier way to continue working on a large project than
> having
> to choose term.tmx/Project.tmx/external.tmx all over again every time I
> open
> the project?
> Why can these databases not be linked to the project so that on opening
> the
> project file everything is there?
They are linked if you tick the relevant boxes in the Project manager
window - see the Memories section in the upper part of the panel. Perhaps
I should add one more box for the "Term memory" there.
> This is the case with most other CAT tools.
> Would be very helpful and time saving. Importing my external tmx for
> segment
> takes about 15/20 minutes because it has to change languages, don¹t ask
> me
> why.
I know why :) Currently, the TMX language pairs are case sensitive (for
speed reasons). The internal language mapping is like the following:
English (United States) = en-US. The language code is lowercase and the
country code is uppercase. I suspect your imported TMX has all in
uppercase (like EN-US). CT cannot find such segments in the first pass, so
it detects the correct language pair code and makes the second pass. If
you type your TMX language codes in the language pair field, the program
will load the segments in the first pass, that is, faster.
Cheers,
Regards
Wolfgang
Am 04/04/12 12:13 schrieb "Igor Kmitowski" unter
<cafetran...@gmail.com>:
Regards
Wolfgang
Am 04/04/12 12:13 schrieb "Igor Kmitowski" unter
<cafetran...@gmail.com>:
>
> They are linked if you tick the relevant boxes in the Project manager
> window - see the Memories section in the upper part of the panel. Perhaps
> I should add one more box for the "Term memory" there.
I'd second that.
>
>> This is the case with most other CAT tools.
>> Would be very helpful and time saving. Importing my external tmx for
>> segment
>> takes about 15/20 minutes because it has to change languages, don¹t ask
>> me
>> why.
>
> I know why :) Currently, the TMX language pairs are case sensitive (for
> speed reasons). The internal language mapping is like the following:
> English (United States) = en-US. The language code is lowercase and the
> country code is uppercase. I suspect your imported TMX has all in
> uppercase (like EN-US). CT cannot find such segments in the first pass, so
> it detects the correct language pair code and makes the second pass. If
> you type your TMX language codes in the language pair field, the program
> will load the segments in the first pass, that is, faster.
Yes, AAMOF, this was the case. So what is the standard internal language
mapping of CT?
Other question: When importing a TMX memory, why does it say: UTF-8 instead
of UTF-16? Aren't TMX files supposed to be UTF-16?
Wolfgang
> does it make sense to create a Memory for Terms
> AND
> an External DB (menu Tables)?
Hi Wolfgang, I'm not Igor, and I readily admit I don't understand much about external databases, but so far, it seems I don't need them anyway. Correct me if I'm wrong, but I think those databases are useful if you work on a project with several translators, or if the database is on a server somewhere.
Cheers,
Hans
--
Hans van den Broek
Schrijf-, vertaal- en redigeerwerk
Peleman Rejowinangun KG1/513
RT029 RW009
Yogyakarta 55171
Indonesia
T +62 (0)85868607333
SKYPE: hanstranslations
transl...@hansvandenbroek.eu
http://cafetran4mac.blogspot.com
Not only safe, you should do it instantly. There's a rumour of a virus for Mac that spreads via Java and Flash. The update will fix it, if there's a problem at all.
> Hi Igor
> does it make sense to create a Memory for Terms
> AND
> an External DB (menu Tables)?
External DB is an option for users who prefer to keep their terminology in
SQL Databases for various reasons (Hans v.d. B. just mentioned a few).
>>
>> They are linked if you tick the relevant boxes in the Project manager
>> window - see the Memories section in the upper part of the panel.
>> Perhaps
>> I should add one more box for the "Term memory" there.
>
> I'd second that.
I take it as a RFE.
> Yes, AAMOF, this was the case. So what is the standard internal language
> mapping of CT?
The language code - lower case.
The country code - upper case.
e.g. en-US
> Other question: When importing a TMX memory, why does it say: UTF-8
> instead
> of UTF-16? Aren't TMX files supposed to be UTF-16?
I don't think UTF-16 is a standard for TMX. Other tools experts, please
correct me if I am wrong. But I am sure that UTF-8 is sufficient in most
cases and takes less RAM.
Cheerio,
Igor
>
> On 5 Apr 2012, at 17:20, Wolfgang Schoene wrote:
>
>> Hi again Igor
>> is it safe for CT to install this http://support.apple.com/kb/DL1515
>> Java update for the Mac?
>
> Not only safe, you should do it instantly. There's a rumour of a virus
> for Mac that spreads via Java and Flash. The update will fix it, if
> there's a problem at all.
>
>
> Cheers,
>
> Hans
>
--
> I don't think UTF-16 is a standard for TMX. Other tools experts, please correct me if I am wrong. But I am sure that UTF-8 is sufficient in most cases and takes less RAM.
How do I find out if the TMX is in UTF-8? Can't find it when I open a TMX in TextWrangler.
>
> On 5 Apr 2012, at 17:58, Igor Kmitowski wrote:
>
>> I don't think UTF-16 is a standard for TMX. Other tools experts, please
>> correct me if I am wrong. But I am sure that UTF-8 is sufficient in
>> most cases and takes less RAM.
>
> How do I find out if the TMX is in UTF-8? Can't find it when I open a
> TMX in TextWrangler.
Yes, see the first line:
e.g. <?xml version="1.0" encoding="utf-8"?>
If the "encoding=" is missing, it is assumed to be utf-8.
> How do I find out if the TMX is in UTF-8? Can't find it when I open a TMX in TextWrangler.
TextWrangler gives you the encoding at the bottom left of the window. In the status bar.
Jean-Christophe Helary
----------------------------------------
fun: http://mac4translators.blogspot.com
work: http://www.doublet.jp (ja/en > fr)
tweets: http://twitter.com/brandelune
Hans, you may open the TMX in TextWrangler and look at the status bar in the lower part of TextWrangler window.
e.g. <?xml version="1.0" encoding="utf-8"?>
If the "encoding=" is missing, it is assumed to be utf-8.
Cheers
Wolfgang
Am 05/04/12 12:30 schrieb "Hans van den Broek" unter <ir...@indo.net.id>:
> Great! And it says UTF-8. Is there any chance that not everything is UTF-8?
No. Otherwise TextWrangler would have complained.
> Haven't succeeded in importing CSV glossaries so far into my
> terms memory, though.
I think you should proceed as follows (Igor?)
- Add the csv file as a glossary in Library by clicking Add Resource
- Open it in Library under Glossaries
- Convert it using Memory>Conversions>Import entries from Glossary
- Memory>Save as TMX
- Place the converted Glossary in the same folder a your terminology database (I take it that one is already in TMX format)
- Open the folder in the Project Manager so both (or more) files will show up
- In the project, select the tab with the folder, and save as [Terminology DB] (or something)
> No. Otherwise TextWrangler would have complained.
Thanks for confirming. Out of curiosity, what would TW do or notify when that's the case?
Cheers,
Cheers
Wolfgang
Am 05/04/12 13:44 schrieb "Hans van den Broek" unter <ir...@indo.net.id>:
>> No. Otherwise TextWrangler would have complained.
>
> Thanks for confirming. Out of curiosity, what would TW do or notify when that's the case?
It would show an error dialog saying that some characters are not compatible with the selected encoding. It would then offer you to select a different encoding or to display the offending characters.
> guessed you were the expert ;-)
I am NOT. That's the main problem with my blog. I will ask for advice on that problem later in this forum. In the meantime, I finally managed to write a new entry, and it's on... Language Codes (your question).
> It would show an error dialog saying that some characters are not compatible with the selected encoding. It would then offer you to select a different encoding or to display the offending characters.
Good to know. Thanks. This should mean that I don't have any UTF code problems since the error dialog never showed up. I consider myself lucky, because my main databases were my own DV databases plus DBs from clients, including in SDL and Trados. And especially the latter can cause UTF issues, so I understood.