Re: Capture console output - edita 0.0.7
On Fri, 18 Feb 2005 13:07:42 +0100, Juergen Luethje <j.lue at gmx.de>
wrote:
>> I'll try to prove you wrong, and you please try to prove me wrong,
Yep, that's the general idea 
)
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)
and changing the create() calls and the menuHandler() routine and
possibly the charInput() routine in edita.exw to scan menus...
One point I had not even considered was mapping (Ctrl N) to (Strg N).
OK, I might just leave it as a plain text thing, assuming that (Strg
N) automatically means the same as (Ctrl N), but (Yksw D) in some
other language suggests (Ctrl D) ought to be the shortcut (NMP if the
translator fails to map all keys uniquely, you understand).
I suppose the file might start with:
"Ctrl" = "Strg"
"Shift" = "Umsch"
>I believe, my changes are... say... 99.3% pukka.
I could shoot you down... But you've given me a few ideas I would not
otherwise had. Leave it with me, I now have plenty to work on.
>When I include "eatext_de.e", everything seems to work fine.
>But when I include "eatext_en.e", and choose "File" > "New" and press
>[F5], then I get a message box, saying "[Error] DuplicateHandle failed",
>and no text is shown in Edita's Message Area.
This may be due to the problem Al Getz reported, in that
PROCESS_DUP_HANDLE is apparently required.
>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.
>Any way, keeping all the text in a separate file
>saves time and reduces the probability, that some text will not be
>translated by mistake.
I plan on issuing warnings if an xlate file is missing entries, and
using a central message constant area and simple function, for
example:
puts(1,xlt("Out of bounds"))
Somewhere, there would be a complete table of English:German (or
whatever language) translations and if one was avaliable it would use
that. The total size is not going to be more than 50K, tops.
>One problem that I often saw in translation of other programs is with
>dialog windows, when the translated text requires more space than the
I'm aware. The only thing I think I can realistically do is design
using right-aligned labels, but there will always be some problems
that will need to be solved as and when they arise.
Regards and thanks,
Pete
|
Not Categorized, Please Help
|
|
