2013/3/13 Rony G. Flatscher <rony.flatsc...@wu.ac.at>
>
> I would say : That depends on your needs... Do you have some use cases in
> mind ?
>
> Well, thinking about working on Unicode encoded (XML) files and finally
> getting the ability to have all glyphs available that are needed for
> European information systems, which also means interfacing with databases
> that are encoding in Unicode.
>
The favorite encoding for XML is utf-8.
For me, no need of special support by ooRexx, if your goal is to read the
strings as-is and pass them to the database API (except changing the
encoding, if utf-8 not supported by the database API).
"all glyphs available" : for display, I suppose ? because otherwise, I
don't see a problem here.
> No need to make the interpreter kernel dependent on ICU (unless you want
> that) : one or several wrapper classes will be enough. Now, if you want all
> these services natively supported by the kernel, then the class String will
> be adapted, and new classes probably added, and the C++ API adapted.
>
> Probably that is what I would be really after.
>
> Would you have any estimates about the size (code-wise, time-wise) of such
> an endeavor by any chance, knowing that you have a lot of experience in
> Unicode?
>
Sorry Rony, I have no experience of ICU... so no idea :-)
ICU is large, but no need to wrap everything. Some services taken from the
user guide :
Unicode character properties
Unicode normalization
Code page conversion (encoding)
Locale (language + region)
Transliteration
Date and time
Formatting
Searching and sorting (collation)
Text analysis (positions of words, sentences, paragraphs, line wrapping,
regular expressions)
Text layout (bidi : left to right, right to left)
...
>
> Well, the challenge is to use plain ooRexx and create the needed UTF on
> all operating systems from ooRexx' strings.
>
> On Linux it is even mandatory, if one wishes to automate/remote-control
> Linux (as can be done on Windows using OLE), taking advantage of the widely
> unknown DBus transport service when sending strings as arguments as I
> learned while creating an external ooRexx library to support it.
>
> Again BSF4ooRexx can (and in the case of DBus effectively) serves as a
> fallback here.
>
>
So I understand that the main need is to convert from the system default
encoding to utf-8... And vice-versa.
ICU probably not needed here... Each platform supported by ooRexx should
have services to do that (Windows and Linux : yes. Others ? I don't know).
But that would be the opportunity to analyze in depth the ICU services for
code page conversion.
Jean-Louis
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
