> On Dec 21, 2015, at 10:26 AM, Matej Horvat <matej.hor...@guest.arnes.si>
> wrote:
>
>> On 2015-12-21 15:06, Jerome E. Shidel Jr. wrote:
>>
>> I don’t know if it is would be possible to have FDI keep changing the
>> Codepage and Character set. But, I don’t think Jim would want the
>> added complexity. So, I will not be adding it even if it is possible.
>
> Good luck getting Russian, Chinese, or Japanese then. I'm not sure about
> the others, but not being able to display a user's language properly
> would make a bad impression on the user. ("We care about your language,
> but not really.")
>
>> Any volunteers?
>
> I thought I'd translate it to Slovenian like I did with many other
> programs (but I haven't published all the translations yet). Is there a
> pre-made floppy disk image or something that can be easily used to test
> translations?
There are two ways to test translations.
1) Best way, checkout entire project source. http://github.com/shidel/FDI
Then download V8Power Tools binaries at http://up.lod.bz/V8Power
Extract V8 and put them in your PATH spec.
Put your translations in a sub folder by Language ID under the LANGUAGES
directory.
Run the LangTest.bat file with a parameter for your language. Like:
LangTest EN
The LangTest batch file is comparable with DosBox.
At anytime it is paused, hit CTRL+C to drop out of LangTest.
Make changes to text or frame sizes.
Resume LangTest with ID to pickup in the section you left. Like:
LangTest EN
2) A little easier to test. But will not verify all user displayed text and it
is much harder to use for making corrections.
Download FDI prototype boot image at http://up.lod.bz/FDI
Place language files in sub directory by ID under FDSETUP\SETUP
Boot image then insert Matuesz's all_cd.iso.
Exit installer.
Set LANG=(ID)
Run installer.
Setup.bat adv
Install FreeDOS.
*
The first method is pretty easy and quick. LangTest needs to be told the
language ID each time it is started. But, picks up where you left off when you
drop out and go back. It also shows every possible question and message that a
user could encounter while running FDI.
>
> And I'm not sure about the licensing: how can you license a translation
> under GPL? May translators use another license, such as one of the
> Creative Commons licenses?
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel
------------------------------------------------------------------------------
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
