|Summary||Description||Existing functionality? Please provide a description.||Note|
|1||1||Make importing TMX easier||Currently, importing TMX from other CATs is anything but easy or intuitive, and involves the following steps:|
1. Export to TMX
2. Import to Trados
3. Export to TXT
4. Change TXT encoding manually to UTF-8
5. Import to DVX2
If I don't perform steps 2-4, most CE characters don't import correctly (are garbled), no matter which encoding I select in the TMX Import Wizard.
|Selcuk Akyuz: Did you try Unicode?|
Stanislav: Yes, that was my first option. CE characters still garbled.
Martin Janda: OK, next time, try saving the .txt file as ANSI. But personally, I have experienced very rarely problems with importing .tmx files in the past. Unless they come from a CAT tool that produces mangled .tmx files...?
Stanislav: I'm afraid this is not the case, Martin. The TMX was validated and imported w/o any problems in all the other CATs. So this has to be a problem in DVX.
|3||1||Make dialog boxes expandable||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 is not very ergonomic and slows down many project and database management tasks.
|Selcuk Akyuz: that was reported to Atril|
|5||1||Include the option to show whitespace characters||This is really a must and I'm surprised to see that this hasn't been implemented yet, although it's a feature that's been called for by many users for quite some time.|
One more hint: the "degree" character (°) should be distinguished from the non-breakable space character, e.g. by using red for nbsp.
|11||1||Auto-adjust the cell height in the AutoSearch - Portions pane||If I adjust the font size for secondary windows, e.g. to Tahoma 11pt., and the translation unit is long enough, the second line does not fit within the cell height.|
|8||2||Make subjects searchable||It should be possible to search for the subjects in the Subjects List in the|
New Project Wizard. Also, using a combo box with multiple selection rather than a drop-down list would be advisable, because a single project may involve multiple subjects.
|Selcuk Akyuz: Good idea for the first one. I will add this feature request. As for combo box, possibly the results will not be good for Subject/Client prioritization in AsR window.||Thanks, Selcuk.|
|12||2||Include multiple selection in Project Explorer||Currently it is not possible to use multiple selection in the Project Explorer, which is a disadvantage e.g. in cases where I want to export just a selection of files. This can only be done in the Advanced Project Explorer.|
|4||3||Include some (most common) SQL statements||Including some of the most common SQL statements in the GUI would make it easier for newbies to find their way around DVX2.||Selcuk Akyuz: IMO, SQL commands are not for newbies, if you make a mistake there is no way to undo it. But there are some useful SQL commands/filters in the help file and many shared at the Yahoo group. Anyway, this was reported to Atril as well.|
Stanislav: This is a topic for discussion. I'm not a newbie to computers or to CAT tools; I'm a noob to DVX2, but I still need to perform some database management tasks. Why do these tasks rely on writing SQL statements instead of including them as buttons with captions, action descriptions and user warning? In Trados Studio, I can perform the same tasks through a set of dialog boxes with combo boxes, drop-down lists and text fields. And these result in SQL statements as well.
Moreover, as much as I can see your point, any decent computer user makes a backup before doing anything that can't be undone. Also, the developer may set up a user-defined backup routine for "dangerous" SQL statements.
Selcuk Akyuz: They are available under Segment Selector and QA menu. No need to write them everytime you need them. Just write (or copy-paste) and then store.
Stanislav: Selcuk, this is what I call user-friendly database maintenance options:
The result is still an SQL query, but the user doesn't have to have extensive knowledge of SQL, nor does he have to search the web for commands written by somebody else (without proper knowledge of SQL, I can't even check if the SQL statement does what the author says it should do).
|6||3||Highlight words with a note||When a note is attached to a portion of the translated text (one, two or several words), those words should be highlighted or otherwise marked||Selcuk Akyuz: additional features for the "comments" you want, only SDL Studio (and SDLX?) use it. Personally I prefer segment level comments.||Credits: Pavel Tsvetkov|
|7||3||The ability to mark proofed segments differently from translated segments||It should be possible to see at the first sight whether a segment is in the "Translated" or "Proofed" status.||Credits: Pavel Tsvetkov|
|9||3||Real-time preview||It should be possible to get a real-time preview of for at least MS Office files. The "Context" pane shows the code surroundings, but tells the translator little about where in the document he/she currently is.||Leo te Braake: Some people love it, some hate it. I do not expect Atril to give this any kind of priority.... |
Martin Janda: Nope. Who knows what Atril gives priority, apart from the Team Server. But there is an easy workaround. Set up a macro (HotKey or MacroExpress) to invoke the relevant Office app and look the hilited word(s) up for you. I have been using this for years and it works like charm.
|13||4||Provide a GUI to set up basic and intermediate SQL queries and commands||Currently, it is nearly impossible to perform intermediate TM and TDB management without some knowledge of SQL. Therefore, it would be nice if DVX2 could feature an interface to set up at least some basic and intermediate SQL queries and commands. |
The reason why I have assigned lower priority to this item is that more experienced DVX users are more familiar with SQL and usually have their set of commands, created over time.
|2||5||Make Toolbar buttons larger and more intuitive||The current Toolbar buttons are too tiny, especially on larger screens. Moreover, most of them are anything but self-explanatory.||Selcuk Akyuz: Tools>Customize>Options>Large Icons||One can be blind sometimes. Thanks, Selcuk, my bad.|
|10||5||Mark pretranslated rows which have capitalization different from source rows NOT as exact match||The current behaviour is creating low quality translations on GUIs using Title Case||For example: "Source Row" is pretranslated as "source row" and marked as an exact match, which it is not!|
Selcuk Akyuz: I don't use pretranslate so I cannot verify if it is a bug or not but in any case I would use a SQL filter (until it is fixed by Atril)
|14||4||Finally make it possible to set up a project with the keyboard only.||At some point, Atril made *most* but not all steps in setting up a project possible to be completed with the keyboard. Unfortunately, one step in the project wizard (databases) does not allow tabbing to the "Next" button. I am forced to use the mouse, although all other screens allowed tabbing.|
|15||4||For the IDML filter, add the possibility to exclude hidden layers from extraction.||Some InDesign files may contain multiple layers with multiple languages||Credit: Walter Weyne|