When MB compiles a file, a MBO or a MBX, it includes in its header the CHARSET of the installation. When compiling a project containing an MBO, if that file is not stamped with the charset of the installation where the compiling takes place, MB will refuse to compile it.
That situation was brought to my attention by Lars Nielsen who had sent one of his MBOs (WindowsLatin1) to a Polish fellow who could not insert it in his program (his installation in WindowsLatin2). The work around that was found to work in this case is to hexedit the MBO heading to adjust it to the local charset. I would like to hear from you in this area, to get a confirmation that this work around is correct in various situations, particularly when it involves two-byte language installations. There are two MBOs available for testing that; they are part of the kit we devise to promote the use of Multi-Language Compatibility in applications (the MLC project at www.paris-pc-gis.com/mlc/mlc_main_en.htm <http://www.paris-pc-gis.com/mlc/mlc_main_en.htm> ) We (Bill T and I) have certainly not thought about that extra constraint; we were very happy to have the applications strings directly written on any type of installation to avoid that exact problem; it seems to catch up with us from behind the haystack! We do not know either if that constraint applies also to MBX, i.e. if a MBX will work on any installation whatever is its charset. My feeling is that it does not apply, but is it always true? Jacques Paris e-mail [EMAIL PROTECTED] MapBasic-MapInfo support http://www.paris-pc-gis.com
