tips & tricks
for translators
|
MS-Word tips Formatting Inside Target Cells Removing and Inserting Graphics Rogue Codes II - Rogue codes & Script Editor Rogue Codes III - Using Trados to clean rogue codes Cannot see columns in 2-column file (DV3) Changing Comments' author name File size in Word 6.0/95
docs Problems understanding what is hidden in you file? Try the Script Editor.
|
|
|
Template files (extension DOT) may contain dangerous macros. Open it using Word Viewer and copy contents to a normal Word doc.
Nevertheless, to work with Windows, you should create a template with all your customization. When there is a problem with Word, one of the ways to solve it is to delete normal.dot. If your customization is in another file, you do not lose it.
To create a template:
|
|
|
It is safer to view a Word document using its viewer. This way, no macro will be executed. Word viewer can be found here.
|
|
|
Formatting inside target cells
In Déjà Vu, one cannot format target cells differently than source cells. If you need to format target cells, we suggest to mark the words and then use one of the tools below to post-edit your file. E.g.: write _italic_ to format the word in italic. After the translation is exported, one can find and replace those marked words with the right formatting. E.g.: Using Wildcards, find: (_)(*)(_) and replace with \2 formatted in italic. See:
OR It is possible to use Windows AutoFormat tool (Insert > AutoCorrect and select AutoFormat tab. Select the "Replace" items you want to activate). That is, you can use the options given by Word inside target cells, and after exporting the translated file, select Format > AutoFormat. NOTE: Use Autoformat carefully. Formatting is based on an underlying template and can alter more things then you expect. Xavier Pitel's macro (below) is safer. Word 2000 AutoFormat Screen: . OR As an alternative: Xavier Pitel developed a Word macro to allow formatting inside the target cell (italic, bold, etc.) The macro works as a "post-editing" tool. One uses some defined codes during translation (e.g.: _italic_, *bold*), and then runs the macro in the exported translated file. Xavier Pitel's Option Screen:
Visit Xavier Pitel's site.
|
|
|
Removing and inserting graphics in a file
Suggestion #1:
Miri Ofek, a Déjà Vu user, developed some Word macros to help removing and reinserting graphics in a Word file. Once the graphics are removed, it is very easy to import, translate, and export the translated file. The macros are in a Word template file (ImagesOutIn.dot) — to download it, click here. How to use Miri's macros:
Alternatively Suggestion #2:
Alternatively Suggestion #3: I do not remember whose suggestion is this, but it is a very good way to deal with the problem. My favorite so far. Pre-translate your file in Trados, saving it as a TTX (TagEditor) file. TTX is a text only file and DVX handles it pretty well. |
|
|
ATTENTION: It does not work in all formats - it works in Word docs.
OR IN DV3 ONLY:
|
|
|
Rogue codes are codes that appear in your cell without any logical reason. (In SDLX, instead of codes, you'll see lots of format colors). E.g.: Rogue c{023}odes {024}are codes that{025} {026}appear in your cell without any logical rea{027}son.{028} Rogue codes frequently are the result of a scanning. How to deal with them? See below, Rogue Codes II, and Rogue Codes III. In Word (Steven Marzuola:
MACRO TO CLEAN ROGUE CODES And... see Rogue Codes II below. |
|
|
Rogue Codes II - Rogue codes & Script Editor And after following the above instructions (Rogue codes I), if you still have rogue codes... Inside Word, go to Tools > Macro > Microsoft Script Editor. Jump to the topic about Script Editor. |
|
Rogue Codes III - Using Trados to remove rogue codes It is known that Trados segmenting seems to remove most rogue
codes. What I didn't realise and that I've just found out is
that if you TWB segment a Word file using Translate and then
immediately run the file back through the TWB Cleanup process
(i.e. remove Trados segmenting), most of the rogue codes have
disappeared when you import the straight Word file (not the Trados-segmented
file) into DVX (except for bullets and automatic page numbers
which are arguably not rogue codes). This is particularly the
case with Word 2003 which seems to scatter rogue codes all over
the place. Trados Translate/Cleanup seems to filter out these
codes. ALTERNATIVELY: Pre-translate your Word file using Trados, but saving it as a TTX (TagEditor) file.
|
|
|
Automatic generated bullets and paragraph numbers Steven Marzuola
While looking in another newsgroup, I learned about the following Visual Basic command: ActiveDocument.ConvertNumbersToText This command converts all automatically generated bullets and paragraph numbers to their text counterparts. The document looks the same, but the automatic features are all gone. The reason somebody might want this is, automatically generated bullets and paragraph numbers can cause inconveniences in DV3 (and I supposed DVX). I posted a macro here a couple of months ago that usually hides those features, reducing the amount of extraneous characters (numbers and bullets) that Déjà Vu has to handle. However, I have recently come across some bullets that the macro won't hide. While trying to learn more about those, I ran across this VBA command. It won't be useful for everyone, but it will be suitable for much of my work. Automatic numbering is great for documents that are being edited and revised, but often the translation is supposed to be done of the final version. Any future edits are usually made to the source, not the target, so the presence of these automatic features in the target is usually not required. |
|
|
Cannot see columns in 2-column file (DV3) When exporting to a 2-column file (actually a 3-column file), DV3 formats the first two as hidden text.
OR
|
|
|
Changing Comment's author name When exporting Comments to Word, DV uses "DVX" as the author for those comments. It is possible to change the author name using Word's Script Editor. Open your doc in Word, go to Tools > Macro > Microsoft Script Editor. Find DVX and replace it with the new author name. To install MS Script Editor, see topic about the Script Editor. Alternatively Save your file as rtf, open it in a good
editor,
look for Be careful, do not change anything else. Recommended Editor (freeware): Crimson |
|
|
From MS website: Document file size increases with EMF, PNG, GIF, or JPEG graphics in Word When you save a Microsoft Word document that contains an EMF, PNG, GIF, or JPEG graphic as a different file format (for example, Word 6.0/95 (*.doc) or Rich Text Format (*.rtf)), the file size of the document may dramatically increase. For example, a Microsoft Word 2000 document that contains a JPEG graphic that is saved as a Word 2000 document may have a file size of 45,568 bytes (44.5KB). However, when you save this file as Word 6.0/95 (*.doc) or as Rich Text Format (*.rtf), the file size may grow to 1,289,728 bytes (1.22MB). See MS page to solve the problem. |
|
|
Problems understanding
what is hidden in your file? I'm a Word 2K user, so there may be some differences to W2003. Basically:
|
|
Convertion of Word docs to new formats (Office 2007/Open XML/ODF) To convert Office/Word 2000, XP, and 2003 to the new Office 2007 (OpenXML) format, download the update found here. To save the Word files (Xp, 2003, and 2007) as ODF, use the plug-in found here.
|
