CAT-Tools/DéjàVu X/Slashes: import and export issues

Added: --Loek van Kooten 15:34, 5 February 2007 (UTC)

Version: 7.0.284

System: Windows XP SP2 (Office 2000)

Description: After import into DVX, single slashes are displayed as double slashes.

Description: After export to Word, slashes disappear.

Description: After export to Excel, single slashes are converted to double slashes.

Reproduction: This issue can be reproduced consistently on at least two systems.

Workaround: If the document is imported from Word and single slashes are displayed as double slashes in DVX, leave the slashes as they are. If you change them into single slashes, they will disappear after export.

If the document is imported from Excel and single slashes are displayed as double slashes in DVX, change them into single slashes. If you leave the slashes as they are, they will be exported as double slashes.


Comments from Atril Software:

Because embedded codes in DVX are represented as {1} (i.e. opening curly bracket, number, closing curly bracket), the program needs to be able to to handle textual curly brackets in a different way. So some text in Word which appears as "The entry {main} is the starting point" will need to be different inside DVX so that "{main}" isn't confused with an embedded code. The way DVX does this is by adding a backslash before textual curly brackets. So DVX will display "The entry \{main\} is the starting point".

This means that backslashes are not just textual in DVX either. They are control characters for escaping curly brackets. So a textual backslash in DVX has to be escaped as well and this happens by doubling it.

So the text in Word "C:\Program Files\" should be imported into DVX as "C:\\Program Files\\" and also translated this way. In the target segment, a single backslash doesn't have any meaning and is only meaningful if paired with another backslash or a curly bracket.

Some filters, such as Excel, have a bug and don't apply these rules correctly or consistently. This is in the process of being fixed.


Comments from other users: