m-stgt

Hello Erich! Based on your hint about Beta UTF-8 I prepared an "internationalisation update" of my Nut CPU firmware interpreter which is published now. Instead of a "central transliteration service" I implemented several specialised for display, printer, tree-view of wand paper keyboard, etc. Observations: * counting characters fails, instead count bytes in ASCII representation, * rexxc lacks an 'addressing mode' option, thus to prepare sourceless executable files for publishing two PCs are needed,...

Hello Jeremy! Sorry to reply so long after you posted... Never mind, expedient solutions are welcome at any time :) Instead of [...] display the bmp. That approach works for several simulations with focus on a surface as close as possible to the role model. I've considered to do what you suggest, but for now I follow Erich's advice, and I plan to publish an "internationalisation update" of my toy within a month or so. Best, M.

Hello Erich! I do have to retract my assertion edit control displays UTF-8 flawlessly, tree view does not. Sorry if I forwarded my confusion. Meanwhile I may precise: ooDialog static text displays on an UTF-8 enabled PC glyphs like Sigma or "lazy T" no matter if using "Courier New" or "IBM Plex Mono Medm" as font. In contrast, in ooDialog tree view this holds true only when using "Courier New". With "IBM Plex Mono Medm" Sigma will show only if prepended with a right-pointing arrow. To show a Sigma...

Hello Erich! can you provide a small test case that shows the issue? I try to boil down the issue as much as possible, sorry if my explanation is too lengthy. To show what I do you may take a look here Within the branch node "GTOs and XEQs for CAT 1" will list alpha labels, which may use characters not available in CP 1252. Up to now I replaced Sigma Σ by paragraph §, what looked funny but worked. Now with UTF-8 Sigma shows in the Display but not in a. m. tree view. With UTF-8 now a substitution...

Next issue: To append text to a multiline edit control I have to place the 'caret' past the last character. Up to now I did so with curva = pastr~lines curva = pastr~lineIndex(curva) + pastr~lineLength(curva) curva = pastr~select(curva, curva) /* no select, set caret only */ UTF-8 enabled this fails, I guess a little discrepancy in counting chars and bytes. A curva *= 3 before select helps in my case (with mainly single-byte characters). My conclusion: a PC with Beta UTF-8 enabled turns ooRexx/ooDialog...

Halfway success only. While ooDialog's edit control displays UTF-8 flawlessly, tree view does not. In addition I'm taken all codepoints above '7F'x within tree view. Nevertheless I'll keep UTF-8 enabled me think. /M.

Success! With your hint to Beta UTF-8 it's now the very first time my "Nut CPU firmware interpreter" may display Σ (Sigma) like the role model HP41. Because I simulate its segmented display by ordinary characters I substituted the Sigma by §, what is a stopgap -- what was a stopgap :) Thank you Erich! /M.

Hallo Erich! TY for the additional information. No sure what you mean by dual. Sorry for ambiguities. Dual-use source in the sense of same REXX program usable on Beta UTF-8 enabled Windows and also usable on not Beta UTF-8 enabled Windows. I've identified already a show-stopper: out = translate(in, ditrl) with ditrl a simple string of characters. After shifting to Beta UTF-8 the editor now files ooRexx programs UTF-8 encoded what results in ditrl being interspersed with "double-byte characters" --...