database publishing GASSENHUBER DATAform DBP  
 
   
First page  <<  >> Last page
First page  <<  >> Last page
II. DATAformTags 84 Developer handbook DATAformXTension © 1992-2004 www.gassenhuber.de {71} *@ Character set table [0; 1; 2] Allows the creation of a platform independent text with DATAformTags. DATAformXTen- sion converts all character set dependent texts from the Macintosh character set into the Win- dows ANSI character set and vice versa. The Tag *@ is defined for each DATAform object and specifies the character set in which the text as well as the colour names etc. are written. The XTension converts, if necessary, the char- acter set into that of the current platform. DATAformXTension also converts all the names that are contained in XPressTags, such as colour names or style sheet names. Style sheet names e.g. may, unlike a simple text export/import with XPressTags, keep any umlauts if used on various platforms. If DATAformXTension exports a box, it will always export the Tag *@. It shows the database from which platform the text with DATAformTags comes from. It is then up to the database to properly convert the text. In principle the “transmitter” of a text with DATAformTags sends in the Tag *@, denoting the character set encoding its text. The “receiver” converts the text if necessary. *@0    or missing Tag: character set is not specified; no conversion *@1    character set encoding is MacOS *@2    character set encoding is Windows-ANSI DATAformXTension converts the text depending on the current platform: If the XTension is running under QuarkXPress Windows and receives an object with *@1, the text will be converted from Mac into Windows ANSI. If it receives an object with *@0 or *@2, no conversion is performed. If the XTension is running under QuarkXPress Mac and receives an object with*@2, the text will be converted from ANSI into Mac. If it receives an object with*@0 or*@1, no conversion is performed. DATAform 4D interface The character set conversion is taken over entirely by the DATAform 4D interface. Under Mac OS, Windows and equally in platform independent use, the character set is converted automati- cally. (The interface always exports the Tag *@1 as 4D always works internally with the Mac char- acter set. When importing text with DATAformTags all text, colour names etc. are converted if necessary.) (See also the procedure DX_Information in the DATAform 4D interfac, page: 121)