Hi,
I suggest to use internally hash array instead of normal array. It will be more flexible on .prg level because user can simply make: trs[ cText ] := cTranslation and then: ? trs[ cText ]
Almost thee same solution I'm using in my local i18n runtime.
Please also remember that you can use hb_serialize*() functions to convert Harbour items to text and hb_deserialize for reverted conversion.
Almost the same solution I'm using in my local i18n runtime. :) I just never wanted to make decision about translation table file format alone.
It's time to make some serialize functions public. See rtl/itemseri.c.
Before that, I have one wish for item serialization (for another purpose, not for i18n). I want a possibility to save all item data including number width and decimals, also to avoid 0.0 be encoded as 0, etc. A possible solution for this can be additional boolean parameter of encoding function. It can have default value .F. for .prg function version to maintain full backward compatibility.
Best regards, Mindaugas _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
