>> I don't know if there is an already existing framework for lisp >> application localizations/documentation translation. If there is I'd > Nope. No standard here.
>> For ease of use, the file would be in unicode (which means anything >> from supporting the unicode character set to being encoded in utf-8 >> or 16) and could be easily formatted as a XLIFF file (with tools >> existing within this l18n framework). > The CL standard does not know about Unicode and friends and different > implementations treat such things (when they do) in different way. >> Also documentation (ie not strictly speaking GUI data) would be in a >> format that can similarly be handled by existing CAT tools (xhtml for >> ex). > XML is S-expression in a drag! :) Looks like there is indeed some gardening to do :) Are there projects here going to deal with unicode/xml/practical data extraction from the code ? What you wrote is kind of scary... All the localization/translation memory standards are xml/unicode based, they all pretty much depend on data parsing/filtering to xml based formats, and that is what translators have to deal with pretty much on a daily basis... Jean-Christophe Helary _______________________________________________ Gardeners mailing list [email protected] http://www.lispniks.com/mailman/listinfo/gardeners
