Quantcast
Channel: ProZ.com Translation Forums
Viewing all 1783 articles
Browse latest View live

Déjà vu x2 Workgroup refusing to export 75% of translated files | re

$
0
0
Forum: Déjà Vu support
Topic: Déjà vu x2 Workgroup refusing to export 75% of translated files
Poster: mikhailo
Post title: re

I had the same problem a long time ago. Solution was simple — always export rtf with segment ID column.

Déjà vu x2 Workgroup refusing to export 75% of translated files | re

$
0
0
Forum: Déjà Vu support
Topic: Déjà vu x2 Workgroup refusing to export 75% of translated files
Poster: mikhailo
Post title: re

Seems first time I had not understand problem correctly

Do You know trick with putting "}" in the end of last segment (until DV exports)?
It' works. But resulted file always corrupted to some extent. This can be corrected manually.
Hope this way will take less time to you.

[Редактировалось 2015-04-30 07:53 GMT]

Object variable or With block variable not set | Same problem, same solution

$
0
0
Forum: Déjà Vu support
Topic: Object variable or With block variable not set
Poster: Matthias Brombach
Post title: Same problem, same solution

...just to let you (Atril and Pavel) know, that Pavel was not the only one experiencing the trouble. I had exactly the same file type of the same content (many figures), the same filter setting and I changed it accordingly as explained here. How sad that the "Live Filter" does not seem to work always. Any fixing in planning? Nevertheless, I was lucky finding the solution here :-)

Best regards,
Matthias

Embedded codes won't allow to export the translation | Create whole new project

$
0
0
Forum: Déjà Vu support
Topic: Embedded codes won't allow to export the translation
Poster: ozkariaz
Post title: Create whole new project

I once had a similar problem and did this to solve it: Send all the material to your database. Create a new project and use "pretranslate". Check code for code manually and use also "Ctr+Shift+F8". For some reason the new project gets rid of the problem, whatever it is. It's the last resource if you have checked the codes over and over and if you have used the "Ctr+Shift+F8 function with no solution. It may take time, but it will help you recover your project to export it.

A problem of termbase DVX 2

$
0
0
Forum: Déjà Vu support
Topic: A problem of termbase DVX 2
Poster: xin liu

Hello everyone, i'am trying to use DVX. I created a termbase file, when i import a glossay in it, i've forgotton to choose the target language, so in the termbase file, the source language and the target language are the same. The weird thing is when i open the file, in the layout of target language, the translation didn't show up when i choose the correct language that it should has been imported even if the language it has been assigned, the translation redisplay when i choose 'all' in target language selection item. When i try to export this termbase file, it's impossible to export the translation, the field of translation is always empty, no matter i choose the correct language it shoud be or the language it has been assigned. So what can i do to ?

A problem of termbase DVX 2 | Re-import correctly

$
0
0
Forum: Déjà Vu support
Topic: A problem of termbase DVX 2
Poster: VIP9N
Post title: Re-import correctly

[quote]xin liu wrote:
...i've forgotton to choose the target language, so in the termbase file, the source language and the target language are the same.
... So what can i do to ?... [/quote]
Delete the wrong base and import it from the glossary again. Isn't it so obvious? :-)

A problem of termbase DVX 2 | Start over again

$
0
0
Forum: Déjà Vu support
Topic: A problem of termbase DVX 2
Poster: Yolanda Broad
Post title: Start over again

I agree with VIP9N.

I assume you still have the original material. Go back and create a new termbase, making sure to select the source and target languages this time.

Then make sure you have entered the names of the source and target languages in the top cells of each of the two columns in the glossary.

Import again.

A problem of termbase DVX 2 | Import the TB again

$
0
0
Forum: Déjà Vu support
Topic: A problem of termbase DVX 2
Poster: Lbenito
Post title: Import the TB again

I agree with the other comments. Though there are various things you could, the easiest and most straight-forward solution is to import the glossary again using the correct language settings.

A problem of termbase DVX 2 | all is gone

