Hello verdy!
My first post to the forum should have been in [Welcome to antiX]. Also, I didn’t put my post to @Robin in [Reply].
No need to be sorry, really. We are glad you are with us.
On the contrary, it’s me who has to apologise, not answering already to your detection that in the transifex resource everything looks fine, while the bootmenu of antiX 23 still looks odd in Japanese language.
If you could direct me to another appropriate place, I will move there.
I would have done this already, but unfortunately I wasn’t able myself to find either the reason or another position. We’ll have to wait for @anticapitalista being back from being busy in real life (see: Posting #101722). I’ll describe what I did meanwhile, so you can learn some methods I commonly use to look up strings in such cases in the translation resources.
Basically, you can (mostly) always update your individual system immediately after editing the translation entries on transifex following these steps, (at least as long it’s about a gettext type ressource, readily identifiable by the file name endings .po on transifex. Download the file after editing:

Then on your local drive either install the GUI tool “poedit” (sudo apt-get update && sudo apt-get install poedit), open the file within it, and save it. That sounds ridiculous, I’m aware, but actually poedit saves not only the file itself but an additional machine readable version of this file (with the file name ending .mo ). Then it’s enough to copy this very freshly created .mo file to the system folder /usr/share/locale/ja/LC_MESSAGES, you’ll need root privileges and you can do it on GUI using zzzFM file manager from antiX main Menu, section Programs → System (right click on the file, from context menu select the Submenu Actions → Root and there click Copy To. Select the folder mentioned as target.
Btw, you can further edit the .po file locally if you are not content with the results after checking the visible results, and upload it only back to transifex after everything looks fine, using the procedure outlined for download, but within the menu transifex provides (see screenshot) use the “Upload File” entry instead. (There is a console shortcut way to do all this, please let me know in case you want to learn it, then I’ll outline it also.)
After having outlined the procedure you can apply on all resources marked with the grey PO label preceding the resource name in this listing: https://www.transifex.com/anticapitalista/antix-development/content/ here some additional methods, handy at transifex:
There is a “search strings” function in the top transifex site. You can use it like this:
https://www.transifex.com/anticapitalista/search/?q=translation_text%3A%E3%83%A1%E3%83%8B%E3%83%A5%E3%83%BC
This way you can check for all resources containing the very string. (you need to enter the proper search pattern descriptor preceding your (single quoted) search string. In the example the descriptor chosen reads “translation_text:’…’“, but you might also search for source strings using source_text:’…’ . You can apply all types of search pattern descriptors available from the pulldown menus below search entry field to refine the search. (please be aware: the search shows only 10 results per page, you can change this from the “Items per page” pulldown, or just stick to proceeding page by page through the search results.
With this background you’ll understand the reason why I didn’t answer before:
I wasn’t able by now to look up the respective .mo file for the live-bootloader resource from transifex within the /usr/share/locale/<lang_id>/LC_MESSAGES folder for any language, neither on antiX 23 nor on antiX 21/22. And also I wasn’t able to find out whether another transifex resource was used, assuming I’ve pointed you to a wrong place (I’m sorry for that, if it turns out to be true). There is a slight possibility anticapitalista has simply used an outdated language file resource for building the alpha testing ISO of antiX 23, and everything is fine hopefully in upcoming beta release already. We’ll have just to wait for a statement from him about this issue.
Btw, I can see from your screenshot: There are some stings untranslated still for you in antiX boot menu, above and below the Japanese strings you’ve marked. This needs to get fixed also, you are perfectly true.
In the meantime, you could check for missing translated strings on antiX desktop or all other places in system in your language.
If some translation is missing, please don’t hesitate to report here in this forum. We’ll help you best we can to make them work.
And now, please allow me another question, maybe you can help me find out how to decide. Somebody has asked on transifex for adding some Japanese sub-languages some weeks ago:
Project language requested: The Japanese (Hiragana) language was requested for the antiX-contribs project by Deleted User
Project language requested: The Japanese (Japan) language was requested for the antiX-contribs project by Deleted User
Since the user is marked as “Deleted User” on transifex, I can’t answer to him for asking whether there is a difference between Japanese and Japanese (Japan), so I could really need your assistance in this decision. Basically in the first place the two (or three) significant character (base) language ID like »jp« should be filled in, it will be automatically used for all languages with four (up to six) significant character (country specific) language ID like »ja_JP«. The latter only need to be filled in for strings which differ from entries present already in the two significant ID characters base language.
I believe jp_JP is identically to jp , so we don’t need jp_JP additionally. Please let me know if I’m mistaken.
And then about Japanese (Hiragana). Is this language used commonly in Japan or elsewhere? If so, we could add it if there are translators willing to fill in the strings in this language. I wasn’t able to find an online machine translator for this language allowing scripted access, and also Debian doesn’t to support this locale (you could check yourself reading the file cat /usr/share/i18n/SUPPORTED on your system, which contains all languages recently supported by debian). For all languages not listed there, debian would need to accept a request for addition, to have them available. Since I can’t read or speak Japanese language and don’t know pretty much next to nothing about the language, it would be a great help if you could make some remarks or suggestions about the question of adding these requested languages to antiX.
Many greetings
Robin
——————
P.S.: このフォーラムでの質問を日本語から英語に翻訳し、同様に回答を日本語に戻すには、https://www.deepl.com/translator#en/ja を使用することができます。
Windows is like a submarine. Open a window and serious problems will start.