Daichi Kawahata wrote: > In other words, that needs source code of other clients modified?
At least, you have to know what messages they use or just accept
that you cannot translate all of them.
> I can't still get interservent message handling certainly. The
> list I've been seeing in these days at the download pane is:
>
> * "HTTP 503 Accodati Full" (Italian, may be)
[...]
That's probably BearShare but I'd think that was just a big i.e.,
someone didn't check what happens with the message and translated
it.
> > In theory, you could simply take the 3-digit response code
> > (e.g., 404) and map this to a prepared message completely
> > ignoring the textual status message.
> In my expecting, I think it might be possible those strings are
> turned translatable if strings ware also associated with certain
> code number other than centered sequential number (404 etc.), by
> using labels in case switch.
There's also the alternate to show both i.e., the original message
along with the canonical (and translated) message. This way you
don't lose any information whilst providing some help for non-English
users.
> However if even each words ('Not', 'Full' etc.) were independent
> and there were words other than English (if my memory is correct
> I had also encountered the language French, German), will it be
> difficult to store corresponded strings in the source code of
> gtkg?
It's not difficult. Someone just has to provide them. Of course, we
can only translate from English to something else. If remote peers
send messages in German, French or whatever we can only use them
as-is. gettext doesn't provide a way to reverse lookup translations.
> > However, this will only work for messages like "404 Not Found"
> > but not so well for "400 Whatever".
> Well, I might still lose your sentence, that means there is no
> certain way if it wasn't dealing with one string especially like
> status '503' case, doesn't that?
Yes, only a few error codes have a definitive standard message
assigned to them and it's not required or maybe not even best
current practice to use them. Even 404 is used with diverse
slightly different messages e.g., "File not found", "Not Found",
"Object not found" etc. Other more vague response codes are used
with a lot more different messages. Sometimes these might even
contain dynamically generated information e.g., a session ID
and other numerical data.
--
Christian
pgpca0oMZWbAk.pgp
Description: PGP signature