$
0
0
Forum: Déjà Vu support
Topic: A problem of termbase DVX 2
Poster: xin liu
Post title: all is gone

i've deleted the original glossary, what i get is the termbase, that's why i need badly to export it into excel format

A problem of termbase DVX 2 | Forget this material

$
0
0
Forum: Déjà Vu support
Topic: A problem of termbase DVX 2
Poster: VIP9N
Post title: Forget this material

[quote]xin liu wrote:
i've deleted the original glossary...[/quote]

You didn't mention that in your first message. I doubt we have magic ball to guess what the real situation was :-) From the other point of view, there are always traces of source from which the original glossary came: email, trash bin, some backup or anything. Search.

[quote].., what i get is the termbase, that's why i need badly to export it into excel format [/quote]

Considering your first message "...in the termbase file, the source language and the target language are the same..." I would say you won't be able to export anything good out of it. As a rule, the databases of all CAT-makers have proprietory formats. You can apply to Atril support to help you. If not and the glossary source is not available anymore (which would be strange), just forget it. But remember to backup copies in the future.

A problem of termbase DVX 2 | thanks for all

$
0
0
Forum: Déjà Vu support
Topic: A problem of termbase DVX 2
Poster: xin liu
Post title: thanks for all

Thanks for your reply.
Finaly I've found a solution which is a hard way to export it. In the termbase, we can edit each target language, so i will choose the correct language for all the terms and the export it in normal way, the problem is that it's been edited one after another, think of about ten thousans of terms, i will finish it before my afterlife.

A problem of termbase DVX 2 | MS Access

$
0
0
Forum: Déjà Vu support
Topic: A problem of termbase DVX 2
Poster: Selcuk Akyuz
Post title: MS Access

I would open the termbase with MS Access, copy the table into Excel and do any editing there. It will be much faster I guess.

A problem of termbase DVX 2 | God bless you

$
0
0
Forum: Déjà Vu support
Topic: A problem of termbase DVX 2
Poster: xin liu
Post title: God bless you

to Selcuk Akyuz
You'are saving my life!!
It's done! I open it with MS Access, and then the next is easy.

Deja vu X3 – bugs and areas to improve | re

$
0
0
Forum: Déjà Vu support
Topic: Deja vu X3 – bugs and areas to improve
Poster: mikhailo
Post title: re

Another one way of working with true PDF.

[url removed]

DVX do not work correctly with Infix XML.

