Atril Team wrote:
XLIFF external views are not meant to be used in DVX3. They are intended for third-party CAT tools, and are designed for this purpose only. When working when another DVX3 user, one has to use Satellite projects, which are meant to share the work between DVX3 users.
If you have to translate some DocBook multihundreds small xml docs, You will understand how good is to create xlf from initial projects and to translate them in another project with only few files.
There are another situations where such usage is preferred. xlf is smaller than satellite. If You don't add into project lexicons, own DB - satellite is not very helpful.
Xlf (or TMX as simple project file) - is a very preferred way to have some not big TM to see translation in full context or have an easy access to.
Guaranteed locked (or just locked segments) are imported in third-party CAT tools and displayed as locked (and the opposite is also true: DVX3 will import locked segments from third-party CAT tools and display them as such). This is the intended behavior. They won't be imported in DVX3 because of the way we deal with the translatable="no" attribute (we use it for different purposes). Then again, XLIFF EVs are not meant for interoperability with DVX3, but with other tools. Using XLIFF external views instead of satellite projects is bad practice.
So why You DO NOT Inform USER ABOUT his «bad» behaviour and expected problems?
5. If You try to translate xlf in new project to the end and export - You got message DVX IS UNABLE TO EXPORT..... Own files......
Here the bug #2 (Why DV can't export you own xlf and also any tip WHY)
That should not happen. Please send the XLIFF external view to firstname.lastname@example.org
and we will check what happens and fix it.
But it does. I was very surprised when I see in exported 538 seg xlf only 228 segs (other were guaranteed)
Waiting for GOTO NEXT EMPTY function
Feel free creating that filter using SQL under File>Options>SQL.
Give that filter a name ("Next empty" for instance) then click on "Build Expression".
Check the "Emty" box under "Translation Status", click "OK" then "Add" and you are done!
I'll try, but I'm not a programmer
Do you know that you can also open single files on their own and that files names are displayed in the lower bar of the interface, so that you know which file you are translating exactly?
if only F F - nice, can look below to see filename
but if so FFFFFFFFFFFFFFFFFFFFFFFFFFFF
or so FFFFFFFFFFFFFFFFFFFFFF
(unfortunately i can't make them of different color)
But If filename is the same but only format differs - xml, html, doc, sdlxliff, xlf, txt
2) reimport back in single language align mode of finished translated files (from their original formats), for example, after external editing/reviewing.
I am not sure I understood this one. Can you elaborate?
Feel also free aligning the final version of the exported file with the source file.
It's easy to understand. It's impossible, even with a preview, reviewing files in bilingual table so good as in original format with all illustrations etc.
Sometimes changes may be very significant. I want to have more easy way to put them in TM, than align.
Mikhailo, our Support Team is also available to address any questions or doubts about Deja Vu. This service is free of charge for users who purchase our software either via the TGB on www.proz.com
or through the web store on www.atril.com
(Proz.com users are entitled to an immediate 20% discount).
[Edited at 2015-09-22 11:16 GMT]
From experience - the problem solving by producers is not very quick as somebody wants to see ready translation. So in 99% cases I try to find and find solution on different forums and usergroups.
So I post problem (and solution if I know) here so that another users can solve such problem in the future.
So from this viewpoint, the good idea is to post here Atril's solutions of the problems.
[Редактировалось 2015-09-22 15:34 GMT]