Custom Text Formatting (Previously: Getting long results in a program)

[komame]

(05-12-2024 02:36 PM)Guenter Schink Wrote:  [...] The German text seems to be o.k. when compared to the English text. One might argue about capitalizing words in some places, but I think it's o.k. as they stand in just as vocabulary for parameters.

When it comes to parameter names, it's a matter of certain assumptions I've made. However, if we were to assume that in the English version we write like this:

Syntax:
ATEXTOUT_P(text, [screen], x, y, [fontSize], [textColor], [attr], [alpha], [width], [backColor])

then the translation into German would look like this

Syntax:
ATEXTOUT_P(Text, [Bildschirm], x, y, [Schriftgröße], [Textfarbe], [Attr], [Alpha], [Breite], [Hintergrundfarbe])

which may be more in line with the spelling rules in German (but not entirely consistent with the "camel case" naming convention). However, it's not a matter of translation quality but rather a matter of agreeing on how parameter names should look (which are often written in abbreviations).

(05-12-2024 02:36 PM)Guenter Schink Wrote:  [...] the target for the output isn't a "screen". Output is directed to a "graphics variable (G0..G9)" ("Grafikvariable") aka GROB which may be displayed on the screen.

Regarding the "screen", it's also a matter of terminology (originally Tyann used the term "screen" in our conversations, and I responded in the same way, and somehow it stuck), but your observation is valid. Analyzing the built-in help, different descriptions are used for G0-G9, sometimes simply "graphic" (e.g., TEXTOUT, BLIT, LINE, TRIANGLE), sometimes "GROB" (e.g., PIXON, ARC), and sometimes the description is omitted altogether or simply "G" is used (e.g., FILLPOLY, INVERT_P). I think I'll stick with "GROB" because it's probably the most universal term.

(05-12-2024 02:36 PM)Guenter Schink Wrote:  And a question: You state that the maximum width of the string is 320. I didn't find such a limit in the documentation for TEXTOUT_P. Is this limit specific for ATEXTOUT_P (length of ICON buffer), thus breaking compatibility (in probably very rare cases), or did I simply miss this information?

Now that we've clarified that TEXTOUT_P also has a limit, there's nothing stopping us from increasing the size of the ICON buffer to 511 (plus a few pixels to support italic text).

Günter, thank you very much for your valuable feedback. I'm really glad you didn't find any language errors (that was very important to me).
With the next update, I'll make corrections to the descriptions (in all language versions, including English) according to the above suggestions, and I'll add translations for the other languages available in the HP Prime help.