And I want to see VERY MUCH a Transit project that DVX imports correctly. :(((

[Редактировалось 2015-06-04 23:44 GMT]

Deja vu X3 – bugs and areas to improve | InFix & Transit

$
0
0
Forum: Déjà Vu support
Topic: Deja vu X3 – bugs and areas to improve
Poster: Atril Team
Post title: InFix & Transit

Hello,

You can work with Infix - you just have to create the appropriate XML filter.
A lot of our clients use that to translate PDF. Let us know if you need help with the filter creation.

You can also import Transit packages in PPX format. Currently, the references (which are language pairs, basically) are not imported but you can translate the package seamlessly. Again, if you encounter any issue doing that, please contact us and describe what the problem is, we're here to help.

Kind regards,
Atril Team

Deja vu X3 – bugs and areas to improve | re

$
0
0
Forum: Déjà Vu support
Topic: Deja vu X3 – bugs and areas to improve
Poster: mikhailo
Post title: re

[quote]Atril Team wrote:
Hello,

You can work with Infix - you just have to create the appropriate XML filter.
A lot of our clients use that to translate PDF. Let us know if you need help with the filter creation.

You can also import Transit packages in PPX format. Currently, the references (which are language pairs, basically) are not imported but you can translate the package seamlessly. Again, if you encounter any issue doing that, please contact us and describe what the problem is, we're here to help.

Kind regards,
Atril Team [/quote]

1. If a lot of clients use that — why can't You add this filter to DVX3 filter set. Despite it takes few minute to create very few peoples in LSP know about this feature.

2. I NEVER SEE TRANSIT PACKAGE where translation was not in ref files — always in ENG/DEU/RUS -extension files, that DVX3 can't export. MemoQ can do that more than two years already.

If You want help to Your users — make a work with Trados, Transit, MQ packages so flawless as in original software, without Invalid XML character ..... and other no-way-to-bypass-in-DV problems.

-----------------------------------------------------
Having translated DVX3 PRO manual in Russian (with parallel UI corrections) I want to add some notes:

1. Dumb «this is that» manual.
It's rather handbook, reference book, but not a manual with step-by-step teaching how to translate with DVX3 with further transition from simple things to advanced.
It is hard to use for newbies.
I recommend to think about changing its' structure or writing «DVX3 for Dummies» book.

Another recommendation - divide manual in parts, corresponding to expertize level and add a questions in the end of chapters.

2. more than 500 pages. Who will read them? Do You hate your potential customers?

3. Despite index is required by standards (f.e. ISO/IEC 82079-1-12), it is useless for e-document - anybody use search in Acrobat Reader, because it's quick and shows all occurrences.

4. Rare file formats can be moved into Advanced chapter. Few translators work with them.

5. Transit. See above.
When does Atril correct import of SDLXliff with bad entities, Transit XV/NTX project and lang files (.eng, .deu etc.)?

6. It's better rename Glossary to Terms and explanation (Terminology) and put in the beginning. Readers must understand terminology before they start reading.

7. Autocorrect and autotext do the same thing - replace one text with another. But it doesn't explained in text. Tricky things make an understanding difficult.

8. SGML stands for the Standardized General Markup Language. It is the result of generalizing and
then standardizing a number of Rich Text Formats (RTF) developed for word processing software
on personal computers by the International Organization for Standardization (ISO) in 1986.

SGML from RTF?? Wiki tells another story

9. tag
When working with file types other than MS Office documents processed with the MS Office
(Live) filter, Déjà Vu X3 Professional only displays translatable text—everything else is hidden.
However, in 􀀩formats such as HTML, FrameMaker, or Word (if it’s not processed with the MS
Office (Live) filter), formatting information is often embedded within a 􀀩segment, such as a
particular word in bold, cursive, or small caps. Because Déjà Vu X3 Professional cannot
automatically decide which formatting belongs to which word, it lets the translator decide where
to place this formatting information. These are "tags." If you have created a Déjà Vu X3 Professional
project for HTML, for example, you will probably have noticed that many segments contain tags
such as {142} or {835}.

Text seems to be not cohesive. Does tag need explanation like that?

10. p.15
INLINE FORMATTING — better Visual formatting

11. p.30
FILE>"""CLOSE"""
This command allows you to """open""" any kind of Déjà Vu X3 file (project, translation memory,
termbase, alignment file, XML filter). You can choose from a list of recently opened files or from
anywhere on your computer or network.

12. p.37
THE AUTOSEARCH WINDOW
A color signifies the origin of the term (by default: red=translation memory, blue=termbase, white=lexicon).
But what means Yellow on screenshot?

13. p.39
File> Options> General> Display portions from Translation Memory
But there is «SHOW portions from Translation Memory» on Screenshot

14. p.83
selecting the languages (up to 2 target languages),
AND 3 TARGET LANGUAGES ON SCREENSHOT :) :) Do not believe to own eyes.

15. p.96
The lexicon is a very useful tool, but as indicated in the light shading in the workflow chart on page
p. 75, it is an optional component.
BUT THERE IS NO ANY FLOWCHART ON P.75

16. p97-98
Unnecessary image duplicating

17. p. 104
1 Before you start to translate, select Tools> Options> General
FILE>OPTIONS......

18.
p.125
Ignore numerals—With this option, A 100 m dash would be a duplicate of A 50 m dash. ?????

19.
p.223
AUTOCORRECT
To manually add new """AutoCorrect""" entries
1 Highlight the term that you would like to add as an """AutoText""" entry.
2 Right-click on the selection and select Add Selection to """AutoText"""

20.
p.349
No IDML string in UI Resources

21.
p. 424
You can sort the order of use of the translation memories with the up and down arrows or the
right side of the field where the translation memories are listed. If you have selected..........?????

22. No example of usage. For example, Lexicon can be used to add non translatable terms. (Good idea to add lexicon of Trade Names, Trademarks etc in DVX3).
Good example - usage of lexicon for translation of Software manuals. Copy Resources to Lexicon and translate/leave/add translation and than use for translation of manual.

23. No alignment to other TM tools (p.e. - Populate (DVX3) = Copy Source to Target (Trados)).

24. With translation technology it is better to link to new ISO [phone removed] standard.

[Редактировалось 2015-06-08 19:16 GMT]

Deja vu X3 – bugs and areas to improve | infix filter

$
0
0
Forum: Déjà Vu support
Topic: Deja vu X3 – bugs and areas to improve
Poster: Selcuk Akyuz
Post title: infix filter

[quote]mikhailo wrote:

1. If a lot of clients use that — why can't You add this filter to DVX3 filter set. Despite it takes few minute to create very few peoples in LSP know about this feature.

[/quote]

AFAIK the infix filter (created by Atril) is located at C:\Program Files\Iceni\Infix6\Translation support\DejaVu

This filter file is included in the installer of Infix.

Selcuk

Deja vu X3 – bugs and areas to improve | Re

$
0
0
Forum: Déjà Vu support
Topic: Deja vu X3 – bugs and areas to improve
Poster: Atril Team
Post title: Re

Hello mikhailo,

I will try to answer all your questions/comments.

1. If a lot of clients use that — why can't You add this filter to DVX3 filter set. Despite it takes few minute to create very few peoples in LSP know about this feature.
As Selcuk mentioned, the filter is available once InFix is installed. I remember some cases where the filter would benefit from some tweaking: that is why I was offering to help you with that if necessary. We have the filter ready for anyone asking for it.
Still, adding it to our default filter list is a good idea as well. We will consider it.

2. I NEVER SEE TRANSIT PACKAGE where translation was not in ref files — always in ENG/DEU/RUS -extension files, that DVX3 can't export. MemoQ can do that more than two years already.
One can import, translate, and deliver a Transit package using Déjà Vu. It is true that as of today, references won’t be imported. This is on our roadmap.

If You want help to Your users — make a work with Trados, Transit, MQ packages so flawless as in original software, without Invalid XML character ..... and other no-way-to-bypass-in-DV problems.
That’s actually the other way around. We see a lot of illegal XML entities in XLIFF produced by other tool. Right now, Déjà Vu won’t import XLIFF with illegal XML entities because it is simply not supposed to do so. The idea behind XML is that it is supposed to make programs simple, efficient and reliable. One of the ways to do that is to force everyone to stick to the rules. If an XML file breaks the rules in some way (e.g. by having illegal entities in it) it should be rejected, because it can have disastreous consequences on the end user application (like a software, a website, etc.)
On another hand, practical reasons command us to import those – which we will implement – even though that’s not the right thing to do from a strictly technical point of view. Déjà Vu is one of the most compatible tool out there. Again, if you encounter any issue (or is DVX3 produces an XLIFF file with illegal character): write to support and we will fix that for you. That would also help us improving the compatibility.

Having translated DVX3 PRO manual in Russian (with parallel UI corrections) I want to add some notes:
1. Dumb «this is that» manual.
It's rather handbook, reference book, but not a manual with step-by-step teaching how to translate with DVX3 with further transition from simple things to advanced. It is hard to use for newbies. I recommend to think about changing its' structure or writing «DVX3 for Dummies» book.
Another recommendation - divide manual in parts, corresponding to expertize level and add a questions in the end of chapters.

Thank you for this very constructive remark.
The manual is actually divided into consistent parts, as you can see below:

The manual is not a training program, nor a “DVX3 for dummies” book: it is supposed to bring any necessary information to Déjà Vu Users.
For step-by-step teaching, please have a look at the following, amongst many other things:

    Using Déjà Vu X3: A tutorial

    Training for new DVX3 users


2. more than 500 pages. Who will read them? Do You hate your potential customers?
Again, the aim of the manual is to offer all the necessary resources in the same file. It is not necessary to read it as a whole at once. Features are indexed, on page 10 you will find very useful pointers on how to optimize your experience with the guide. I don’t think I’m supposed to answer the second part of your question.

3. Despite index is required by standards (f.e. ISO/IEC 82079-1-12), it is useless for e-document - anybody use search in Acrobat Reader, because it's quick and shows all occurrences.
This is not an e-document. It is available online, yes. But download it and you will benefit for the dynamic research which most of our users use to find relevant information. I find the index necessary in acrobat - it is actually used very often because it's dynamic: if one clicks on the reference, one will be taken to the right page instantly. I would tend to think that this is helpful, especially on large files.

9. tag
When working with file types other than MS Office documents (...)If you have created a Déjà Vu X3 Professional
project for HTML, for example, you will probably have noticed that many segments contain tags such as {142} or {835}.
Text seems to be not cohesive. Does tag need explanation like that?


It does. Questions about tags are frequent which also originated this helpful article:
How to handle tags in a project.

12. p.37
THE AUTOSEARCH WINDOW
A color signifies the origin of the term (by default: red=translation memory, blue=termbase, white=lexicon).
But what means Yellow on screenshot?

The screenshot is to be found right below the customization paragraph in order to show that colors can be changed.

18.
p.125
Ignore numerals—With this option, A 100 m dash would be a duplicate of A 50 m dash. ?????

What is wrong about that? DVX3 gives you the possibility to count two segments whose only difference is a number as duplicates, since DVX will adapt the number automatically. Usage is optional.

I want to thank you for the inconsistencies you spotted and the corrections you suggested. We will fix them in due time. On another hand, I wish you had contacted us while translating it (thank you for that, also) since we would have had the chance to correct those mistakes earlier. But it's never too late. I will contact the writer today in order to correct those mistakes. Please feel free sending us your suggestions and comments directly. We truely value user input.

Kind regards,
Atril Team

[Edited at 2015-06-10 12:41 GMT]

Deja vu X3 – bugs and areas to improve | re

$
0
0
Forum: Déjà Vu support
Topic: Deja vu X3 – bugs and areas to improve
Poster: mikhailo
Post title: re

[quote]One can import, translate, and deliver a Transit package using Déjà Vu. It is true that as of today, references won’t be imported. This is on our roadmap.[/quote]

I don't think that announcing of badly or not completely working feature is a good idea. Having tried it most of peoples are disappointed and start thinking about more reliable solution, especially when so annoing bugs like invalid XML... is not corrected few years.

[quote]That’s actually the other way around. We see a lot of illegal XML entities in XLIFF produced by other tool. Right now, Déjà Vu won’t import XLIFF with illegal XML entities because it is simply not supposed to do so. The idea behind XML is that it is supposed to make programs simple, efficient and reliable. One of the ways to do that is to force everyone to stick to the rules. If an XML file breaks the rules in some way (e.g. by having illegal entities in it) it should be rejected, because it can have disastreous consequences on the end user application (like a software, a website, etc.)
On another hand, practical reasons command us to import those – which we will implement – even though that’s not the right thing to do from a strictly technical point of view. Déjà Vu is one of the most compatible tool out there. Again, if you encounter any issue (or is DVX3 produces an XLIFF file with illegal character): write to support and we will fix that for you. That would also help us improving the compatibility.[/quote]

Replace invalid XML entities with tags in internal DVX files. The same applies to any other incompatibilities.

[quote]
Thank you for this very constructive remark.
The manual is actually divided into consistent parts, as you can see below:

The manual is not a training program, nor a “DVX3 for dummies” book: it is supposed to bring any necessary information to Déjà Vu Users.
For step-by-step teaching, please have a look at the following, amongst many other things:

    Using Déjà Vu X3: A tutorial

    Training for new DVX3 users

[/quote]

Who are target readers of this manual? Newbies - it's difficult to start with, users of other CAT - due to interface terminology difference (and NO hot-keys sets for other CAT like DVX set in MemoQ) - some things for them will be hard to understand and this creates a negative attitude to DVX.

Only DVX users who want to become more competent in DVX3 remain. Are they a main aim of the manual?

If You have different manuals — it's a good idea to give all links on forums, etc.

[quote]
Again, the aim of the manual is to offer all the necessary resources in the same file. It is not necessary to read it as a whole at once. Features are indexed, on page 10 you will find very useful pointers on how to optimize your experience with the guide. I don’t think I’m supposed to answer the second part of your question.

[/quote]

My first impression was to close manual, when I see more than 550 pages in it. It contains a lot of duplications, unnecessary links, redundant images. You can number all interface elements on the first big screenshot and later link to it as «pos. XX on fig. 1», but not putting new images in text.

[quote]
This is not an e-document. It is available online, yes. But download it and you will benefit for the dynamic research which most of our users use to find relevant information. I find the index necessary in acrobat - it is actually used very often because it's dynamic: if one clicks on the reference, one will be taken to the right page instantly. I would tend to think that this is helpful, especially on large files.

[/quote]

I propose to ask the topic's community — 1) Do you print 500+ pages manuals?
2) How do You search information in e-manuals that contains index:
a) using Find/Search in software
b) using index in document

