French here !

[Pure]

Hey i begun to translate, but I see somes files you give me its ini files or something like this, its not dialog and there is write (inside) ---------"partie qui bug--------

like a prob with this files, but I dont understand how it work, and what is for, can you explain me ?

 

[zorglub]

Well, in all case don't worry about the ini files, I am the one assigned to them...
As I think I told you in 'Instructions.txt' I sent you, those ini files are normaly located in ...\RESOURCE\INI\TEXTS\FRENCH.
'Copie de common.ini' and 'interface_strings_progression.txt' are not used by the game, and should be kept away from the game folders. There are copies of Common.ini and Interface_strings.ini, but without all the elements that have been alreday translated - it indicate us what is remaining.
I've added 'Partie qui bug' because we have some serious difficulties here. But first how those ini files work...

Quite complicate to explain... Let's take an exemple : open ...\PROGRAM\INTERFACE\NationRelation.c . This file code how the Diplomatic Relation menu looks like and works in the game men (the one you access pressing F2.) So this file basicly says what picture is used as the background, where are the differents flags located, what happen when you click on a arrow... And it says which text is where.
For exemple :
<!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1--> {GameInterface.strings.FlagRelation = XI_ConvertString("Relation based on flag") + ": " + XI_ConvertString(tempstring);}<!--c2--></div><!--ec2-->
Here we have this interesting part : "Relation based on flag". If you search this in the english Common.ini, you will find this line :
<!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1-->string = Relation based on flag,"Relation based on flag"<!--c2--></div><!--ec2-->
That's to say that the game put here the phrase linked to 'Relation based on flag' in common.ini, depending on witch language you're using. For exemple, in the russian common.ini you have :
<!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1-->string = Relation based on flag,"��� ���� ������"<!--c2--></div><!--ec2-->.
For the French common.ini, we will have to put something like :
<!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1-->string = Relation based on flag,"Attitude par rapport à nos couleurs"<!--c2--></div><!--ec2-->

Voilà... Hope this was clear enough. Of course this doesn't mean we should never modify a .c file. But again normaly I am doing all this stuff myself... Try to concentrate on the dialogs : its much easier to translate!



About the 'partie qui bug'. sometimes we have complicated sentences with lot of important adjectives, whitch are not located at the same place in the English sentence then in the french sentence. And even worst - sometime we have the problem of French masculin/feminin.
ex : a good saber & a good rapier = un bon sabre & une bonne rapière... <img src="http://forum.piratesahoy.net/public/style_emoticons/<#EMO_DIR#>/modding.gif" style="vertical-align:middle" emoid="" border="0" alt="modding.gif" />

That's why for the moment the complicate part of 'you equiped a fine badelaire' or 'you've found a badly worn saber' isn't translated, and will be extremely difficult to do...

 

[Pieter Boelen]

I would personally not bother about the "un" vs "une". In that Quick-Equip code I wrote, I didn't bother to differentiate between "a" and "and" either, which WOULD be required for 100% proper grammar It would just require too much coding with too little improvement to the game. I would prefer it if all code in the .c files could be kept as they are a much as possible. If additional code needs to be added for grammar purposes, I'm afraid that might be the cause of bugs and/or compatibility problems. Especially when trying to merge the translation work into Build 14. <img src="style_emoticons/<#EMO_DIR#>/unsure.gif" style="vertical-align:middle" emoid=":?" border="0" alt="unsure.gif" />

 

[zorglub]

all code in the .c files could be kept as they are a much as possible

Yes, that's the goal. Trying to mess as little as possible with the .c files, and not having them being unreadable... The simplier the better. But your short quick-equip code is really bothering me, I'll have to find a solution - anyway that's not the priority for the moment.

 

[Pieter Boelen]

I'm sorry about the Quick-Equip code. I tried to make it as simple as possible while still having it do what I want. Personally I don't care much about small grammar errors if it means much simpler code. <img src="style_emoticons/<#EMO_DIR#>/unsure.gif" style="vertical-align:middle" emoid=":?" border="0" alt="unsure.gif" />

 

[Pure]

Just about your problem : for a good saber & a good rapier

I dont know where its used, but if its only on the inventory screen you can translate without "a" like
bon sabre / bonne rapière.

At least if gender are a problem maybe you can use tips like :

sabre bonne facture / sabre mauvaise facture / sabre facture moyenne
rapière bonne facture ....

like that alla will be in the same gender.

(just wanna help ^^)

 

[zorglub]

Pure... Seems like you didn't play a lot...
I already had this idea.

Check your inventory in game, you should see something like this :
"sabre hors-pair", "badelaire en mauvais état" etc...
I didn't used 'facture' because the quality of the blade slowly decreases each time you use it... So it's more a question of 'état' than 'facture'. But if you have better expressions than mines, please tell!

But for the quick-equip code I have some other problems. (the article, + "vous vous êtes équipé" : there should be a sex check here, for "vous vous êtes équipée". I personally don't like "équip2(e), or "équipé-e-s" ...)
I'll try to think over this week-end at the problem.