Another BUG
Thread poster: mikhailo

mikhailo
Local time: 12:28
English to Russian
+ ...
Oct 7, 2015

When import EN-RU Text (in Win, UTF 8, UTF 16 LE with signature) or XLS into DVX lexicon - text in import window LOOK LIKE EN - JAPANESE (with hyeroglyphs) instead of russian text.
It's confusing. Later correct encoding for russian can be set, but peoples must go through hyeroglyphs first. (I've done that oly after I've tried all possible russian encodings (see above).

And why DVX3 does not have xlsx between file extensions for the import of lexicon?


 

Atril_TEAM
France
Local time: 11:28
Not a bug Oct 9, 2015

Hello mikhailo,

When importing external data into a TB the proper encoding page might no be recognized automatically.
That is why the preview window is available during this process: to let you adjust it.

I always recommend to use Unicode in case the characters are not displayed properly.
This is shown in this webinar (starting from 14:33):
http://www.atril.com/content/6-recorded-training-advanced-déjà-vu-users-3607

Regards,
Atril TEAM


 

mikhailo
Local time: 12:28
English to Russian
+ ...
TOPIC STARTER
re Oct 9, 2015

Atril_TEAM wrote:

Hello mikhailo,

When importing external data into a TB the proper encoding page might no be recognized automatically.
That is why the preview window is available during this process: to let you adjust it.

I always recommend to use Unicode in case the characters are not displayed properly.
This is shown in this webinar (starting from 14:33):
http://www.atril.com/content/6-recorded-training-advanced-déjà-vu-users-3607

Regards,
Atril TEAM


I agree with You but I can't understand why in standard installaton it is set to Japanese JsXXXXXXX.

But to solve this problem absolutely correctly

1. Use only one encoding, for example Unicode 16 LE and WARN user before (or use default and WARN)
2. Add in font choosing field in first screen of import master, as it is done in ALL OTHER SOFTWARE with the same functions.

regards


 

Atril_TEAM
France
Local time: 11:28
Agreed Oct 9, 2015


1. Use only one encoding, for example Unicode 16 LE and WARN user before (or use default and WARN)
regards


I do agree with you. That would be even easier for everybody.
I'll pass it along to our R&D team.

Kind regards,
Atril Team


 


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

Moderator(s) of this forum
Pavel Tsvetkov[Call to this topic]

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

Another BUG

Advanced search






Wordfast Pro
Translation Memory Software for Any Platform

Exclusive discount for ProZ.com users! Save over 13% when purchasing Wordfast Pro through ProZ.com. Wordfast is the world's #1 provider of platform-independent Translation Memory software. Consistently ranked the most user-friendly and highest value

More info »
SDL Trados Studio 2019 Freelance
The leading translation software used by over 250,000 translators.

SDL Trados Studio 2019 has evolved to bring translators a brand new experience. Designed with user experience at its core, Studio 2019 transforms how new users get up and running, helps experienced users make the most of the powerful features, ensures new

More info »



Forums
  • All of ProZ.com
  • Term search
  • Jobs
  • Forums
  • Multiple search