[quote]
Ignore numerals—With this option, A 100 m dash would be a duplicate of A 50 m dash. ?????

What is wrong about that? [/quote]

Punctuation

Correctly
With this option the sentence «A 100 m dash» would be a duplicate of the sentence «A 50 m dash».

[quote]12. p.37
THE AUTOSEARCH WINDOW
A color signifies the origin of the term (by default: red=translation memory, blue=termbase, white=lexicon).
But what means Yellow on screenshot?

The screenshot is to be found right below the customization paragraph in order to show that colors can be changed. [/quote]

Changes are usually illustrated who two pictures BEFORE and AFTER

Another one problem - Do You have resource file with numbers or may be video of all screenshots with numbers of resources instead of text? Now I'm trying to correct russian UI and tired with correct/reload/check. First problem — that some inscriptions are present twice, trice etc. and it's difficult to determine which one to be corrected. Second problem — some inscription linked to 2-3-4 places but in russian it's better to divide them.
Example — resource string 20530 - «Add to TM» - on MAIN tab (where it means ADD 1 seg to TM - single operation) and on LEXICON tab (Where it means ADD whole lexicon to TM - batch operation and this is more close in sense to res. string 20531 «Add to TM» on PROJECT tab — Where it means ADD whole project to TM - batch operation)

This I can't correct with resource editor.

[Редактировалось 2015-06-11 16:29 GMT]

2-Column export not reimporting

$
0
0
Forum: Déjà Vu support
Topic: 2-Column export not reimporting
Poster: Robinshaw

Dear fellow DVXers,

I'm an experienced user of DVX, but recently encountered a new problem after migrating DVX 3 Professional (9.0.723) to a new computer running under WIN 8.1.

I can export (Share) a 2-col file as a Word .rtf file with no problems. Previous experience has shown that I can only reimport it after saving it as a Word 97-2003 doc. On my other computer with the same version of DVX running under Win 7, I had no problems reimporting. Now, when I Select Share-> Reimport-> Reimport, click on the file, and press 'Open' in Windows, and then 'OK' in the DVX Import Package dialog, a new Windows Explorer File Save Dialog opens asking me to save the file again (this never happened before). Irrespective of whether I press 'Save' or 'Cancel,' the file does not reimport.

Has anyone encountered this problem. Is it a bug? Does anyone know a workaround?

MTiA

Martin

[Edited at 2015-06-12 08:13 GMT]
Viewing all 1783 articles
Browse latest View live