Технические форумы » Wordfast support »
Страниц в теме:   < [1 2]
Inconsistent term recognition from glossaries
Автор темы: Khadhé
Khadhé
Khadhé
Local time: 23:13
английский => французский
Автор темы
I never converted my glossaries from UTF-8 to Unicode with WF Mar 8, 2013

I think you are misinterpreting my posts:
"In WFC is no tool to convert UTF-8 to Unicode"

I never converted my glossaries from UTF-8 to Unicode using WF.

I mistakenly mentioned UTF-8 when in fact - yes you're correct on that point -, WF uses LE16.
My glossaries were initially created in the default character encoding format that WF uses.
I then used WF tool to rewrite all my glossaries in Unicode.

I may miss something bu... See more
I think you are misinterpreting my posts:
"In WFC is no tool to convert UTF-8 to Unicode"

I never converted my glossaries from UTF-8 to Unicode using WF.

I mistakenly mentioned UTF-8 when in fact - yes you're correct on that point -, WF uses LE16.
My glossaries were initially created in the default character encoding format that WF uses.
I then used WF tool to rewrite all my glossaries in Unicode.

I may miss something but why would I have to go through Word Pad to convert glossaries that are already in WF unicode format?

EDIT: I actually just tried to open each glossary with Notepad. On Save As, Notepad proposes as default format "unicode" in the field, meaning, I suppose, that both glossaries are indeed already in unicode.





[Edited at 2013-03-08 19:56 GMT] ▲ Collapse
 
Milan Condak
Milan Condak  Identity Verified
Local time: 08:13
английский => чешский
Believe or look at reality Mar 8, 2013

5. Open your file in NotePad, try Save as and you CAN SEE your current encoding.

That is OK. Now you have to look if fonts look right in this encoding. The fonts can be bad, I can show you, how it can looks.

http://www.condak.net/tmx/wfconverter/cs/01.html

That is all.
For me it works since 2001.

Milan

Khadhé wrote:

EDIT: I actually just tried to open each glossary with Notepad. On Save As, Notepad proposes as default format "unicode" in the field, meaning, I suppose, that both glossaries are indeed already in unicode.


[Upraveno: 2013-03-08 20:29 GMT]
 
Khadhé
Khadhé
Local time: 23:13
английский => французский
Автор темы
:) Mar 8, 2013

"believe or look at reality"

I don't "believe" anything.

I just said I opened the files with Word Pad. I saved as unicode, as proposed (because it is already unicode). Of course, all characters look correct under Word Pad. I know what it looks like when the character encoding is not correctly interpreted.

Thanks for trying to help. Have a great day.
 
Milan Condak
Milan Condak  Identity Verified
Local time: 08:13
английский => чешский
NotePad vs. WordPad Mar 8, 2013

I do not believe in WordPad in case of the encoding, only to NotePad.

Milan

Khadhé wrote:

"believe or look at reality"

I don't "believe" anything.

I just said I opened the files with Word Pad. I saved as unicode, as proposed (because it is already unicode).


 
Khadhé
Khadhé
Local time: 23:13
английский => французский
Автор темы
yes agreed Mar 8, 2013

I wrote WordPad when I am actually using Notepad. Sorry.
 
Страниц в теме:   < [1 2]


To report site rules violations or get help, contact a site moderator:

Модератор(ы) этого форума
Natalie[Call to this topic]
Marco Ramón[Call to this topic]
Prachya Mruetusatorn[Call to this topic]

You can also contact site staff by submitting a support request »

Inconsistent term recognition from glossaries







Trados Business Manager Lite
Create customer quotes and invoices from within Trados Studio

Trados Business Manager Lite helps to simplify and speed up some of the daily tasks, such as invoicing and reporting, associated with running your freelance translation business.

More info »
Pastey
Your smart companion app

Pastey is an innovative desktop application that bridges the gap between human expertise and artificial intelligence. With intuitive keyboard shortcuts, Pastey transforms your source text into AI-powered draft translations.

Find out more »