Déjà Vu ideas

I suggest you ...

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. Make Déjà Vu X3 a truly 64-bit application

    All these years we're still dealing with a 32-bit application in 64-bit operating systems, with real and potential problems.

    I suspect this is the culprit behind my Déjà Vu X3 program being unable to process a 65,000-word project consisting of several .js and .xml files, with some .js files reaching 19,000 'words' and crashing the application during pretranslate every single time.

    22 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. More on-the-fly QA options

    -check if source and targe are identical
    -check target segments that are longer/shorter by .... %
    -check for inconsistent translations
    -check for unedited fuzzy matches
    -check for multiple spaces
    -check for multilple dots
    -check target segment length based on a specific number of characters (e.g. not more than 180 characters in a segment)
    - check that source and target end in the same punctuations

    19 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Trim trailing and leading spaces

    DVX should automatically trim trailing and leading spaces in segments. This would much enhance hit precentages with regard to other CAT tools, like MemoQ and Studio, which do this, and save quite a lot of QA time. An added bonus would be having less segments in the TM as there would not be one with a trailing space and one without, for instance, all else being identical.

    10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Sort hits alphabetically in "AutoSearch - Portions" pane (optional)

    Would be possible to make it possible to sort the termbase hits alphabetically in the new version?

    I keep trying to get used to it, but especially if there are a lot of hits, I find it very hard to locate things and would REALLY LOVE to be able to switch it to alphabetical.

    19 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  5. Honed Autowrite

    1) Autowrite often suggests incomplete phrases, for example finishing with an article e.g. "Compared to previous generations of aircraft, the"
    or
    "Before he knew, she"
    I believe, this could be honed for Autowrite to show larger phrases, but also those that finish with a comma, those that are capitalized etc.
    2) Autowrite should also be able to adapt the case of the suggested words from the TM. In other words, when I'm writing: "He wanted to eat a banana" and there's BANANA (all in caps) in TM, Autowrite should adapt the case and propose "banana" instead of "BANANA".
    3) It…

    20 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. 21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. 18 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Formatting in TS should reflect formatting in SS automatically.

    For example, if source is all in bold or italics, this should be set automatically in the target window without my intervention.

    20 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Punctuations changing according to the target languages

    Ex: Automatic use of french quotation marks in French target text

    11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. Improvements to project templates

    Project templates are a very powerful tool.
    They would be even better if they allowed
    1) Project-specific segmentation rules
    2) Project-specific regex rules
    3) Dynamic update of connected lexicons

    14 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  11. Bilingual/Multilingual Excel filter

    A Bilingual/Multilingual Excel file import filter capable of importing existing translations, comments and character limitation fields.

    Currently we can use External View RTF file to import existing translations and comments. And character limitation check is still possible through SQL.

    If character limitation is supported, then QA should be able to check and warn where target segments exceed a certain number of characters. Currently, we can open the project file in MS Access and copy/paste the target character limitation in Source Comments column and check with the SQL filter: LEN(Target_XXXX) > Comments
    or SQL Statement: UPDATE Pairs SET QA_XXXX = "character…

    17 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. 12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  13. Enable termbase selection for Add term pair dialog box

    In the dialog box invoked by pressing F11 in DVX3, Add Term Pair, it would be not just nice but extremely convenient to have a list of the termbases being used for the project in view, with a check box beside each termbase. As a translator, I use multiple termbases for my health care, employee manual and benefits manual projects (as well as medical projects), and I use a legal termbase, a health care termbase and a Human Resources termbase altogether in the same project. To keep terms in their respective domains, however, it would be great to be able…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. 13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. prefix matching for terms in ASr

    If "migration" is in TB, then it will find migrations, migrational, migrationist, migrator but not immigration.

    13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Change underlying db technology of TMs so we can handle bigger resources

    Have Atril ever considered switching to a better performing underlying database technology, so that users could use bigger TMs, and get better overall performance.

    I know that SDL Studio recently switched its TMs to SQLite, e.g., which is also what TMLookup uses, and CafeTran's "Total Recall" system. All of these programs are MUCH better at dealing with large amounts of data than the current Microsoft Jet (if that's what it's called) stuff Déjà Vu X3 uses. The system that DVX currently uses may have been sufficient a few years ago, but it is barely so anymore, and this is only…

    13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. Remove mandatory selection of sub-languages

    The sublanguages are of no use to me, they just create problems in case the wrong one is selected by me or a colleague. The option could be offered but made non mandatory.

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. 7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. 7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  20. Ignore the difference between smart apostrophe and straight apostrophe in term lookup/matching

    In the French language in particular the apostrophe is very heavily used. If the smart and straight apostrophes are treated as separate characters matching in memories and termbases is destroyed: terms like code de l’environnement étude d’impact avis de l’autorité environnementale etc. basically have to be entered twice once with the smart apostrophe and once with the straight apostrophe.

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Déjà Vu ideas

Feedback and Knowledge Base