Re: Capture console output - edita 0.0.7

new topic     » goto parent     » topic index » view thread      » older message » newer message

Pete Lomax wrote:

> On Fri, 18 Feb 2005 13:07:42 +0100, Juergen Luethje wrote:
>
>> I'll try to prove you wrong, and you please try to prove me wrong,
> Yep, that's the general idea blink)

Sometimes I like to say the obvious. Please don't ask me why. blink

> Your mods were helpful, but a gut feeling...
> They have given me some great ideas, though:-
>
> I am now thinking along the lines of eamenus.ew containing:
>
> sequence menus={
> 	{"&File",Main,{},0},
> 	{"&New\t(Ctrl N)",{1},14,{routine_id("newFile"),{"",{""},{}}},
> ...
> (ie the definitive set in english, and parent/shortcut/action stuff)
>
> and eatext_de.e containing eg:
> "&File" = "&Datei"
> ...
> (ie a 1:1 translation)

Nice, that will make the work of translators rather comfortable.

<snip>

>> The way I made it here, the language of course can only be changed at
>> parse-time. But that is not a bad thing IMHO,
> No real issue, but I would prefer an "Options" entry, even if it meant
> shutdown/restart, over editing the source, however trivially.

I agree that this is better.
Just out of curiosity: Do you plan to put the words of the supported
languages (except of English) in plain text files, or DLLs, or ...?

<snip>

I have one more suggestion/wish:
I would appreciate it, if the console output was captured, without an
ugly black console window popping up. However, I don't know how much
efforts or whatever that requires.

Regards,
   Juergen

PS: Have you already looked at Wolf's "multilingual.zip"?

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu