On Wed, 27 June 2001, Pascal Bauermeister wrote:
>...
> > I like that last option, storing it as a theme string. Any objections?
>
>
> I like it too. If I remember well, we can have the default theme define the text,
>and, if we omit the text in overriding themes, it will appear as defined in
Micah Dowty wrote:
>
> Sounds good. How about the client library? The only text it has (besides the command
>line options) is the message for the PicoGUI error dialog. For that, we could:
>
> - Leave it alone. The errors are cryptic enough that it won't matter what language
>the dialog box
Sounds good. How about the client library? The only text it has (besides the command
line options) is the message for the PicoGUI error dialog. For that, we could:
- Leave it alone. The errors are cryptic enough that it won't matter what language the
dialog box is in ;-)
- Somehow get that te
Micah Dowty wrote:
>
> On the whole, PicoGUI itself doesn't generate much text that the end user sees. The
>small amount of text it does use, though, should be internationalized. In addition, a
>standard method of internationalizing PicoGUI clients should be defined.
>
> In PicoGUI itself, the
On the whole, PicoGUI itself doesn't generate much text that the end user sees. The
small amount of text it does use, though, should be internationalized. In addition, a
standard method of internationalizing PicoGUI clients should be defined.
In PicoGUI itself, the following types of text need
