• New Horizons on Maelstrom
    Maelstrom New Horizons


    Visit our website www.piratehorizons.com to quickly find download links for the newest versions of our New Horizons mods Beyond New Horizons and Maelstrom New Horizons!

WIP Spanish translation

Nice, thanks. But wouldn't it be better to create a separate file for that particular storyline, like the others do? I had already gone ahead and created one, although I forgot to include the "Fighting" and "not-Fighting" parts. But I can use the general file if you prefer it that way.

About nicknames, that I can deal with myself as I find them, wasn't thinking in any particular instance.
 
I didn't notice that some storylines have separate files. I'll see about writing one up because there are more Indians whose names will probably need the same treatment - the ones in the Taino village on Isla Mona.
 
I appreciate that. It'd take me ages to look for all of them myself.

Yet another quirk of the translation. The title of the tutorial mission on international relations (and a few more that worked previously but I had to change because special characters) shows only as "erro", whatever I type in the title line.
(also I found even more texts that don't admit sepecial characters, there's more than I thought). The fun just never ends, does it?
 
Last edited:
Homo eructus said:
Yet another quirk of the translation. The title of the tutorial mission on international relations (and a few more that worked previously but I had to change because special characters) shows only as "erro", whatever I type in the title line.
(also I found even more texts that don't admit sepecial characters, there's more than I thought). The fun just never ends, does it?
Click to expand...
That's just a regular queststext file, isn't it? :shock
 
It seems every quest title I've modified to get rid of the special characters, even if I put it back the way it was, gives the same "erro", not even full "error"

Edit: Well, not all of them, it seems. Some actually work, so thare's not even a recognizable pattern as for why the others don't
 
Last edited:
I even replaced all the affected quests with an earlier back up from before the "erro" appeared and it still shows. I'll try replacing them with the original English files just to check if it's not corrupted beyond all repair, and if I can edit them again from there, but if that fails, I'm officially out of ideas other than a fresh installation.

Also I tried to translate the wind logs from WhrWeather.c using the XI_ConvertString and adding the new strings to commons.ini, but it didn't work (the logs don't show at all on screen). Should I use TrasnlateString instead or other? (I don't really know what's the difference) or maybe add the strings to interfacestrings instead of commons?
Code: 
bool ShowWindLog = false;
   string logstr = "";
   string compasstype = CheckCharacterEquipByGroup(pchar, COMPASS_ITEM_TYPE);
   if (winds == 0)           logstr = XI_ConvertString("The air is calm");
   if (winds > 0 && winds <= 2)   logstr = XI_ConvertString("There are light airs ");
   if (winds > 2 && winds <= 6)   logstr = XI_ConvertString("There is a light breeze ");
   if (winds > 6 && winds <=10)   logstr = XI_ConvertString("There is a gentle breeze ");
   if (winds >10 && winds <=15)   logstr = XI_ConvertString("There is a moderate breeze ");
   if (winds >15 && winds <=20)   logstr = XI_ConvertString("There is a fresh breeze ");
   if (winds >20 && winds <=27)   logstr = XI_ConvertString("There is a strong breeze ");
   if (winds >27)           logstr = XI_ConvertString("There is a near gale ");
 
Last edited:
Homo eructus said:
Also I tried to translate the wind logs from WhrWeather.c using the XI_ConvertString and adding the new strings to commons.ini, but it didn't work (the logs don't show at all on screen). Should I use TrasnlateString instead or other? (I don't really know what's the difference) or maybe add the strings to interfacestrings instead of commons?
Click to expand...
XI_ConvertString only checks common.ini, if I recall correctly.
 
They should be excactly the same as the ones in the textfiles. so if the ones in the textfiles don't have an extra space you need to make sure that's also the case in the c files
 
That's what I did. The weird part is that it didn't work when both the c file and the txt file had the extra spaces and were also exactly the same. Even weirder when the next strings (the ones for "the wind comes from the ... at ... kts") did work with the spaces (luckily, all the words would display bunched together otherwise)
 
Normally leading and trailing spaces are excluded from the translation strings anyway.
I don't know why, but it can't hurt and maybe this here DOES explain why.
 
You must log in or register to reply here.
Back
Top