I can still reproduce this issue on 1.6.2 server/client.
And when I set Japanese characters on server.properties file like this:
motd=Minecraft\u30B5\u30FC\u30D0\u30FC
the client don't show them properly.
Another screenshots (confirmed on 1.6.2 release server/client). Also untranslatable:
Tooltip for status: '(no connection)'
'Outdated server!' (in the case of server:1.6.1, client:1.6.2)
'Server closed' (when the server is shut downed.)
'Illegal position' (When a player goes further than 32,000,000 blocks. This occurs not only on multiplayer but also singleplayer.)
@Ezekiel What can I do for it? I don't have any rights to update info, so may I clone this issue?
Screenshot. Using minecraft_server.1.6.2.exe on Windows 7.
Ok. Fixed in 1.6.2.
EDIT:
I confirmed this issue only on LAN multiplayer.
I've heard of that this still occurs on the Internet multiplayer servers,
but I cannot test. Sorry about that.
As of 1.6.1, "Scanning for games on your local network" is translated.
As of 1.6.2pre, "Polling..." ,"Can't reach server" and maybe "Communication error" are not translated.
(en_US.lang doesn't have these entries.)
Are there any guidelines about differences between bugs and feature requests?
I can undetstand it's a feature (or a limitation) because regular guest users will not play multiplayer.
But some messages are bug and others are not... what is the difference between them?
There will be custom named mob. Servers should send mobs' name in both unnamed (translatable)
and named (untranslatable). I think same as for the players.
(I am very sorry about funny English.)
All of these strings are not translatable in 1.6.2pre.
'Player' is not an actual username. It is default name for guest account.
Thank you for closing. Users can refer this ticket as 'specification' of .mcmeta.
This maybe belongs to the 'request for enchancement', so please keep this issue closed.
According to RFC 4627:
> JSON text SHALL be encoded in Unicode. The default encoding is UTF-8.
And .lang files are written in UTF-8. Translated end.txt also uses UTF-8 (same as with credits.txt).
Some files are written in UTF-8, and some files are not... this makes us very confusing.
To avoid confusing, Unicode based character encoding should be used in (pseudo) JSON files.
Still happens in 1.6.1.
Still occurs in 1.6.1 release.
Some of the strings shown in screenshots are for debugging.
Messages for normal gameplay must be translated, but debug informations are not needed.
Same resource pack on Mac OS 10.6 with English locale setting.
Shows garbage characters.
Example screenshot: my own language pack for 1.6.1 with Japanese description on Windows 7 64bit/Japanese.
description (generic resources), name and region (language packs) will contain non-ASCII letters.
> In 1.6 zombies no longer have this behaviour.
If so, please mark this issue as 'Work as Intended', not 'Fixed'.
You want to say: Language pack is not updated. Right?
In my environment, old ja_JP.lang is downloaded.
File ja_JP.lang is outdated, and maybe newer one is pushed to us.
But binaries and other resources such as language packs should be synced.
言語パックが更新されていない、でしたら言語パックファイル ja_JP.lang は
適宜更新されますのでお待ちください。
Still I can reproduce this problem on 1.6.2.