I'm working hard to translate event messages.
However, so many huge sentenses remain yet.
If I cannot finish translation on time for Japanese version release, I will add English version as update. (User will be able to switch languages by a setting file.)
最新情報(固定記事)
※※※※※※※※※※※※※※※※※※※※※※
計画中!★ルビーのスパイ作戦
カードバトルxアドベンチャー製作の最新情報はCi-enにて!
発売中!
★えびげん、ターニャのラインディフェンス(NEW!)
★エヴァいじり
弄ってイかせよう。シミュレーションゲーム!・キャッスルえびる登録情報ページ
・スーサイダー登録情報ページ
・スペルマスター登録情報
・パツィーノの幸せの鳥登録情報
・ミナーヴァ登録情報
・ダンジョンオブエロチックマスター発売中!(プログラム担当)
------------------------------------------------------------
★更新情報(2018/11/01)
※※※※※※※※※※※※※※※※※※※※※※
2015年7月27日月曜日
登録:
コメントの投稿 (Atom)
Don't worry, we can do those translate ourselves.
返信削除Just make progress in the japenese version.
Private translation is OK.
返信削除However, I have the stance that I deny reconstructing data files and re-uploading by others.( Especially re-uploading full packaged commercial products.)
I noticed it from that one web site re-uploaded full packaged files including EXE and translated data files.
I think better ways are;
[1]Request translation as a work to someone.
[2]Make text message file editable.( User will be able to edit it like Skyrim MOD)
[3]Translating by myself.(Current state)
I think [2] or [3] is more better than [1].
Maybe it can be come up as [4]Text message will have a compressed basic file, but can load an external text file over its top?(Some what like Dungeons & Prisoners ~ 竜の乙女と魔孕の島 was doing.)
返信削除Indeed, the [4] is another good way like [2]. But message file's contents does not be ordered at all. (It also contains scenario script, commands, and so on discretely.)
削除So I cannot tell users what AN ID is used for THAT message easily.
I think it should be that I settle the two same files into archived data[A] and external text file[B]. As you say, [B] override [A].
I appreciate the work you're doing on the translation, but I understand it shouldn't hold you back from making progress on the actual game itself. Whatever you decide is the best way to move forward, I'll support.
返信削除Thanks. I will decide the way when a full product is released.
削除Because the scenario script contains functions that user can access to full contents, so I cannot publish the message text file at the trial version. In other hand, what ID is used to messages for trial scenario is difficult to find.
返信削除From above, the trial version will be only Japanese language. Only full product can be edited by external text file to translate messages.( And only message text file is able to be shared between users, I plan.)
If I find any other better way, I will adopt that idea.