On Saturday, June 19, 2004, at 12:29 PM, tedd wrote: >>> Many thanks for any answers >>> >>> tedd >> >> You likely need to be using MLTE or ATSUI, for unicode simplicity I'd >> think (you using that already? Send me ATSUI headers. :) ) >> >> MLTE = Multi-Lingual Text Engine, Editor X used that. ATSUI = Apple >> Type Services for Unicode Imaging. >> >> MLTE headers are done courtesy RP...I may have some ATSUI done in at >> least a portion within a week or two, unless RP gives me a surprise >> birthday present and spares me the agony. ATSUI is what renders, via >> Quartz and Quickdraw, everything you see in your OS X OS experience. >> >> Given the excess of glyphs in the languages you mention, I 'd have no >> clue as to how to do your sorts intelligently, unless you had access >> to the glyph-train equivalents of A-Z in the respective languages. >> >> I do know that the ATSUI reference is very helpful and may offer you >> a direction. There are 2...one an overview describing text and ATSUI >> concepts along with the ATSUI API and the other is ATSUI Reference, >> describing all the widgets and types, etc. >> >> Go to Apple's developer site, type in ATSUI and both should turn up >> within the list. >> >> Robert > > Robert: > > After deliberation and reading -- wow! > > Please correct me if I'm wrong, but what this means is that the > routines you and RP are adding provide FB applications with truly > Global language capabilities -- is this correct? If so, not a minor > feat. > > In other words, if FB programmers use MLTE properly, then their > programs can be used for any language reference by Unicode. This, I > believe, means that no static text should be hard-wired into a > program, but instead be made a variable that could be changed by the > user. > > Is my understanding correct? > > tedd MLTE and ATSUI certainly seem to provide global -text editing- abilities, but not sure if what you seem to be seeking, localization, are directly aided, and easier, without more supporting widget-craft. Project Builder makes localization rather simple, but I am not sure your universal thing, other than the current STR# and such we have now, is available to us when using FB? I've often considered using an external file with all my strings, for localization purposes...each would be loaded simply by line number or other delimiter. However, I think without a 2byte unicode handling system, it still might only work for some scripts, and not other scripts (Kanji,etc) Your best bet is to start something impossible, then get stuck, and post the context of why you are stuck to the list. ;) rc