Published by SDL International ( Copyright SDL International. All rights reserved. Documentation for SDLX2004.

Transcription

1 Project Wizard

2 Published by SDL International ( Copyright SDL International. All rights reserved. Documentation for SDLX2004. Microsoft and Windows are registered trademarks of Microsoft Corporation. All other trademarks are acknowledged as belonging to their respective companies. Documentation produced April 2004.

3 Contents SDL Project Wizard About the Project Wizard File types handled by SDL Project Wizard Working with FrameMaker files Working with QuarkXpress files Project Import Wizard Overview of the import wizard process Files and folders created by the Import Wizard Project Import Wizard screens File type selection Filter Options dialog boxes Source and Target Languages Source files location Target Language folder Options Confirm Project Export Wizard About the Project Export Wizard How to export selected ITDs How to export all files in a project (SPJ) file Error log produced during the export

4 Appendix A Code File Filter Options dialog box 26 Appendix B CopyFlow Filter Options dialog box 27 Appendix C Generic Delimited Filter Options dialog box 28 Appendix D HTML Options dialog box 29 Appendix E Java Filter Options dialog box 30 Appendix F MIF (Maker Interchange Format) Options dialog box 31 Appendix G RTF Filter Options dialog box 33 Appendix H SGML/XML Extract Options dialog box 34 Appendix I WBF file type HTML Extract Options dialog box 38 Appendix J XML Extract Options dialog box 39 Appendix K XPress tags Filter Options dialog box 48 Appendix L XLS Filter Options dialog box 49 Appendix M Segmentation Rules 50 Appendix N Regular expressions used in SDLX 61 Appendix O InDesign 63

5 SDL Project Wizard About the Project Wizard There are two SDL Project Wizards - Import and Export: SDL Project Import Wizard Use Project Import Wizard to: Extract translatable content from selected files and put this into ITDs for translation in SDL Edit Create a project file which enables you to handle groups of ITDs as a single project Create OTF format files for use in such applications as SDL Align and SDL Analyse. SDL Project Export Wizard Use Project Export Wizard to: Take translated ITD files and combine the translated content with the other elements of the original language file to create a translated version of the file. File types handled by SDL Project Wizard SDL Project Wizard can handle these file types: Code File CopyFlow Filter Doc (Microsoft Word) Generic Delimited HTML (Web pages) JAVA MIF (FrameMaker) PPT (Microsoft PowerPoint) RC (Program Resource File) RTF (Documentation and Help) Server side scripting SGML TXT (Plain Text) WBF - Web-based formats XLS (Microsoft Excel) XML XPress Tags Filter. SDLX Import Wizard has a complete set of filters to handle each of these file types. The filters are able to recognise the different elements of each file type and identify what is translatable text. They then extract and format this text and place it in ITD files ready for translation. In addition to the default filters there is a set of Filter Options dialog boxes which enable you to tailor the default filter settings to suit your particular processing requirements. Working with FrameMaker files Before you can process FrameMaker files (.fm) in SDLX you need to export them to MIF format. This is how you export them: 1

6 1. Open the original FM file. 2. Select Save as from the File menu. The Save Document dialog box is displayed. 3. Select MIF (*.mif) in the Save as type box. 4. Go to the File name box and change the.fm extension to.mif 5. Click the Save button. 6. Close the file. 7. Close FrameMaker. Working with QuarkXpress files Before QuarkXpress files can be processed in SDLX they must first be exported to CopyFlow TAG file format. 2

7 Project Import Wizard Overview of the import wizard process This is a high-level overview of the steps in the import process. Each of the Import Wizard screens is described in detail in the next section of this guide. Step 1 Click the Project Wizard button on the SDLX Switchboard and then select the Import option on the Select wizard mode dialog box. Click OK. Step 2 File type selection screen Specify the types of files to be included in the import. Click Next. If any of the file types selected have associated Options screens, these will now be displayed. File-type specific Options dialog box Specify how you want files of this type to be handled. There are several different Options dialog boxes. Complete the dialog box and click OK. 3

8 Step 3 Source and target languages screen Specify the source file(s) language and the languages into which they will be translated. No target languages need be selected if you are creating OTF files only. Click Next. Step 4 Source files location Specify where the source files can be found. Click Next. Project files Confirm which files at the specified location are to be processed. Click OK. 4

9 Step 5 Target language folder Specify where you want the target language files created by the wizard to be placed. A separate folder is created for each target language. Click Next. Step 6 Options Specify processing options for the selected files. Click Next. Step 7 Confirm Confirm your selections and click Next. The import now takes place. 5

10 Files and folders created by the Import Wizard Before running the Import Wizard you must put all of the files to be imported into a single folder or folder hierarchy. Files to be processed by the Project Import Wizard. During the import process the Import Wizard creates these folders: One for each target language, all of the target language ITDs are placed here One for each web page selected, all of the graphics that appear on the page are placed here. In this example you can see the contents of the French target language folder created by Project Import Wizard when it was run on the files shown above. 6

11 Each target language folder may contain the files shown below. The ITDs may be distributed for translation but the other files must not be moved or deleted; they will be needed when you come to create translated versions of the original files using Export Wizard. When translated ITDs are returned, they must be placed in the correct target language folders. FMP XLS & PPT OBJ ITD _ix.itd _vr.itd _xr.itd scr.itd FMP files contain font mapping information. An FMP file will be created if there were any RTF files in the source folder(s). Copies of all XLS and PPT source files. These files must not be deleted. They will be needed when you come to create translated versions of the original files using Export Wizard. When you export the translated ITD, the new translated PPT file will overwrite the copy of the original PPT file. An OBJ file is created in respect of every source file that contains embedded objects such as graphics. These files must not be deleted. This file contains the translatable text extracted from the source file. ITD files are translated in SDL Edit. These are the files for translation. These three ITD files are created when you have MIF source files. They contain the file: indexes, variables and cross-references. These files need to be checked for translatable content. If web based files contain script elements, the script is output to this file. Project files: SPJ This is the project file. If you opt to create a project file, it is placed in the origin (top level) folder with the source files. 7

12 Project Import Wizard screens File type selection This is where you specify what types of files are included in the set of files to be translated. Select the appropriate check box for each file type. If the Options button is active special filter options are available for the selected file type. You can click the button to display and complete the filter dialog box now or wait until you have finished selecting file types and handle them all at the same time. If this button is active a filter options screen is available. Click the button to display the File-type Options dialog box. Click the Next button when you have finished selecting files. If filter options are available for any of the file types you have selected, the Filter options dialog box is displayed. Click Clear All if you do not want to see any of the Filter Options dialog boxes. The system default filters will be used to process the files. Click Cancel to use the same filter settings you used previously. Click Check all if you want to see the Filter Options dialog box for every file type listed. Click OK to display the Filter Options dialog box for each selected file type. 8

13 Filter Options dialog boxes Filter options control the process of extracting content from selected files and placing it in the ITD or OTF file(s) being created. They control what data is extracted and how it is prepared for translation. There are default filter options for all supported file types; these additional options enable you to tailor the filter process to suit your particular needs. The filter options dialog boxes are described in Appendix A to Appendix L. 9

14 Source and Target Languages This is where you specify the source language of the selected files and language(s) into which they will be translated. An ITD file will be created for each file selected in respect of each target language specified. Selected target languages appear here. Click to select a target language. Click to add the selected language to the list of target languages. How to complete the Source and Target Languages screen 1. Check the language shown in the Source language box. Click the down arrow and select a different language if required. 2. Select the UTF-8 check box if the source language files are UTF-8 encoded. 3. Select the first target language into which the files will be translated. Click the down arrow in the target language selection boxes and select the required language. 4. Select the UTF-8 check box if you want the target language files to be UTF-8 encoded. 5. Click the Add button to add the language to the list of target languages. 6. Continue adding target languages until the list is complete. 7. Click Next when you have finished selecting languages. 10

15 Source files location Use this to specify where the source language files are located. The source files may be stored in a single folder or a folder hierarchy. How to complete the Source and Target Languages screen 1. Click the Browse button. The SDLX Project Wizard dialog box is displayed. 11

16 2. Navigate to the folder where the source files are located (or the top level folder of a folder hierarchy). 3. Select the folder and click OK. The selected folder appears in the Source file folder box. 4. Select the Search through sub-folders check box if the folders below the selected folder also contain project files. 5. Click Next. The Project files dialog box is displayed. It shows all files selected for translation. 6. Confirm the list of files for translation: If you want to remove a file or folder from the list you want to create a checklist of the selected files for future reference then select the file/folder and click the Exclude form processing button. click the Copy button. A copy of the folder structure is placed on the clipboard. 7. Click OK. The Target Language folder dialog box is displayed 12

17 Target Language folder Use this to specify where you want the target language files to be created. Project Import Wizard will create a sub-folder for each of the specified target languages and the ITD files will be placed in the appropriate language folders. By default the ITD file names are created by combining the source file name and with the.itd extension. For example the French ITD for the source file BayerQuest1 would be named: BayerQuest1.itd and placed in the French folder. How to complete the Target language folder screen 1. Check the location in the Target file folder box. Is this where you want the target language folders to be created? If then this location is correct go to step 2. you want to the folders to be created in the click the Default button. source file folder (selected on the previous screen) you want to select the folder location. click the Browse button. The SDLX Project Wizard dialog box is displayed Navigate to the folder and click OK. 2. Select the Use short language codes check box if you want language codes (rather than language names) to be used when creating the itd file names. 3. Click Next. 13

18 Options This dialog box contains a number of options needed when processing HTML and MIF files. This is also where you specify what type of segmentation you want to be applied to the text in the source files. The options available for selection depend on the types of source files you have selected. Dialog box elements: Remove embedded objects from files Glue files together for processing Maximum number of glued files Select this to remove graphic images and other objects from source files. These objects are stored in an OBJ file. Do not erase these files!! When the translated versions of the original files are being created, the objects in the OBJ file are merged back into the target language file. Select this option to enable SDLX to glue several HTML or XML files together to create a single large file for translation. The default maximum number of files that can be glued together is 1,000. You can change this figure if you wish. If you select more files than the maximum you have specified, more than one ITD will be created. The glued files are named: _HTML001.itd, _HTML002.itd etc. A file named glued.txt is also produced. It contains a list of all files that have been glued together to create an ITD. Files are unglued in Project Export. Backup HTML files before validation Because the HTML filter validates the HTML code before processing, we recommend that you backup the selected HTML files before processing them. 14

19 Remove tag file when ITD is generated Enable script processing timeout Number of minutes for timeout Segmentation rules By default SDLX creates an OTF file for each of the source files (or each glued file). These OTF files can be used in SDL Align and SDL Analyse (if you have a version of SDLX that contains those tools). If you do not need the OTF files then you may as well get rid of them. Select this option to automatically remove the OTF files created during the Import process. When HTML files are found to contain script elements, SDLX creates two ITD files for the source file one for the non-script content and one containing the script elements. The ITD containing script has _scr added to the filename. For example: projectfile1_scr.itd SDLX then checks each _scr.itd for segments that do not contain text and locks them. This is usually quite a rapid process however you can put a time limit on it if you wish. Select this to display the Segmentation Rules dialog box where you can select the type of segmentation to be applied to the text extracted from the source files. The selected rule set name is displayed in the box to the right of the Segmentation rules button. How to complete the Target language folder screen 1. Check the default settings and change these if required. Use the field descriptions above to help you decide which options to select. 2. If you want SDLX to use a different segmentation method to the one displayed, click the Segmentation Rules button and select the required method. 3. Click Next. 15

20 Confirm This is where you actually start the import process. Click Next and this screen reflects what processes are being performed and how much progress is being made. Shows what processing is currently taking place. Indicates how the current process is progressing. Click this to save your current selections as the default settings for project Import. How to complete the Confirm screen 1. Are you happy with your selections? If you want to change any of your selections you want to save your selections and have SDLX use them as the default selections next time you use Project Import Wizard then click the <Previous button to return to the screen to be updated. click the Save Defaults button. 2. Click Next. The import process now takes place. 3. When the import is complete the Save Project button is displayed. Click this if you want to create a project file (SPJ file) containing all of the imported files. 4. Click Close. When the import has finished, go to the folder where the target language ITDs have been created. You can now start distributing these for translation. DO NOT delete any of the other files created during the import process as these will be needed when you Export the translated ITDs to create translated versions of the source files. 16

21 Project Export Wizard About the Project Export Wizard The Project Export Wizard is the method by which files imported into SDLX format for translation are now exported back to their original format. When ITDs have been translated, use Project Export Wizard to integrate the translated text with the other elements of the original language files to create translated versions of those files. You can export: Selected files, or All files in a project. When the export is complete, a target language version of each ITD included in the export will be placed in the target language folders. Note: If you edit a translation after the file has been exported, export the file again and the new version will overwrite the previous one. How to export selected ITDs 1. Click the Project Wizard button on the SDLX Switchboard. The dialog box is displayed. 2. Select the Export files from an existing project option. The SDLX Project Export screen is displayed. 17

22 3. Select the I want to use an existing project file option. 4. Click Next. The Select translation documents folder screen is displayed. 5. Click the Browse button. The SDLX Project Wizard dialog box is displayed. 6. Navigate to the folder where the ITDs are located (or the top level folder in a folder hierarchy) and click OK. 18

23 7. If you want to select ITDs located in sub-folders to the selected folder, select the Search through sub-folders check box. 8. Click Next. The Project files dialog box is displayed. 9. Confirm the ITDs to be exported: If you do not want one of the selected ITDs to be exported you want all ITDs in an entire folder to be excluded from the export you want to copy details of the confirmed folders/files to the clipboard then select the ITD and click the Exclude from processing button. select the folder and click the Exclude from processing button. click the Copy button. 19

24 10. Click OK. The Confirm screen is displayed. 11. Confirm the export settings: If you want to save your selections and have them as your default settings the next time you use the Project Export Wizard You want a different font to be applied to the exported file(s) rather than the default project font then click the Save Defaults button. click the Font Mapping button. The Font Mapping dialog box is displayed. 12. Click Next. The export is now performed. When the export is finished the Complete dialog box is displayed. 13. Click Close to exit the wizard. 20

25 How to export all files in a Project (SPJ) file 1. Click the Project Wizard button on the SDLX Switchboard. The dialog box is displayed. 2. Select the Export files from an existing project option. The SDLX Project Export screen is displayed. 3. Select the I want to use an existing project file option. 4. Click Next. The Select SDLX project file dialog box is displayed. 21

26 5. Click the Browse button. The Navigate to the Open dialog box is displayed. 6. Navigate to the folder containing the SPJ file. Select the file and click the Open button. 7. Click Next. The target language selection screen is displayed. 22

27 8. Select the check box of any language for which you do not want ITDs to be produced. 9. Click Next. The Project files dialog box is displayed. 10. Confirm the ITDs to be exported: If you do not want one of the selected ITDs to be exported you want all ITDs in an entire folder to be excluded from the export you want to copy details of the confirmed folders/files to the clipboard then select the ITD and click the Exclude from processing button. select the folder and click the Exclude from processing button. click the Copy button. 11. Click OK. The Confirm screen is displayed. 23

28 12. Confirm the export settings: If you want to save your selections and have them as your default settings the next time you use the Project Export Wizard you want a different font to be applied to the exported file(s) rather than the default project font then click the Save Defaults button. click the Font Mapping button. The Font Mapping dialog box is displayed. 14. Click Next. The export is now performed. The Complete dialog box is displayed when the export is finished. 15. Click Close to exit the wizard. 24

29 Error Log produced during the export If SDLX encounters any problems performing the export it will produce an error log that is automatically displayed on screen. The most common errors are caused by a file having been deleted or a file being open (in use) when the export took place. If you want to save the log, click the Save button. The Save As dialog box is displayed. 25

30 Appendix A - Code File Filter Options dialog box Use this dialog box to specify how files containing programming code are processed. The file must be ASCII text, but the file extension can be anything. Specify the programming language. Specify whether single or double quotes (or both) are used to separate items in files. If selected, ignore specific types of text. 26

31 Appendix B - CopyFlow Filter Options dialog box Use this dialog box to specify how CopyFlow TAG files are processed. CopyFlow is a third party add-on to QuarkXpress. In order to import QuarkXpress files into SDLX they must first be exported to CopyFlow TAG file format. You need to have an understanding of these DTP/Typesetting terms before selecting these options. If in doubt, leave them unchecked. 27

32 Appendix C - Generic Delimited Filter Options dialog box Use this dialog box to specify how delimited ASCII files are processed. Select a previously saved scheme (set of options), or create a new scheme. Click Save As to save the current settings. Click Delete to remove the selected scheme. Specify whether the first line of a file consists of headings, and whether each line is contained in quotation marks. Specify the value that indicates a new column. If you select Other, then you must enter the value in the box provided (it can be more than one character in length). Source Column - Specify the column from which source segments are generated. Translation Column - Specify the column from which translation segments are generated. Minimum number of columns - Specify the minimum number of columns that must exist in a line. If a line contains less than the minimum number, then it is not processed. Tooltip Format Optional. Specify a tooltip that appears in SDL Edit when the pointer is over a segment. To specify that the contents of a particular column should be used as a tooltip, use this formula: % <column number> % For example %2% Tooltip must exist - Available only if a Tooltip Format has been specified. If this check box is selected and there is no value in the column specified as the tooltip source, this row of the file will not be imported into the ITD (or OTF file). 28

33 Appendix D - HTML Options dialog box Note: The HTML Options dialog box exists for legacy reasons. We recommend that you actually use the Web Based Formats (WBF) filter for processing HTML files. List of tags recognized by SDLX. To add a non-standard tag to the list, enter the tag here and click Add. To remove the tag from the list, select the tag and click this. This prevents the HTML validator from checking the tag. Click this to remove all tags from the list. Select a tag and then select this to indicate that two or more instances of the selected tag are allowed to overlap. For example, here two FONT tags are overlapped: <FONT FACE="Arial">Hello <FONT COLOR="#0000FF>World</FONT></FONT> HTML Filter Options This dialog box is displayed after the HTML Option dialog. Select this check box if you want a placeholder to appear in ITD files to indicate the position of IMG tags. The placeholder is a vertical red bar. Having a visible placeholder enables the translator to move the IMG tag to a new position (using Format Painting) if required. There are further settings that relate to HTML files on the SDL Project Import Wizard - Options screen. 29

34 Appendix E - Java Filter Options dialog box Select the check box to exclude comment text from the import. 30

35 Appendix F - MIF (Maker Interchange Format) Options dialog box Don t split will keep index entries within an index marker together unless they contain any of the criteria by which the rest of the documentation is segmented, e.g. a full stop. Split at ; only will force SDLX to split index marker entries into separate segments wherever it sees a semi-colon ; Split at ; and : will force SDLX to split index marker entries into separate segments wherever it sees a semi-colon ; or a colon : Select this to remove embedded objects from MIF files and place them in OBJ files. If you choose not to extract embedded objects they will be stored in the ITDs. This is not advisable as it slows down the filter process and results in very large ITD files being created. To remove a marker from the list, select the marker and click Remove. To remove all markers, click Clear. To add a non-standard marker to the list, enter the marker here and click Add. FrameMaker files must be converted to MIF format before they can be imported into ITD files for translation. During the MIF import process, Project Wizard creates these files:.itd.obj sdlx_ix.itd One for each MIF file imported. These contain the translatable text extracted from the MIF files. These contain any embedded/linked graphics found in the imported files. The.obj files must be kept with the.itd files as they will be needed when you want to convert the translated itds back to MIF format. One sdlx_ix.itd file is created; it contains the text from index markers in all of the imported MIF files. When translating this file you must ensure that segments do not exceed 256 characters (this is FrameMaker s limit per index marker). If a segment exceeds that number, character 257 and all subsequent characters will be excluded when the ITDs are processed back into MIF format and then FrameMaker format. 31

36 sdlx_xr.itd One sdlx_xr.itd file is created; it contains all cross references from all MIF files imported. When translating an sdlx_xr.itd file: Do not translate anything inside chevrons < > as this will damage the formatting of the text when the files are processed back into the MIF/FrameMaker format Make sure that Auto Propagation is NOT active. If it is you will get fuzzy matching taking place and the cross-references will become unusable once merged back. sdlx_vr.itd One sdlx_vr.itd file is created; it contains all variables from all MIF files processed. When translating an sdlx_vr.itd file: Do not translate anything inside chevrons < > as this will damage the formatting of the text when the files are processed back into the MIF/FrameMaker format Make sure that Auto Propagation is NOT active. If it is you will get fuzzy matching taking place and the cross-references will become unusable once merged back. Note: Do not rename or move any of these files otherwise SDLX Project Export Wizard will not be able to merge the translated content with the original file elements when creating translated versions of the original files. This dialog box is displayed next. Don t segment on hard returns Note: The name of this box should be Don't segment on forced returns. Sometimes in FrameMaker people put a soft return at the end of a line even though it may not be the end of the sentence. Since SDLX automatically segments on soft returns, this can cause problems when applying a TM (sentences would not match). If soft returns have been used to break lines, select this to prevent SDLX from automatically segmenting when it encounters them. Use native language encoding FrameMaker can have problems with Greek and Turkish below Windows To overcome this, use native language encodings. Use literal <char> commands For some languages (Japanese for example) FrameMaker uses a <char > command in the MIF file rather than the correct double byte character. If a MIF file contains intermittent? characters, select this option. 32

37 Appendix G RTF Filter Options dialog box Use this to specify how RTF files are processed. If you select the Extract Auto Generated Fields check box, auto-generated fields are extracted from the RTF and put in the ITD for translation. Here are three examples of automatically generated fields: Table of contents (TOC) Index (not index markers) Page numbers. 33

38 Appendix H SGML/XML Extract Options dialog box Use this to specify how SGML files are handled during import. Tags in bold will be translated. Tags in normal text will not be translated. Highlight a tag to activate the Status options. The blue highlighting indicates Inline segments. This means a segment break will occur after every sub element. Tags with a plus sign (+) can be expanded. Dialog box elements: File menu Analyse select a file to analyse. Open - Display the Windows Open dialog box and select an ANL file. Save - Save the analysis Save As - Save the analysis as an ANL file with a different file name. Save As Table - Save the analysis as a table file. Save As Trados INI File - Save the analysis as a Trados INI file. Translate If selected this indicates that the selected tag contains translatable text. Deselect this if you do not want the tag to be translated. 34

39 Inline Segment Break Entity Options Merge Options Save Close Inline (embedded) segments are shown on a blue background. By default text in the main element is combined with that in the sub-elements to form a single segment. If you want a segment break at the end of each segment, deselect this box. Applies to empty tags only. Causes a segment break on the tag. If you do not want the segment to break, deselect this box, the empty tag will appear as a red vertical bar. Click to display the Entity Options dialog box where you can specify how entities will be processed. The settings on this dialog box affect both the import and export processes. Click to display the Merge Options dialog box where you can specify mark-up options to be used on the translated output file. Save the analysis. Close the dialog box. There are three steps to import process: 1. Select a DTD file or an SGML file to analyse. SDLX analyses the file and creates a list of the tags (and their properties) it found. 2. Use the options available on the SGML/XML Extract Options dialog box to specify how each of the tags is to be handled during the import. 3. Save the analysis in an ANL file. The ANL file provides the rules by which SGML files are prepared for translation. You can analyse a DTD file or an SGML file: If a DTD file is available, analyse this If no DTD is available, but one of the SGML files to be translated contains all of the tags that appear in the SGML files to be imported, analyse this file If a DTD file is not available, and none of the SGML files contain the complete set of tags, create a temporary SGML file that contains all of the tags and analyse this. Tag analysis example The following XML code: <?xml version="1.0"?> <doc> <rob><jump>hello</jump>, my name is Rob.</rob> <oliver>hello, my name<newline/> is Oliver.</oliver> </doc> Without editing would produce an ITD that looks like this: 35

40 By default, tags have the Segment break property set. Therefore, the <jump>hello</jump> element becomes a segment on its own, which is not good for translation. To prevent this you need to change the property of the <jump> tag so that it is classified as Inline. You should also change the properties of the <newline/> tag as this should also be classified as Inline. It is also an Empty tag, so this box can be checked, if it is not already. The resulting ANL file will look like this: And the resulting ITD will look like this: The text "Hello" is marked for Format Painting so that the translation for the word "Hello" can be made to be inside the <jump> tag. The empty <newline/> tag is marked with a red bar which can be moved, also using Format Painting. If any tags should not be translated, highlight the tag name and de-select the Translatable option. Tags which will be translated are shown in bold text, and tags which will not be translated are shown in normal text. How to complete the SGML/XML Extract Options dialog box 1. Select File, Analyse. The Analyse dialog box is displayed. 36

41 2. Click the Browse button beside the DTD/SGML/XML box. The Open dialog box is displayed. The file type defaults to DTD, change this if you are going to select an SGML file. 3. Navigate to the folder containing the DTD or SGML file to be analysed. 4. Select the file and click Open. 5. Click the Browse button beside the Analysis file (output) box. The Save As dialog box is displayed. 6. Navigate to the folder where you want the analysis file to be created. 7. Enter the name for the analysis file in the File name box. 8. Click Save. The Analyse dialog box is now complete. 9. Click OK. The selected file is analysed and the tags found in the file are displayed here. 10. Select the first tag: If the Translate check box is selected but you do not want the segment to be translated the Inline check box is active and you want segments breaks to occur at the end of each sub-element the tag is empty but you want a segment break to occur here then select the Translate check box (to remove the check mark). select the Inline check box. select the Segment Break check box. 11. Continue checking until all tags have been checked. 12. Click Save. 13. Click a button to continue: If you want to specify SGML/XML mark-up options to be used on the translated output file you want to specify how entities will be processed you have finished then click the MergeOptions button. The SGML/ XML Merge Options dialog box is displayed. click the Entity Options button. The SGML Entity Options dialog box is displayed. click Close. Note: If you need help completing the SGML/ XML Merge Options dialog box or the SGML Entity Options dialog box go to the SDLX Switchboard and open the application Help. The dialogs are explained in the Filter Options Dialog Boxes topic. 37

42 Appendix I WBF file type HTML Extract Options dialog box When you specify a WBF file type the HTML Extract Options dialog box is displayed. This dialog is used to analyse the different elements of web format files and specify how they should be handled during the import process. When the analysis is complete the analysis details are saved in an ANL file. The ANL file is then applied to all web based files during the import. You can edit the standard elements shown here if you have the necessary expertise. If you have an existing ANL file you can select and view or edit it for use during the import. Note:!!Do not change the default WBF filter settings unless you are an expert user!! If you want to change them, contact the SDLX support team for advice. The symbols indicate how the attribute will be treated. Key to the symbols that appear beside each attribute. Select to include the contents of CDATA sections in the import file analysis. Dialog box elements: File menu Add Edit Delete Open - Display the Windows Open dialog box and select an ANL file. Save - Save the analysis Save As - Save the analysis as an ANL file with a different file name. Add a new element. Edit the selected element. Delete the selected element. Web files containing Script If the web file being analysed contains script, the script will be extracted and placed in a separate SCR.itd for translation. 38

43 Appendix J XML Extract Options dialog box The SDL Extract Options dialog box is used to create a template that tells SDLX how to handle each element of XML files submitted for translation. This template is stored in the form of an ANL file. To create this template, select and analyze a DTD or XML file in the XML Extract Options dialog box. The options on the SDL Extract Options dialog box enable you to specify: Whether tags and elements should be translated Whether an element should be treated as inline, a segment break, or empty. You can only select and analyze one file at a time. However, you can analyze a series of files in turn and append each set of analysis results to the same ANL file. Expressions You can add Expressions to the ANL file to identify specific elements or instances of elements for translation. Expressions are based on a subset of XPath (XML Path Language) which is the standard used to query XML documents. Expressions are described in detail later in this Appendix. XML Extract Options dialog box example When you analyze an XML file to create the ANL file, the analysis results are displayed in the XML Extract Options dialog box. The elements and attributes are displayed in a list view. Select/de-select the check boxes to indicate how an element should be treated. 39

44 File menu Toolbar Right mouse-click menu Dialog box elements: File menu New Analyse Open Save Save As Save As Table Save As Trados INI File Clear Add a new element. Select a file to analyse. Display the Windows Open dialog box and select an ANL file Save the analysis Save the analysis as an ANL file with a different file name. Save the analysis as a table file. Save the analysis as a Trados INI file. Clears the currently displayed analysis without saving the ANL file. Delete Move Item Up Move Item Up Element Attribute Expression Segment break Delete the selected element. Move the currently selected item up a row. Move the currently selected item down a row. Element name. Attribute name. There will only be a value here if you have created an Expression for this element. If the expression is found to be true the element will be translated. Applies to empty tags only. Causes a segment break on the tag. If you do not want the segment to break, deselect this box, the empty tag will appear as a red vertical bar. 40

45 Translate Empty Auto detect encoding Replace carriage return character with a space Replace multiple whitespace characters with a space Include attribute values in the tooltip Translate unlisted elements Inline Namespaces Entities If selected this indicates that the selected tag contains translatable text. Deselect this if you do not want the tag to be translated. Select this to indicate that the selected tag is empty. By default, segment breaking occurs on empty tags. Select this if you want SDLX to use the encoding specified in the document (rather than the encoding specified by the user importing the file). Select this to replace each carriage return in the file with a single white space. Sometimes, when a tag contains a long passage of text, carriage returns are added mid sentence so that the text can be seen in an editor. When these files are imported into SDLX, each carriage return will be represented by a vertical red bar. If you select this box each carriage return is replaced by a space. This affects the way the code looks in an editor but not the way the file works. Select this to replace a sequence of spaces with a single white space. Often multiple white spaces are used to indent code to make it look better in an editor. If this box is checked any sequence of white spaces is replaced with one space. This affects the way the code looks in an editor but not the way the file works. Select this to include tooltip attribute values in the file for translation. When you place the cursor over a segment in an ITD a tool tip, containing the name of the tag that corresponds to the text that has been extracted, is displayed. If you select this check box then any attribute values will also be displayed in the tool tip. Select this to all unlisted elements in the file for translation. Inline (embedded) segments are shown on a blue background. By default text in the main element is combined with that in the subelements to form a single segment. If you want a segment break at the end of each segment, deselect this box. Click to display the Namespaces dialog box. This dialog lists the namespaces used in the file. Click to display the Entity Replacement dialog box. This is where you can define substitution rules for XML entities. How to create an ANL file The golden rule when processing XML files is that the XML code must be valid and well formed. A quick way to check if an XML file will import successfully into SDLX is to open it in Internet Explorer (version 5 or above) as this contains an XML validation tool. Scroll down the file and look for any errors indicated by the browser. Fix these errors before importing the file into SDLX. Note: If, when the XML Extract Options dialog box is displayed it already contains a list of elements, an ANL file has already been created. You can analyse further XML files and add more elements to the ANL file if you wish. 41

46 1. Select File, Analyse from the menu bar. The Analyse Options dialog box is displayed. 2. Select the required Translatable option and click OK. The Open XML/DTD file to analyse dialog box is displayed. 3. Navigate to the XML or DTD file to be analysed, select it and click Open. The Save Analysis file as dialog box is displayed. 4. Navigate to the location where you want the ANL file to be created. 5. Enter the filename in the File name box and click Save. The selected file is now analysed and the results are displayed in the XML Extract Options dialog box. 6. Check each element of the file: If the Empty check box is selected but you do not want a segment break to occur here the Translatable check box is selected but you do not want the segment to be translated the Inline check box is active but you want segments breaks to occur at the end of each sub-element the Segment Break check box is selected but you do not want a segment break to occur here you want to add an Expression to an element you want to add another instance of an element (to create multiple instances of an element in order to specify multiple Expressions for the same element) you want to delete an element then select the Empty check box (to remove the check mark). select the Translatable check box (to remove the check mark). select the Inline check box (to remove the check mark). select the Segment Break check box (to remove the check mark). select the element, right mouse-click and select Add Expression from the menu. The Expressions dialog box is displayed. Complete this and click OK. Note: The Expressions dialog box is described over the page. click the New button. The New Item dialog box is displayed. Complete this and click OK. The element is added to the bottom of the list. Select the new element and use the Move Item Up and Move Item Down buttons to move it into the correct position. select the element, right mouse-click and select Delete Expression from the menu. 7. Make any further selections and click the Save button. 42

47 Expressions If you do not want every instance of a particular element to be considered for translation you can identify specific instances of the element using an Expression. The elements that meet the Expression criteria will have the settings on the XML Extract Options dialog box applied; all other instances of the element will be ignored. When creating an Expression you can: Create one that tests the value of an attribute contained in the element, or Create one that identifies an element by its location in the XML tree. You can also apply multiple Expressions to an element. Example: In the following piece of XML you may wish to translate the text within a title element, but only if the country attribute of the cd element has a value of UK. <?xml version="1.0" encoding="iso "?> <catalog> <cd country="usa"> <title>empire Burlesque</title> <artist>bob Dylan</artist> <price>10.90</price> </cd> <cd country="uk"> <title>hide your heart</title> <artist>bonnie Tyler</artist> <price>9.90</price> </cd> <cd country="usa"> <title>greatest Hits</title> <artist>dolly Parton</artist> <price>9.90</price> </cd> </catalog> The expression for title element above would be: cd[@country= UK ] Note: The Translate unlisted elements option (in the XML Extract Options dialog box) overrides the use of Expressions. Ordinarily, if an element fails to satisfy its Expression condition it would not be translated. However, if you have selected the Translate unlisted elements option any element that fails to satisfy an Expression will be translated. Apply Multiple Expressions You can create multiple Expressions and apply them to the same element; each one will be applied to the element in turn. First, create multiple entries for the same element in the XML Extract Options dialog box (click the New Item button) and then create an Expression for each one. When an XML file is analyzed each Expression is applied to the element in turn. They are applied in the order in which they appear in the XML Extract Options dialog box. As soon as one of the 43

48 Expressions is found to be satisfied, the conditions defined for that element\expression (in the XML Extract Options dialog box) are applied to the element. These two Expressions will be applied to the title element in turn If the element is found to satisfy the second Expression, these settings will be applied to the element. Because Expressions are applied in the order in which they appear in the dialog box it is important to put them in the correct order. Use the Move Item Up and Move Item Down buttons to move the Expressions into place. Expressions dialog box To add an Expression to an element, select the element, right mouse-click and select Add Expression from the menu. The Expressions dialog box is displayed. 44

49 Create an Attribute Value Expression 1. Select the Attribute Value checkbox. This enables the other boxes and options in this part of the screen. 2. Click the down arrow in the Element box and select the element to which the attribute belongs. 3. Click the down arrow in the Attributes box and select the attribute to which the Expression will be applied. If nothing appears in the drop-down list the selected attribute contains a text value then the element has no attribute(s) on which to base an Expression. select the Text check box. Note: It is important that you select this check box as it places quotation marks around the value when it is tested. 4. Complete the Value box by entering the value against which the attribute will be tested. 5. Select the appropriate option for testing the attribute value: If the attribute contains a text value the attribute does not contain text then only the Equal to option will be available. This enables you to check whether the attribute value is equal to the value specified in the Value box. all three options will be available. 6. Click OK to create the Expression. In this example the Comparison element will be considered for translation if the attribute value = gt. 45

50 Create an Expression based on an XML Tree Node Location Use this option if you want an element to be considered for translation ONLY when it occurs at a particular location in the XML file. All occurrences of the element at other locations will be ignored. The fields in the lower part of the Expressions dialog box enable you to specify the element name and identify a location in the XML tree. The node location can either be fixed or defined in relation to another node. But what if an element appears in five places and you want three of them to be translated? By default each element appears once in the Extract Options dialog box. If you add multiple instances of the element you can specify a different location for each one. This means that the three instances of the element, at the specified locations, will have the Extract Options dialog box settings applied and the other two instances will be ignored. These are your options for specifying a tree location: Arbitrary descendant of Specific path Level it is in the tree, relative to a parent element Use this option to specify a node that is any type of descendant of a selected parent element. Note: If the node is an attribute then the rules defined in the Extract Options dialog box will only be applied to the attribute if its corresponding element is a descendant of the parent. Use this option to specify any node that is at the path location provided. Paths can be absolute or non-absolute. Use this option to specify any node that appears at a particular level below the selected parent. Note: You can combine a tree node location test with an attribute value test. This means that any element found at the specified location would have the attribute value test applied. If the attribute satisfied the test the Segment Break/Translate/Empty settings would be applied to the element. How to create an Arbitrary Descendant of condition 1. Select the Position in Tree check box. 2. Select the parent element from the drop-down list in the Parent Element box. 3. Select the Arbitrary Descendant Of option. 4. Click OK. How to create a specific path condition Paths may be absolute or non-absolute. Absolute paths start at the top of the tree and work down. For example, this is what an absolute path, for the same XML file example used earlier, would look like: /catalog/cd/artist/ 46

51 Non-absolute paths start at the current node and work backwards, up the tree, until they get a match. An absolute path starts with a / character and a non-absolute path does not. Toggling the Absolute Path (/) checkbox adds or removes this character. 1. Select the Position in Tree check box. 2. Select the Specific Path option. 3. If you wish to create an Absolute Path, select the Absolute Path (/) checkbox. 4. Select the first part of the path from the drop-down list in the Parent Element box. Click Add. 5. Repeat step 3 to select the next part of the path. If you have incorrectly added a path element, click the Remove button to remove it. 6. Continue selecting path elements until the path is complete. 7. Click OK. How to create a level condition Use this option to select a node by its relative position to its parent. 1. Select the Level option. 2. Select the child element from the drop-down list in the Child box. 3. Specify where the child appears in the tree in relation to its parent by specifying a level number and qualifier (Equal to, Less Than, Greater Than). For example if you want to apply the Expression to all children entities which are at least three levels down from the parent you would set the level at 2 and select the Greater Than option. 4. Click OK. How the Equal to, Less Than, Greater Than qualifiers work In this example the element Hello world appears at the third level below the level of the parent Test. To specify this level you would select level = 3 and option = Equal to. <Test> <One> <Two> <Three> Hello world </Three> </Two> </One> </Test> You could also select level 4 and Less Than or level 2 and Greater Than. However, both of these options mean that nodes on levels other than 3 could also be selected. 47

52 Appendix K XPress tags Filter Options dialog box Like the CopyFlow filter options, update these DTP settings tags if you are an expert user. Otherwise close the dialog box and use the default settings. 48

53 Appendix L XLS Filter Options dialog box Use this dialog box to specify how you want the text contained in Excel spreadsheets to be extracted for translation. To complete the dialog box, make your selections and click OK. Dialog box elements: Translate by row Translate by column Export hidden worksheets Export formulas Allow ungrouping of objects Blank cell tolerance Select this if you want data to be extracted row by row. For example: A1, B1, C1, D1, E1 then A2, B2, C2, D2, E2 Select this if you want data to be extracted column by column. For example: A1, A2, A3, A4, A5 then B1, B2, B3, B4, B5 Select to allow hidden worksheets to be made available for translation. Select to allow formulas to be translated Grouped items cannot be translated. Select this to allow SDLX to ungroup grouped items for translation. Note: If you select this option all macros associated with the group will be disabled. After this number of blank celles SDLX assumes the spreadsheet is finished. 49

54 Appendix M Segmentation rules Segmentation rules determine how text for translation is broken down into chunks (segments) for translation memory (TM) matching and translation. Segmentation rules tell SDLX exactly where you want text strings to be split and also, if required, where you do not want them to be split. In English for example the most common method of creating segments is to place a segment break at the end of every sentence. Getting your segmentation rules right is very important as the segment is the basic unit used in translation memories (TM). To get the best possible leverage from your TMs you need to have consistency when segmenting text. Selecting the correct rule is also important if you exchange TMs with other applications. What makes a segmentation rule? Segmentation rules are not language specific. A single set can handle all of the languages you deal with in fact. Each segmentation rule contains: Language Rules language (or language group) specific information that identifies particular characters/character sequences where text is to be broken (or must not be broken) Maps the maps tell SDLX how to navigate the available language rules and find the one to be used on a particular file. Segmentation rules available in SDLX SDLX provides these sets of segmentation rules for you to use: Default Paragraph S-Tagger Style Default TagEditor Style Default TRADOS Style Default. Of these, only the Default and Paragraph rules cannot be edited. As well as editing existing segmentation rules you also have the ability to create your own custom rules. Default This is the default SDLX segmentation rule. With these rules a new segment is created: At paragraph end (i.e. on encountering a carriage return) At cell end (when in a table) At list item end (for HTML) At sentence end. This means that when SDLX encounters a full stop followed by a space, it will start a new segment. Paragraph With these rules a segment break occurs at the end of every paragraph. 50

55 S-Tagger Style Default TagEditor Style Default TRADOS Style Default Used when segmenting MIF files. This set of rules mirrors the rules used in S-Tagger. You should use this set of rules if you intend to create a Trados TM from your translations (using the "Export to Trados" option in SDL Edit or SDL Maintain). Used for XML, Html, SGML etc. This segments your file as Tag editor would. You should use this set of rules if you intend to create a Trados TM from your translations (using the "Export to Trados" option in SDL Edit or SDL Maintain). Used for RTF, DOC etc. This set of rules causes your text to be segmented in the same way that it would be segmented by Trados. You should use this set of rules if you intend to create a Trados TM from your translations (using the "Export to Trados" option in SDL Edit or SDL Maintain). Defining custom segmentation rules You can create custom rules from scratch, but the simplest way to create a new set of segmentation rules is to select an existing set and modify them. If you intend to create your own segmentation rules you need to have some understanding of language rules, character sets and regular expressions used in SDLX. Language rules Language rules are language (or language group) specific and identify the precise characters or character sequences that identify the point at which text is to be split. They also define exceptions to the general language rule. An exception prevents text being split when it appears that the conditions for splitting have been met but actually they have not. Exception example: In English the default rule for segmentation is at the end of each sentence; the end of a sentence is indicated by a full stop followed by a space character. However, a full stop followed by a space can also appear in other circumstances. For example abbreviations such as Ltd. and e.g. appear in the middle of sentences. By identifying these abbreviations as exceptions, SDLX is prevented from inserting a segment break when these abbreviations occur. Character sets and code pages Character sets All of the characters used in a language are collectively referred to as the character set. For example the English character set includes the alphabetic characters a to z and A to Z, the digits 0-9 plus other assorted characters such as the pound symbol and asterisk *. Code pages When you hit a key on your keyboard a binary code is sent to the application software. The code page tells the application how to interpret this code and consequently what character to display on the screen. There are different code pages for different languages or sets of languages. For example, English and Western European languages are supported by code page 850. (P&M) but code page ISO is for Turkish only. 51

56 Although characters in a character set are usually based on a single code page, some special situations may require that the character set is comprised of characters from more than one code page. SDLX gives you the option to do this when you define a character set using the Edit Character Set dialog box. Regular expressions A regular expression is a formula for matching strings that follow some pattern. They are made up of normal characters and metacharacters. Normal characters include upper and lower case letters and digits. The metacharacters have special meanings and are described in Appendix N. Example: The asterisk (*) is a metacharacter that enables wildcard searching. For example a search for garden* would find garden, gardens, gardener and gardening. A list of the regular expressions which can be used in SDLX is given in Appendix N. Dialog boxes used to create a set of segmentation rules Segmentation Rules dialog box This dialog is displayed when you click the Segmentation Rules button. It lists all of the available segmentation rules and from here you can view the rules, edit rules and create new rules. This is also where you select the rules that you wish to be active. The active rules are the ones that will be used to segment new files being imported for translation. Define Rules dialog box This dialog box is where you create and maintain segmentation rules. 52

57 Character sets Language rules Maps Select the character set(s) to be used for a language. For a language (or language group), identify the characters and character combinations after which text should be split. Also identify the characters where text should not be split. When a file is imported the language contained in the file is identified and assigned the appropriate language code. Maps are used to link language rules to language codes. Edit Character Set Specify the characters contained in a character set. In SDLX the characters are grouped into digits, white spaces and word characters. 53

58 A character set can contain characters from any code page; typically however a set usually contains characters from a single code page. There is a predefined set of characters for each code page and these are displayed in the Digits, Whitespace and Word characters boxes. To add other characters to a code page default set, select the Other check box and enter the character in the edit box on the right of the check box. You can enter the character itself or the hex value for the character preceded by a back slash. Edit Language dialog box This is where, for a selected language, you specify: Where segment breaks should be inserted End rules Where they should not Exceptions. First select the character set to be used and then create the rules based on the characters in the selected set. Each row represents a single rule. In this example the first rule ([\.\?!]+\s) will be interpreted as follows: Insert a segment break where there is a full stop or a question mark or an exclamation mark followed by a space. Insert the break before the space. The second rule (/n) instructs SDLX to insert a segment break immediately before a line break. First select the character set on which the rules will be based. The rules themselves are created in the Language Rule dialog box. To create language rules you need to understand how to use regular expressions (see Appendix N). Language Rule dialog box This dialog is where you create a language rule. The same dialog is used for end rules and exceptions. It is displayed when from the Edit Language dialog box you either: 54

59 Click the Add button, or Select an existing rule and click the Edit button. Create rules by entering the elements that make up the rule into the appropriate box (Before Break or After Break) or selecting the elements from a sub-menu. To select rule elements, place the cursor in either the Before Break box or the After Break box and click the Insert button to display the sub-menu of options available for selection. Once you have created a set of rules you have to link it to a language code. This is done in the Maps dialog box. Edit Maps dialog box This is where you tell SDLX which set of language rules to use on a file being imported. When a file is imported the language contained in the file is identified and assigned the appropriate language code. Maps link language codes to language rules. If you add more than one map per set of rules, SDLX will try each map in turn (starting at the top of the list) until it finds one containing the language code of the import file. 55

60 Use these arrows to move a selected code/rule combination up or down the list. Click the down arrows and select a language code and set of rules. Where the language code in the file matches the regular expression here, apply this language rule. The value in the Language code box is a regular expression. In this example the first entry is JA.*. This means that on any file where the language code is - JA followed by any number of any other types of character SDLX will use the Japanese language rule. Important Note: The order of the entries in the Language code box is significant. SDLX checks them one by one, starting at the top, looking for a match. As soon as it finds one it automatically applies the corresponding language rule. This is why it is important to have a catch-all entry in the Language code column at the very bottom of the list; it must match all of the language codes that do not match any of the preceding entries. Using this method means that you do not have to add a separate entry for every one of the (140+) available language codes. 56

61 Create a new Segmentation Rule We recommend that instead of creating a new segmentation rule from scratch you check the existing rules, find one that closely matches the rule you need, copy this and edit the copy to create the new rule. The procedure below describes how to do this. Part 1 Display the Segmentation Rules dialog box From the SDLX SwitchBoard, select Tools, Options, Segmentation Rules. From the Project Import Wizard, click the Segmentation Rules button on the Options screen. Part 2 Create the new rule 1. Select the existing rule to be copied. 2. Click the Copy button. The Copy Segmentation Rules dialog box is displayed. 3. Enter the name for the new rule and click OK. 4. Select the new rule and click the Edit button. The Define Rules dialog box is displayed. If you want to create a new character set you want to create a new map based on an existing one then select the character set to be copied and click the Edit button. The Edit Character Set dialog box is displayed. Make the required changes and click the Save As button. The Add New Definition dialog box is displayed. Specify a name for the new character set and click OK. If you do not want to change anything else go to step 7. select the map to be copied and click the Edit button. The Edit Maps dialog box is displayed. Make the required changes and click the Save As button. The Add New Definition dialog box is displayed. Specify the name for the new map and click OK. If you do not want to change anything else go to step 7. 57

62 you want to create a new language rule based on an existing one select the rule to be copied and click the Copy button. The Copy Definition dialog box is displayed. Enter the name for the new rule and click OK. Select the new rule and click the Edit button. The Edit Language dialog box is displayed. Go to step Edit the End Rules and Exceptions: If you want to delete a rule you want to rename a rule you want to edit a rule you want to add a new rule you want to create a new rule by copying and editing an existing one then select the rule and click the Remove button. select the rule and click the Rename button. select the rule and click the Edit button. The Language Rule dialog box is displayed. Make the change and click OK. click the Add button. The Language Rule dialog box is displayed. Add the new rule conditions. For example if you want SDLX to insert a segment break wherever there is a colon followed by a space you would enter: : in the Before break box and \s in the After break box. You can paste values into the fields or type them or select them from a list. To select values, click the Insert button and select the required sub-menu and menu options. select the rule to be copied and click the Copy button. A copy of the rule is placed at the bottom of the list in the End Rules box. Select the rule and click the Edit button. The Language Rule dialog box is displayed. Make the change and click OK. 6. Click the Save button when you have finished. The Define Rules dialog box is redisplayed. 7. Click the Close button. The Segmentation Rules dialog box is redisplayed. If you want to set the new segmentation rule as the active rule then select the rule and click the Set Active button. 8. Click the Close button. 58

63 Import a nosplit.txt file If you used a nosplit.txt file in previous versions of SDLX, you can import this file and the exceptions defined in it will be used to create a custom segmentation rule. First you must create a text file containing all of your No Split rules and then import this into a custom language rule. To import existing No-Split rules you need to: 1. Outside SDLX, create a.txt file called NoSplit.txt and add your no split rules to this file. 2. Display the SDLX SwitchBoard. 3. Select Tools, Options, Segmentation rules. 4. Select the Default Rules and click the Copy button. The Copy Segmentation Rules dialog box is displayed. 5. Enter a name for the new rule and click OK. 6. Select your new segmentation rule and click the Edit button. The Define Rules dialog box is displayed. 7. Select the Default entry in the Language rules part of the screen. 8. Click the Edit button. The Edit Language dialog box is displayed. 9. Click the Options button and select: Import NoSplit.txt file. 10. Select the appropriate option fro your data, with regular expressions or without them. The Open dialog box is displayed. 11. Locate the NoSplit.txt file and click Open. The file contents are now imported. When the import is finished this dialog box is displayed. 12. Click OK. 13. Click Save and then Close. When the Segmentation Rules dialog box is redisplayed, if you want the new rule to be the active rule, select the rule and click the Set Active button. 14. Click the Close button to close the segmentation Rules dialog box. 59

64 Sharing segmentation rules Each set of segmentation rules is stored in a file with the extension.ssr. The files are stored in the SDLX directory where SDLX was installed. By default, this is C:\Program Files\SDLX\Ssr You can easily share segmentation rules with other SDLX users. For example, you can distribute the files as attachments. Just remember to store any you receive in the C:\Program Files\SDLX\Ssr directory and the rules will be available the next time you use SDLX. 60

65 Appendix N - Regular expressions used in SDLX Special characters Pattern Meaning Notes. Any character If you want to signify a full stop you must escape the character by placing a backslash in front of it. \t A tab character (ASCII 9) \s Any white space character White space characters are user-defined \S Any non-white space character Equivalent to [^\s] \d Any digit Digit characters are user-defined \D Any non-digit Equivalent to [^\d] \w Any word character Word characters are user-defined \W Any non-word character Equivalent to [^\w] \x Introduces a hex character e.g. \x20 = 32 = space ^ Beginning of segment ^\d\. finds "1.", "2." etc. at the start of the segment ^ If used after [ represents logical NOT \ Escapes the next character Followed by. - + *?.$ ^ \ [ ] ( ) { } to match the actual character Pattern matching In this table x is used to represent the character being matched and n represents a number. Substitute the real value for the x and n when creating the regular expression. Pattern Meaning Notes x* Matches zero or more occurrences of the Rea*d character preceding the asterisk. Matches "Red", "Read" and x+ Matches one or more occurrences of the character preceding the plus sign. x? Matches zero or one occurrence of the character preceding the question mark. x{n} x{n,n} x{n,} Matches exactly the number of x characters specified. Matches a number of x characters where the number falls in the specified range. Matches any number of x characters where the number of x characters is equal to or greater than the figure in the brackets. "Reaad" Rea+d Matches "Read" and "Reaad" but not "Red" Rea?d Matches "Red" and "Read" but not "Reaad" Rea{2}d Matches "Reaad" Rea{1,2}d Matches "Read" and "Reaad" but not "Reaaad" Rea{2,}d Matches "Reaad", "Reaaad", "Reaaaad" etc. 61

66 Logical OR operator Red Green light Matches where light = Red or light = Green. (xxx) Expressions Allows grouping e.g. (yo)+ finds "yo", "yoyo", "yoyoyo" etc. [xyz] Character set. Matches any character listed between the brackets. [^xyz] Matches any character except those listed between the brackets 62

67 Appendix O InDesign filter You can create.itd files directly from InDesign files through SDLX. To do this you need both InDesign CS and SDLX 2004 Bonus Release Build 10 (or later) installed on your PC. The InDesign filter is installed as part of the SDLX 2004 Bonus Release but only if you have InDesign CS (3.0) installed. If InDesign CS is not installed at the time of the SDLX Installation then the InDesign filter option will not be available within SDLX. If you do not currently have the InDesign filter option you would need to install InDesign CS and then re-install SDLX to get it. The SDLX InDesign filter installs a plug-in into the InDesign installation folder. This plug-in will only work with InDesign CS (3.0 or 3.01) If, however, you have older InDesign 2.0 files these can be translated by the InDesign filter without having to upgrade the file to InDesign CS (3.0) format, but the translated file will be in InDesign CS (3.0) format. It appears that Adobe does not have a mechanism for converting InDesign CS (3.0) file formats to the older InDesign 2.0 format. How to create ITDs from InDesign files 1. Start SDLX, and click the Project Wizard button. 2. Select Import files in to a new project and click OK. The SDLX Project Import dialog box is displayed. 3. Select InDesign CS from file type selection list then click the Option button. The InDesign CS Filter Options dialog box is displayed. Select this option and click the Options button to display the InDesign CS Filter Options dialog box. 63

68 4. Select the required options and click OK. If you select the Ignore Kerning option you select the Extract index topics option you select the Extract auto-generated text option you select the Remove style overrides on Merge option then kerning formatting will be removed from text before it is placed in the.itd. each index will be extracted to a separate.itd file that corresponds with the.indd file where the index is defined. all auto-generated text (a table of contents or index for example) will be included in the.itd for translation. any formatting applied to text during translation without changing the underlying style of the text, will be removed automatically when the text is exported back to InDesign format. For example, text may have been highlighted or made bold or had the font colour changed. 5. Click the down arrow in the Source language box and select the appropriate source language. 6. Select the required target language from the drop down window and then click the Add button. The selected language is added in the Target languages list box. You can select as many languages as you wish. Select target languages here 7. Click Next when you have finished selecting languages. 8. Browse to the source file folder location and click OK. 9. For Target language folder, click Default. This results in the target language folder being created under the source file folder. 10. Click OK. 64

69 11. If you want OTF files to be created as well as ITDs, select the Remove tag file when ITD is generated check box (this removes the default selection). Note: OTFs (OpenTag Files) are used in the SDL Analyse module to obtain word counts and other statistics. 12. Click Next and then click Next again to create the.itd files. Create translated InDesign files from ITDs 1. Make sure that the ITD files are in exactly the same location they were in when they were created. If the folder structure has changed they will not export back. 2. Start SDLX, and click the Project Wizard button. 3. Select Export files from an existing project and click OK. 4. Select I want to search for translation documents. 5. Click Next. 6. Click Browse and navigate to the folder that contains the translated ITD files. 7. Click Next. 8. Click Next to create translated InDesign files. Note: When you create the translated InDesign CS documents the original source files (*.indd) that were used to create the initial.itd files must be in the same place on your hard disk or network. 65