CafeTran

Yep. The 'bilingual import' has been fixed. Greatz!

Someone will be happy here ;).

Hello,

I have just completed a project with the latest CafeTran version and I have noticed a few things that could be improved:

1. TM matches highlighted in the source segment editor seem to also highlight parts of words that contain the TM match.

So for example, if you ad "or" or "and" as a fragment, any word with these letters will have these highlighted, such as as "more" or "understand".

Is there a way to avoid this? Is it related to the latest prompter (auto-complete) improvements?

Screenshot: 

2. In the target segment, even small words are cut to the other line sometimes. This makes it difficult to read.

Example:

Here, the word is "simplement", the t appears in the next line. This happens for small words such as "qui" Which appears as:

qu

i

This may also be related to the prompter update, and suggestions in the middle of a word.

3. Finally, there has been an issue with an Excel file export which lost paragraph marks within one cell, where I have used the split feature, but I prefer to open a ticket for this as I need to attach the project files.

Jean

> I don't know if this also happens with Glossaries.

It does.

I'm sure I've read this somewhere, but I can't find where and I think it's an issue.

When translating from French into Spanish, the French "élision" is considered as a whole word, so termbases don't recognize it as a word (nor the QA). Example:

L’élément - L’élision - L’invention and so on are not recognized even if I record "élement", "élision", "invention". I usually use this (') as an apostrophe for French, but my project manager sends me the documents with this (’) instead (I guess it's due to Abbyy FineReader, as we work with PDFs converted into .docx files).

Read here and there (the whole thing, not only the first pages).

Short from here: 

The user needs to remove the curly apostrophe from the "Do not match" list in Edit > Preferences > Memory tab to have it matched. This should also work for straight ones.

And just one last thing to fine tune Statuses, when a segment is "Checked", why not to "Uncheck" the segment if we type something on it after we "checked" it? This could avoid, for example, typing by mistake a checked segment and actually consider it as checked and not edited.

OFFTOPIC: isn't it AMAZING we, the users/translators, are shaping the software on the go because the developer is just here, listening all the time? This is priceless.

>OFFTOPIC: isn't it AMAZING we, the users/translators, are shaping the software on the go because the developer is just here, listening all the time? This is priceless.

A) I don't think that this is off topico.

2. Yep, that's what amazed us too, years ago :).

III/. Spread the word.

Igor: Added the "es" language code (neutral - without a country variant) for Spanish spoken in the US.

Would it be possible to let the user choose whether to add the country variant to the language code upon file export? I always find myself deleting it.

Thank you

A solution is to use multiple-file projects, even for one file. The exported folder bears the language code, the contain files do not.

Jean: A solution is to use multiple-file projects, even for one file. The exported folder bears the language code, the contain files do not.

This is an even better solution, thank you. I didn't know it exist at all. I'll try it out.

Hi again Jean, 

I followed your suggestion, but the file in the exported folder still has the country code. Does your CTE behave differently?

Try using Project > Export all documents, instead of "Export current document".