Hi Rony,

To clarify this a little regarding ooDialog, there have been huge changes
to the ooDialog code base since Jean-Louis branched it off to his sand
box.  And, since I'm not done making changes / refactoring code, it would
be a very large job for him to bring it up to date.

--
Mark Miesfeld

On Tue, Dec 20, 2011 at 1:51 PM, Jean-Louis Faucher
<jfaucher...@gmail.com>wrote:

> Guten abend Rony
>
>   Does this comment mean that your sandbox version of ooRexx is fully
>> Unicode-enabled already?
>>
>
> no...I did not work on Unicode since several months. But since uft-8 is
> compatible with ascii, it's possible to process utf-8 strings and pass them
> to (or receive them from) oodialog. That's why I say I can use
> oodialog.wchar to test unicode, assuming I restart to work on Unicode.
>
>>
>> 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?
>>
>> The sandbox version is very stable. I run ooRexxShell daily, which loads
> *all* the packages/libraries, including bsf4oorexx. After modifying one of
> the packages, I enter the 'reload' command which reloads everything in a
> few seconds, and I test.
> I can deliver a binary version for Windows (32 bits)  and Mac (64 bits)
> through dropbox. The main thing to test is the RexxContextualSource (that I
> will probably rename RexxBlock) and all its derivatives.
>
>  ---
>>
>> 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?
>>
>
> yes, oodialog.wchar is fully Unicode. Internally, all the strings are
> utf-16 strings. At the boundaries, the multi-bytes strings (which covers
> ascii, utf-8 strings) are converted to/from UTF-16. You have just to
> specify the code page of the multi-bytes strings.
> I don't plan to redo this work for the new oodialog, But the work is not
> lost...
>
> Jean-Louis
>
>
> ------------------------------------------------------------------------------
> 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
>
>
------------------------------------------------------------------------------
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

Reply via email to