The Battle for Wesnoth Forums

Below is the link. It is in Japanese . <https://amachamusic.chagasi.com/index.html> Their terms of use (利用規約): (https://amachamusic.chagasi.com/terms.html) ●音楽素材は、ウェブ、映像、ゲーム、ラジオなど、何かのBGMとしてお使い下さい。 ●音楽だけを販売したり、2次配布することは禁止です。 ... It means you can use their music as a BGM but you cannot distribute onl...

I'm not an active translator with Wesnoth, so I would only suggest a way to move the translation catalogs into the add-ons. Does this correctly fit players expectations? If they know about gettext, they expect it. Otherwise, one of their expectations. I think they expect outdated data are imperfect ...

The en_US method would not fit the translation add-on method. The en_US method lacks the synchronizing mechanics at run time, it's a serious problem for the translation add-on that is updated independently. The en_US method needs that the deployers make sure to synchronize the original texts and the...

I have an idea to free the translators from the release schedule of Wesnoth. An add-on in Wesnoth 1.16 can add any translation messages if they belong to a new textdomain in a language, but cannot change the existing textdomains. If an add-on could replace some translation messages in any textdomain...

Is there any way to just...well...mass-encode it all to common utf-8? From VScode preferably? Unless given clear/concise instructions, I won't change anything if it's too time consuming. The newest version that is not corrupted seems to be 1.0.5.78, but some files are already converted to UTF-8 enc...

The version 1.0.5.80 has some strange characters. For example, 11_Legend_Of_The_Water_Dragon.cfg includes U+FFFD (REPLACEMENT CHARACTER) instead of ⁢U+2026 (HORIZONTAL ELLIPSIS). The old version by revansurik seems to be encoded by WINDOWS-1252, so probably we can use "iconv -f WINDOWS-1252 -t ...

I heard weblate.org hosted FOSS projects for free. (https://github.com/naev/naev/issues/158 ... -748379631)
I use weblate.org as a translator in Naev which has more than 10,000 source strings.

MoonyDragon wrote: ↑November 14th, 2021, 5:35 pm ... And a newer japanese translation has been imported, which is hopefully in accordance with licensing and attribution requirements.

I downloaded and confirmed it. Thanks!

I would like to reserve the /translations/wesnoth-se/ folder for the .po files only, so is it okay if I place the accompanying files in the /translations/ folder above it? You can put gpl-3.0.txt and changelog.ja.txt anywhere in the distribution and rename their filenames into proper ones if you wa...

@MoonyDragon Wesnoth 1.14 or later can load the PO files directly. You can just extract the zip file in the "add-ons" folder and remove the old Japanese MO file, so you can use the Japanese translation. GPL requires you to describe your changes if you modify the Japanese translation. If yo...

Where does the Japanese translation come from? It seems to be same as my translation. If it's mine, you violate GPL v3. I'm also afraid you don't realize it's experimental. I don't care the rule of Japanese translation team, and I love some laying-out character in Unicode, but I don't test it on MS-...

a) No Why should we avoid to include variable? I have never annoyed variable expansions. b) Yes, but... IMO, the translators know what sentences are properly in their languages. That is, you should tell translators your requests and recommends, but it's not a necessary comment "we have no reque...

The wmlxgettext from oooo work very fine. But...... Not for the lua files. :lol: Uhm, It seems to work fine to me, but I'm not quite sure because I recently don't play LotI. I use the wmlxgettext with following command line which specifies all cfg and lua files explicitly. wmlxgettext --directory $...

I immediately noticed your problem when I read this subject ;) I had suspected that the current version of wmlxgettext cannot handle WML sources which have some macros, same as the old perl version. I'm not sure this is what you want, but I have a modified wmlxgettext. Its original version was inclu...

I have found some translation issues. Would you fix them at next release? Missing translatable marks. Wrong escaped double quotation marks. A QUOTATION MARK (U+0022) within a WML string must be doubled quote mark (""), not escape with BACKSLASH. https://wiki.wesnoth.org/SyntaxWML Misused h...