Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / fpc-pascal / 2012-08

Resourcestring and multi-line text

3 messages · 2 people ·

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Mark Morgan Lloyd

When putting text into a resourcestring, for example for i18n, what is best practice for multiline blocks?

I'm thinking of, for example, explanatory text that goes on a page in a wizard-style set of dialogues, or a description that appears in a pane when a tree node is clicked.

Mark Morgan Lloyd markMLl .AT. telemetry.co .DOT. uk [Opinions above are the author's, not those of his employers or colleagues]

Reply by email

Marco van de Voort
to Mark Morgan Lloyd

In our previous episode, Mark Morgan Lloyd said:

Show quoted text 6 lines
When putting text into a resourcestring, for example for i18n, what is best practice for multiline blocks? I'm thinking of, for example, explanatory text that goes on a page in a wizard-style set of dialogues, or a description that appears in a pane when a tree node is clicked.

Afaik dxgettext and its editor support this. IIRC they use \n though.

Reply by email

Mark Morgan Lloyd
to Marco van de Voort
Marco van de Voort wrote 9 lines
In our previous episode, Mark Morgan Lloyd said: > When putting text into a resourcestring, for example for i18n, what is > best practice for multiline blocks? > > I'm thinking of, for example, explanatory text that goes on a page in a > wizard-style set of dialogues, or a description that appears in a pane > when a tree node is clicked. Afaik dxgettext and its editor support this. IIRC they use \n though.

Thanks Marco, noted: I don't consider \n to be a dirty word, and have a modified Format() that understands it. My SNMP to Pascal translator inserts LineEnding in constant definitions which works OK, so presumably this would also work with resourcestrings.

Mark Morgan Lloyd markMLl .AT. telemetry.co .DOT. uk [Opinions above are the author's, not those of his employers or colleagues]

Reply by email