[Home] [Downloads] [Search] [Help/forum]

Gammon Software Solutions forum

See www.mushclient.com/spam for dealing with forum spam. Please read the MUSHclient FAQ!

[Folder]  Entire forum
-> [Folder]  MUSHclient
. -> [Folder]  Bug reports
. . -> [Subject]  "Translate German characters" not working with aliases
Home  |  Users  |  Search  |  FAQ
Username:
Register forum user name
Password:
Forgotten password?
(New message)
Subject: "Translate German characters" not working with aliases
Name:
Your forum user name.
Register forum user name
Password:
Your forum password.
Forgotten password?
Message:
Message to be posted (in English, please).
Forum codes:
Check this if your message uses 'forum codes' or templates (auto-detected for new posts).
Forum codes Templates

Save this message ...

Subject review (reverse sequence)

Posted by Nick Gammon   Australia  (18,770 posts)  [Biography] bio   Forum Administrator
Date Wed 26 May 2004 12:40 AM (UTC)  [ quote  ]
Message
OK, I have changed my mind. I will leave in the new script routine, which is very small, but have changed the way it works to translate the umlauts just *before* sending to the MUD, rather than just *after* you type something.

After all, if you want them translated you always want them translated, right? Even if they come from a script, a speedwalk, a disk file, or whatever.
- Nick Gammon

www.gammon.com.au, www.mushclient.com
[Go to top] top
Posted by Nick Gammon   Australia  (18,770 posts)  [Biography] bio   Forum Administrator
Date Wed 26 May 2004 12:17 AM (UTC)  [ quote  ]

Amended on Wed 26 May 2004 12:29 AM (UTC) by Nick Gammon

Message
Hmm - I am now sharing your doubt as to where this translation should go, if anywhere.

At present the "translate German characters" option is honoured for "send to":


  • world (ie. to the MUD)

  • command queue (ie. to the MUD after the speedwalk delay)

  • immediate (ie. to the MUD, bypassing the speedwalk queue)


However it is *not* done for:


  • command window (you may well want the text "as is", and in any case it would be translated when you sent the command)

  • status line

  • notepad (new, append, replace)

  • output window

  • log file

  • variable

  • execute (it would be translated when the command is re-evaluated)

  • speedwalk (you would not expect umlauts in speedwalks)

  • script (the script can decide what to do with it)



Basically the ones it does *not* translate are generally ones that are not sent back (directly) to the MUD, and are thus considered to be "safe".

However in your case your script is indirectly sending the umlauts back to the MUD (via Send or Queue or whatever).

For maximum flexibility I have added a new script routine (in version 3.50) called TranslateGerman. This will apply those translations to a string of your choosing.

Thus you could do, in your script:


World.queue "give " & TranslateGerman (something) & " to salesperson"




The more I think about it, the more I'm not sure about this. The new routine will be handy, but perhaps the best place for the translation is just before sending, not just after typing. It was added into the "input" configuration box, but is really an "output" configuration. What do you think?

- Nick Gammon

www.gammon.com.au, www.mushclient.com
[Go to top] top
Posted by Nick Gammon   Australia  (18,770 posts)  [Biography] bio   Forum Administrator
Date Mon 10 May 2004 09:43 PM (UTC)  [ quote  ]
Message
Hmm - looks like a bug, I'll look into it.
- Nick Gammon

www.gammon.com.au, www.mushclient.com
[Go to top] top
Posted by Poromenos   Greece  (1,037 posts)  [Biography] bio
Date Mon 10 May 2004 02:49 PM (UTC)  [ quote  ]
Message
Maybe you could do a World.Execute instead of a World.Send?
Vidi, Vici, Veni.
http://porocrom.poromenos.org/ Read it!
[Go to top] top
Posted by Hve   Germany  (11 posts)  [Biography] bio
Date Mon 10 May 2004 12:18 PM (UTC)  [ quote  ]
Message
In a german MUD (which doesn't like umlauts, though), the
"Translate German characters" option allows me to type, for example

öffne tüte

and this will be sent to the MUD as

oeffne tuete

With a trigger like
<alias
script="OnVerkaufe"
match="verkaufe *"
enabled="y"
sequence="100"
>
</alias>
where the OnVerkaufe skript essentially does something like
World.queue "give "&something&" to salesperson",
german character translation does not take place, i.e.
typing
verkaufe tüte
results in the command
give tüte to salesperson
sent to the mud instead of
give tuete to salesperson

I must admit that now when I come to think of it, I'm unsure as well where in the process to place the umlaut translation. Maybe the best place would be immediately before sending, maybe immediately after typing...
[Go to top] top

The dates and times for posts above are shown in Universal Co-ordinated Time (UTC).

To show them in your local time you can join the forum, and then set the 'time correction' field in your profile to the number of hours difference between your location and UTC time.

1,732 views.

[Reply to this subject]  Reply to this subject   [New subject]  Start a new subject   [Refresh] Refresh page

Go to topic:           Search the forum

[Go to top] top

[Home]

Written by Nick Gammon - 5K

Comments to: Gammon Software support
[RH click to get RSS URL] Forum RSS feed ( http://www.gammon.com.au/rss/forum.xml )

[Best viewed with any browser - 2K]    [Internet Contents Rating Association (ICRA) - 2K]    [Web site powered by FutureQuest.Net]