Sample translate file for use with IBM formats ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ They handle the fact that for text files on the QL and/or THOR the character normally used to denote end-of-line is LF, while on IBM and compatible machines the CR LF character sequence is normally used to fulfil this role. This table is set up on the assumption that at the time you load it, you will have the following settings: SOURCE: QL TARGET: IBM On this basis, the following translate will take place if you now simply select the "Copy Files" option from the Main Menu Copying from QL to IBM format: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. change LF to CR LF ;ST #10; #13, #10 Now we translate charcters with values above 127 to their equivalent in the PC-8 character set which is the commonest one on PC's (but not all characters in the QL set have equivalents in the PC one!). ;ST #96; #158 ;ST #128; #132 ;ST #130; #134 ;ST #131; #130 ;ST #132; #148 ;ST #134; #237 ;ST #135; #129 ;ST #136; #135 ;ST #137; #164 ;ST #139; #168 ;ST #141; #133 ;ST #142; #131 ;ST #143; #137 ;ST #144; #138 ;ST #145; #136 ;ST #146; #139 ;ST #147; #161 ;ST #148; #141 ;ST #149; #140 ;ST #150; #162 ;ST #151; #149 ;ST #152; #147 ;ST #153; #163 ;ST #154; #151 ;ST #155; #160 ;ST #156; #226 ;ST #157; #155 ;ST #158; #157 ;ST #159; #96 ;ST #160; #142 ;ST #162; #143 ;ST #163; #144 ;ST #164; #153 ;ST #166; #128 ;ST #167; #154 ;ST #170; #146 ;ST #171; #173 ;ST #172; #224 ;ST #184; #174 ;ST #185; #175 Copying from IBM to QL format: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ If instead after you have loaded this translation table, you select the "Swap Devices" option to reverse the Source and Target devices, then the following translates will be used instead. .. remove CR ;TS #13 Now we translate characters with values above 127 in the PC-8 character set to their equivalent in the QLcharacter set (but remember that not all characters in the QL set have equivalents in the PC one!). ;TS #96; #159 ;TS #128; #166 ;TS #129; #135 ;TS #130; #131 ;TS #131; #142 ;TS #132; #128 ;TS #133; #141 ;TS #134; #130 ;TS #135; #136 ;TS #136; #145 ;TS #137; #143 ;TS #138; #144 ;TS #139; #146 ;TS #140; #149 ;TS #141; #148 ;TS #142; #160 ;TS #143; #162 ;TS #144; #163 ;TS #146; #170 ;TS #147; #152 ;TS #148; #132 ;TS #149; #151 ;TS #151; #154 ;TS #153; #164 ;TS #154; #167 ;TS #155; #157 ;TS #157; #158 ;TS #158; #96 ;TS #160; #155 ;TS #161; #147 ;TS #162; #150 ;TS #163; #153 ;TS #164; #137 ;TS #168; #139 ;TS #173; #171 ;TS #174; #184 ;TS #175; #185 ;TS #224; #172 ;TS #226; #156 ;TS #237; #134 Final Comments ~~~~~~~~~~~~~~ The thing that you always need to remember about such translate tables is that the TS and TS values are always relative to the device settings at the point in time when you originally load the translation table. (Multi)DiscOVER will automatically track for you any "Swap Devices" commands, swapping over the ST and TS settings as part of this Swap so that you always have the correct translates for the direction you currently intend to copy. It is recommended (although not mandatory) that as a rule you set translate tables up such that the source format is QL, and the target format is the alien one. This makes it easier to remember what settings of the Source and Target device you need at the point in time when you load the translate table.