Bonsoir Jean-Louis,
looking through the commits I stumbled over your commit to rev. 7391 applied to
your sandbox version
of ooRexx, giving the comment:
Revision: 7391
http://oorexx.svn.sourceforge.net/oorexx/?rev=7391&view=rev
Author: jfaucher
Date: 2011-12-19 21:31:09 +0000 (Mon, 19 Dec 2011)
Log Message:
-----------
Moved wide-char oodialog (now outdated) to oodialog.wchar
and then reading "sandbox/jlf/_diary":
===============================================================================
+2011 dec 19
+
+Moved wide-char oodialog (now outdated) to oodialog.wchar and adapted the
makefiles
+to build both standard oodialog and oodialog.wchar. The wide-char version
can be
+still useful to test unicode support by the interpreter.
+
+Next step : merge from trunk.
+
+
+===============================================================================
Does this comment mean that your sandbox version of ooRexx is fully
Unicode-enabled already?
If so, how would you describe its stability? In any case: would it be possible
to get at a binary
version of it (Windows, Linux or Mac, any bitness) to be able to test it over
Christmas?
---
Also another question in this context: what about oodialog.wchar that you state
to be "outdated",
was it fully Unicode-enabled (as wchar and your respective documentation in the
sandbox indicate)?
What about the newest version of oodialog then?
TIA,
---rony
------------------------------------------------------------------------------
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create
new or port existing apps to sell to consumers worldwide. Explore the
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
