| Stron w wątku: < [1 2 3 4] | DJV X2 areas to improve (wishlist) Autor wątku: Pavel Tsvetkov
|
|---|
| Thanks for your insights | Jan 20, 2014 |
Dear all,
Thank you all for your comments about DVX2. We tend to remain quiet on Proz but we always keep an eye on this forum and read you with great care.
At this point I would like to answer some of your comment/question/suggestion:
1. "Introduce whitespace visualization"
This has been done in DVX3
2. "Introduce way to make font bigger in Autosearch windows (Segments and Portions)"
This is already possible in DVX2.
Go on "Tools">"... See more Dear all,
Thank you all for your comments about DVX2. We tend to remain quiet on Proz but we always keep an eye on this forum and read you with great care.
At this point I would like to answer some of your comment/question/suggestion:
1. "Introduce whitespace visualization"
This has been done in DVX3
2. "Introduce way to make font bigger in Autosearch windows (Segments and Portions)"
This is already possible in DVX2.
Go on "Tools">"Options">"Display" and select "Secondary" from the Window Type dropdown list.
We might change the texts here to make it clearer.
3. "It would be nice if a term entered with a capital, could also be automatically recognized in the source and offered by Autowrite with a small letter."
This will be developped in DVX3.
4. "Spell-checking should be done in real-time (while typing – or after you stop typing and 2 seconds have passed, like in Trados Studio). Even Microsoft Word has this function."
This has been done in DVX3.
5. "It would be nice if DVX could underline, highlight or otherwise mark recognized terms in the source (like in Trados Studio). If not I have to always check in the AutoSearch - Portions window to see which are the recognized terms and what translations have been offered."
This is defintely on our roadmap and will be developped in DVX3.
6. "Is it possible to export the finished translation for just one of two files in a project (just the translation, not a table with side to side source and target)? If not, this should be implemented."
Yes it is. Simply right-click on the file you want to export in the project explorer, and click on "Export".
7. "Is there a function available like the 'Review' and 'Sign off' in Trados (segments are checked manually by the reviewer and marked with a different sign)? This is important, because when I review work in DJV x2, there is no way to tell which segments have been reviewed – and which not."
DVX3 allows you to chose between "Translated", "Proofread" and "Validated" status.
8. "When doing Find and Replace, it would be helpful if DJV could return information on how many substitutions have been made (if any)."
This has been developped in DVX3.
9. "Why cannot Google Translate and Microsoft Translator be used simultaneously like in Trados?"
It has been possible for quite some time now in DVX2.
10. "I would really like DVX2 to be more selective when importing DOC/DOCX files with regard to some useless codes like codes for spelling errors. It would also be great if there was at least some WYSIWIG formatting, like bold, italics, underline, colours etc instead."
This has been developped in DVX3.
11. "get a button to take over numerals manually from the source segment into the target like, yes, like in Trados."
This is on our roadmap.
12. "when the window of the spell-checker is closed before ending the checking, you lose your current position and have to conduct a manual search (if you remember what to search for)"
Right, this has been reported. This is to be fixed.
13. "Segments with warnings stay that way even after editing, re-confirming them"
This is normal behaviour, but i understand your point. You can use "Delete QA warning" or "Delete all QA warnings" to make it/them disappear.
14. " if a term is present with several different translations in the term base (or as part of a phrase), unless all translations are used at once in a single segment, Déjà vu X2 shall consider it a case of term missing"
Could you please develop ? I have not been able to reproduce this behaviour.
15. "Batch Find and Replace does not tell you the count of hits/replaces"
This has been fixed in DVX3.
16. "Currently, many of the dialog boxes used in DVX2 are not expandable and users need to use the scrollbars to get access to the information they need."
This has been fixed in DVX3.
17. "It should be possible to search for the subjects in the Subjects List in the New Project Wizard"
This requires a significant change in the code and a huge amount of work. We have not prioritized it so far.
18. "Include some (most common) SQL statements"
We need to define what are the most common ones, any suggestion is welcome. We have been reluctant to do so in the past because of the "risk" it implies.
However, feel free to suggest the 5 you would like to have by default. If we manage to get consensus on the most used and required, we'll be able to implement it.
19. "The ability to mark proofed segments differently from translated segments"
As stated above, this has been done in DVX3.
20. "Real-time preview"
This has been done in DVX3.
21. "For the IDML filter, add the possibility to exclude hidden layers from extraction."
This is a great idea, thank you. This one our roadmap for future development.
Again, thank you all !
Etienne ▲ Collapse
| | | | mikhailo
Local time: 06:27
angielski > rosyjski
+ ...
Etienne Tessier wrote:
XXXX
1. IMHO ----- The MOST IMPORTANT today for DV feature - ABILITY TO WORK FLAWLESSLY WITH PACKAGES FROM OTHER TMs, first of all TRADOS 9/11/14, MQ, TRANSIT XV/NXT, not pretranslated ttx/sdlxliff, SDLXliff with bad entities.
2. Problem of disappearing of some text before first or after last tag in segment
Example (tags of BOLD text)
Source :{1}XXX{2} declares
Translation :Company {1}XXX{2} declares
Export XX declares
3. What about comfortability of working in DV? I'm afraid that DV3 requires latest i7 with 32GB RAM and SSD-raid to work without lags with all these visual features. (as it was with AERO interface in Windows)
4. «Do not Import Hidden Text» from DOCX converted from Doc does not work correctly. For compatibility with Trados there should be an opportunity import/do not import some styles from doc/docx.
5. Filter for languages with inflexion
example
ENG
RMB (right mouse button) menu
cat-> Filter->cat
cat, cats
RUS
новый->Filter->новый
нов*, нов**, нов***
where * - any cyrillic letter
with opportunity to make own rules (first of all for languages that Atril can't manage)
6. Proposed search feature similar to filter
RMB
cat ->Filter
Search->In Google
->In wiki
(with default browser or for IE, Chrome, FF, O) - may be with opportunity to define own browser and site to search, for example BAIDU)
| | | | Pavel Tsvetkov 
Bułgaria
Local time: 06:27
Członek ProZ.com
od 2008
angielski > bułgarski
+ ...
Moderator tego forum NOWY TEMAT | More frequent Atril responses needed | Jan 21, 2014 |
Dear Etienne,
Thank you for your post and your clarifications.
I would like to see more frequent and pronounced presence by Atril representatives on this forum. I started this thread (which proved to be very popular with www.proz.com users) on Aug 1, 2012, and it is only now, 1.5 years later that an Atril representative has addressed our concerns, and made his presence known.
Tr... See more Dear Etienne,
Thank you for your post and your clarifications.
I would like to see more frequent and pronounced presence by Atril representatives on this forum. I started this thread (which proved to be very popular with www.proz.com users) on Aug 1, 2012, and it is only now, 1.5 years later that an Atril representative has addressed our concerns, and made his presence known.
Trados has dedicated reps on www.proz.com to monitor and unofficially mediate the forums, and Atril is lagging behind in this respect.
The feeling is that opinions by everyday users and paying customers of Deja Vu matter little to Atril, and this (true or not) is bad for both sides.
Kind Regards,
Pavel Tsvetkov ▲ Collapse
| | | | | More frequent Atril responses indeed | Jan 21, 2014 |
Dear Pavel,
As a new year resolution, I can assure you we will definitely spend more time on Proz forum.
It is true we remained quiet, but we also implemented a lot of the features that were requested here.
@Mikhailo: i'm adressing your requests and let you know what we plan to do.
About your concern, let me give you the technical requirements:
Minimum hardware requirements
Processor
1GHz or faster 32-bit ... See more Dear Pavel,
As a new year resolution, I can assure you we will definitely spend more time on Proz forum.
It is true we remained quiet, but we also implemented a lot of the features that were requested here.
@Mikhailo: i'm adressing your requests and let you know what we plan to do.
About your concern, let me give you the technical requirements:
Minimum hardware requirements
Processor
1GHz or faster 32-bit (x86) or 64-bit (x64) processor
Memory
1GB RAM
Recommended hardware
Processor
1.5GHz or faster dual-core processor
Memory
2GB RAM
Kind regards,
Etienne
[Edited at 2014-01-21 10:19 GMT]
[Edited at 2014-01-21 10:20 GMT] ▲ Collapse
| | |
|
|
|
| Response time by Atril | Jan 21, 2014 |
Pavel Tsvetkov wrote: ... I started this thread (which proved to be very popular with www.proz.com users) on Aug 1, 2012, and it is only now, 1.5 years later that an Atril representative has addressed our concerns, and made his presence known.
You must have missed Etienne's first answer from august 9, 2012. That is not 1.5 years, but 1.5 weeks after the date of your initial question
Leo
| | | | mikhailo
Local time: 06:27
angielski > rosyjski
+ ...
Etienne Tessier wrote:
@Mikhailo: i'm adressing your requests and let you know what we plan to do.
About your concern, let me give you the technical requirements:
Minimum hardware requirements
Processor
1GHz or faster 32-bit (x86) or 64-bit (x64) processor
Memory
1GB RAM
Recommended hardware
Processor
1.5GHz or faster dual-core processor
Memory
2GB RAM
DV2 often lags on more powerful configs. Do You convince me that DV3 with visual features will work good enough on proposed config? May be - with empty TM and simple and short text files in project.
Recommended config - it's a configuration where DV3 will work without lags with all autofeatures and visual features ON (autocomplete, autosend to TM, autopropagate etc) with 100000 seg TM and project with 10 different filetypes and filesizes. One if files should have at least 10000 segs.
I recommend You to make SUCH TEST PACKAGE and TEST TM to demonstrate how NEW DV3 works.
Project should have 30+% of 100% matches, 30+% fuzzy and the rest to translate.
You can get TM and examples of documents from EU laws site.
You can use them to demostrate new features so EVERYBODY can see and understand how You determine that new versions are better than old.
Feature to implement
CAD files filters - first of all for AutoCAD dwg/dxf files (may be in cooperation with Autodesk) with 3-4 export options (Only Transit can work with DXF. So You can get the valuable advantage over competitors).
Export Options
1. Replace original text with translated in the same layer
2. Add translation after original text in the same layer
3. Add translation into new layer and delete/make invisible/move to one layer and make the invisible original text
4. Simply add translation to new layer
with checkbox «save all text as MTEXT»
Don't forget about opportunity to join ACAD TEXT into MTEXT in DV.
[Редактировалось 2014-01-22 09:30 GMT]
| | | | | Everyone knows that... | Jan 25, 2014 |
DV2 often lags on more powerful configs. Do You convince me that DV3 with visual features will work good enough on proposed config? May be - with empty TM and simple and short text files in project.
... minimum and even recommended hardware requirements should probably be doubled for comfortable working. You probably can't even buy a computer any more with less than 4GB RAM.
I haven't tried DVX3 with a 2GB configuration but I can assure you that runs quite happily with 4GB which is really what comes as standard in any computer less than 3 years' old.
What wasn't mentioned in the sneak preview is the speed of the new Office filter.
In the summer, one of my customers sent me a Word file that SDL Studio 2011 refused to import (120 pages, 17,000 words, lots of tables and graphics).
At the time, I managed to import it into DVX2 in about 5-6 minutes.
I just tried to import the same file into memoQ 2013 and had to kill the process after 15 minutes when it seemed stuck a 1/5th of the way along the progress bar with the computer's fan racing.
DVX3 imports the same file with the new Word filter in 30 seconds!
Recommended config - it's a configuration where DV3 will work without lags with all autofeatures and visual features ON (autocomplete, autosend to TM, autopropagate etc) with 100000 seg TM and project with 10 different filetypes and filesizes. One if files should have at least 10000 segs.
DVX3 (not DV3 by the way, which goes back to 2002) will run quite happily with such a project and TM, unlike SDL Studio 2014 (see http://groups.yahoo.com/neo/groups/TW_users/conversations/topics/66723).
| | | | mikhailo
Local time: 06:27
angielski > rosyjski
+ ...
Olaf Carlson wrote:
Now I have spent a lot of Euros on my DVX2 Workgroup to guarantee file interchangeability With Trados 2014 - which is Limited and has cost me a lot of extra work and money due to having to iron out errors on borrowed time. Shall I have to Shell out even more Money for an X3 upgrade just to get a software version that does just what the old one (X2) should have done in the first place? I don't think it is fair.
Voice of truth. Atril are thinking like No1. It's a problem.
David Turner wrote:
... minimum and even recommended hardware requirements should probably be doubled for comfortable working. You probably can't even buy a computer any more with less than 4GB RAM.
I haven't tried DVX3 with a 2GB configuration but I can assure you that runs quite happily with 4GB which is really what comes as standard in any computer less than 3 years' old.
Now DVX2 runs on Intel dualcore+4GB so I'm not quite happily, especially with big TMs and autofeatures ON.
In the summer, one of my customers sent me a Word file that SDL Studio 2011 refused to import (120 pages, 17,000 words, lots of tables and graphics).
At the time, I managed to import it into DVX2 in about 5-6 minutes.
I just tried to import the same file into memoQ 2013 and had to kill the process after 15 minutes when it seemed stuck a 1/5th of the way along the progress bar with the computer's fan racing.
DVX3 imports the same file with the new Word filter in 30 seconds!
I haven't seen DVX3, but I had seen a lot of doc (no docx) that makes DVX/DVX2 hanging or which imported in DVX/X2 3-4-and more hours in comparison with few minutes in MQ/TRD.
I've seen DVX2 can't manage correctly hidden text in docx, converted from doc.
I've seen a lot of SDLXLIFF with bad XML entities that DVX2 can't import.
I've seen a lot of corrupted exported docs with all correct tags and no error indications (with }}}} solution of problem)
But no one say when these bugs will be corrected. Is it the time to stake on MQ?
| | |
|
|
|
| Post removed: This post was hidden by a moderator or staff member for the following reason: Empty post
| | This post began with DVX2... | Feb 10, 2014 |
I haven't seen DVX3, but I had seen a lot of doc (no docx) that makes DVX/DVX2 hanging or which imported in DVX/X2 3-4-and more hours in comparison with few minutes in MQ/TRD.
... but we're now talking about DVX3, right? I can only reiterate that, according to the tests I've done so far, the DVX3 new Word (Office) filter imports both doc and docx files significantly faster than memoQ and with fewer tags or other problems.
| | | | Pavel Tsvetkov
Bułgaria
Local time: 06:27
Członek ProZ.com
od 2008
angielski > bułgarski
+ ...
Moderator tego forum NOWY TEMAT | Etienne, item 14 | Apr 5, 2014 |
Dear Etienne,
Regarding 14. above: " if a term is present with several different translations in the term base (or as part of a phrase), unless all translations are used at once in a single segment, Déjà vu X2 shall consider it a case of term missing"
1. Example 1:
I am currently working on a translation that includes the term Дружеството-майка [the Parent company]. In my termbase I have entered the terms дружеството [the company] and ... See more Dear Etienne,
Regarding 14. above: " if a term is present with several different translations in the term base (or as part of a phrase), unless all translations are used at once in a single segment, Déjà vu X2 shall consider it a case of term missing"
1. Example 1:
I am currently working on a translation that includes the term Дружеството-майка [the Parent company]. In my termbase I have entered the terms дружеството [the company] and Дружеството-майка [the Parent company]. In my translated segment I have used the correct term 'the Parent company' which corresponds to the source term.
However, Deja vu X2 Workgroup 8.0.641 flags a warning that I have not used the correct term for дружеството [the company].
2. Example 2:
Source Segment: Основните характеристики на предлагането на морски специалисти са [The main characteristics of the supply of maritime professionals are]
Terms in the termbase: морски специалисти = maritime professionals, специалисти = experts
The problem: I have translated the segment as shown above: The main characteristics of the supply of maritime professionals are.
However, Deja vu X2 Workgroup 8.0.641 flags a warning that I have not used the correct term for специалисти = experts.
Your comment?
Best regards,
Pavel Tsvetkov
[Edited at 2014-04-05 08:48 GMT] ▲ Collapse
| | | | Pavel Tsvetkov
Bułgaria
Local time: 06:27
Członek ProZ.com
od 2008
angielski > bułgarski
+ ...
Moderator tego forum NOWY TEMAT
Here starts the infamous months-to-years wait for a response from Atril...
| | |
|
|
|
| Regarding TB QA check | Apr 14, 2014 |
Pavel Tsvetkov wrote:
Here starts the infamous months-to-years wait for a response from Atril...
Dear Pavel,
Sorry for the wait, I thought Daniel had gotten back to you during Proz event.
This is not normal behaviour, and it will be fixed.
Best regards to you all,
Etienne
| | | | | Stron w wątku: < [1 2 3 4] | To report site rules violations or get help, contact a site moderator: You can also contact site staff by submitting a support request » DJV X2 areas to improve (wishlist) | 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 » |
| | Anycount & Translation Office 3000 | Translation Office 3000
Translation Office 3000 is an advanced accounting tool for freelance translators and small agencies. TO3000 easily and seamlessly integrates with the business life of professional freelance translators.
More info » |
|
| | | | X Sign in to your ProZ.com account... | | | | | |
Login to reply/comment 
