The Battle for Wesnoth Wiki - User contributions [en]

Fosdem2010

2009-12-14T20:15:15Z

Noyga: /* Schedule/Plans */

== General information ==
This page is meant to somehow coordinate the small Wesconf taking place at FOSDEM 2010. That is everyone attending should please list him/herself in the list of arrivals and stuff like this. FOSDEM 2010 will take place at the first weekend in Febuary 2010, on Saturday 6th and Sunday 7th.

* Fosdem - http://fosdem.org/2010/
* [http://www.wesnoth.org/forum/viewtopic.php?p=283311#283311 List with phone numbers] (forum moderators only)

== Schedule/Plans ==
{| border="1" width="100%"
|-
! (nick)name(s)
! Arrival
! Departure
! Accomodation
|-
| AI
| Fri, 5th
| Sun, 7th
| 2go4, booked by Ivanovic
|-
| Boucman
| Fri, 5th
| Mon, 8th
| unknown
|-
| Crab
| Fri, 5th
| Sun, 7th
| unknown
|-
| Fendrin
| Fri, 5th
| Sun, 7th
| 2go4, booked by Ivanovic
|-
| grzywacz & deekay
| Fri, 5th (?)
| Mon, 8th (?)
| unknown
|-
| Ivanovic & chrber
| Fri, 5th
| Sun, 7th
| 2go4, booked by Ivanovic
|-
| mordante
| Fri, 5th
| Sun, 7th
| 2go4, booked by Ivanovic
|-
| Noyga
| Fri, 5th
| Sun, 7th
| unknown
|-
|
|
|
|
|-
|}

For accomodations please keep in mind that parking in the center of Brussels is really problematic. It might make sense to drive to the University where FOSDEM takes place, park there and take the bus into the town center (where some of the hotels/hostels are).

Possible hostels that we at least contacted over the last years (some of them might already be booked out by now!):
* [http://www.chab.be/ CHAB]
* [http://www.2go4.be/ 2go4] Note: groups bigger 6 are not allowed, so we can (officially) not form a complete Wesnoth group at this hostel, got to meet somewhere in town/at the university...
* [http://www.jeugdherbergen.be/brusselE.htm Bruegel YH]

On the official FOSDEM page [http://fosdem.org/2010/practical/accomodation some more possible hotels/hostels] are listed.

== Maps ==
* [http://tinyurl.com/3a65gr Bruegel YH]
* [http://tinyurl.com/35br9c Brussels Central (Train Station) → Bruegel YH]
* [http://tinyurl.com/37d9v4 Bruegel YH → Brussels Central (Train Station) → Novotel Grand Place]
* [http://tinyurl.com/2mzns6 Novotel Grand Place]
* [http://tinyurl.com/3dggg3 CrownePlaza (Europa)]
* [http://tinyurl.com/36epxj FOSDEM]
* [http://tinyurl.com/2w4bms Novotel Grand Place -> FOSDEM]

== Transportation ==
Information about how to reach the FOSDEM is listed at the [http://fosdem.org/2010/practical/transportation official transportation subpage].

Short version of how to get there for those that reside in Bruegel YH and Novotel Grand Place (basically town center):

* Enter Bus 71 (Debrouckere - Central Station ("Gare Centrale") - Delta) somewhere at 'Central Station'
* Leave the bus at "ULB" (crossroads Ave. Adolphe Buyl - Sq. Deveze)
* Walk down Ave. Paul Heger on your right hand.

== Wesnoth Hacking Room ==

Wesnoth will not have a room of its own. Instead we will use one of the "general hacking rooms". So far it is not sure which room it will be, if we do it like the last two years, it will be room number 115 in the building AW1. Last year this was the smaller of the two hacking rooms and we had no real problem with conquering (and holding) the first row in this room. There were not too many power outlets, so this year at least Ivanovic will bring one multi-outlet power strip plus some extension cable (5m or something like this). There is no wired network, everything wireless (and sometimes rather/very unstable!). Beside this you should bring laptops since there are no computers available for hacking.

Short version:
AW1 - Room 115

== Planned discussion ==
We usually discuss all sorts of things at FOSDEM, this section is here to have a small bullet list of things that we actively want to discuss at FOSDEM.
* GSOC 2010: finding mentors, organizing the submission etc..
* FOSDEM 2011 : trying to get a dev room with other games ?
* [wanted: discussion topics!]

== FOSDEM 2009 ==
We were already at FOSDEM 2009, here something as reference:

* [http://www.wesnoth.org/wiki/Fosdem2009 FOSDEM 2009 wiki page]

== FOSDEM 2008 ==
We were already at FOSDEM 2008, here something as reference:

* [http://www.wesnoth.org/forum/viewtopic.php?p=283649#p283649 Forum topic (with group photo)]
* [http://www.wesnoth.org/wiki/Fosdem2008 2008 wiki page]
* [https://mail.gna.org/public/wesnoth-dev/2008-02/msg00078.html Summary of FOSDEM 2008 results]

[[Category:Development]]
[[Category:Wesconf]]

Fosdem2010

2009-12-05T19:57:15Z

Noyga: /* Schedule/Plans */

== General information ==
This page is meant to somehow coordinate the small Wesconf taking place at FOSDEM 2010. That is everyone attending should please list him/herself in the list of arrivals and stuff like this. FOSDEM 2010 will take place at the first weekend in Febuary 2010, on Saturday 6th and Sunday 7th.

* Fosdem - http://fosdem.org/2010/
* [http://www.wesnoth.org/forum/viewtopic.php?p=283311#283311 List with phone numbers] (forum moderators only)

== Schedule/Plans ==
{| border="1" width="100%"
|-
! (nick)name(s)
! Arrival
! Departure
! Accomodation
|-
| Ivanovic & chrber
| Fri, 5th
| Sun, 7th
| unknown
|-
| Crab
| Fri, 5th
| 7th or 8th
| unknown
|-
| grzywacz & deekay
| Fri, 5th (?)
| Mon, 8th (?)
| unknown
|-
| Boucman
| Fri, 5th (?)
| Mon, 8th (?)
| unknown
|-
| mordante
| Fri, 5th
| Sun, 7th
| unknown
|-
| Turuk
| Fri, 5th
| Sun, 7th (?)
| unknown
|-
| Noyga
| Fri, 5th (?)
| Sun, 7th (?)
| unknown
|-
|
|
|
|
|-
|
|
|
|
|-
|}

For accomodations please keep in mind that parking in the center of Brussels is really problematic. It might make sense to drive to the University where FOSDEM takes place, park there and take the bus into the town center (where some of the hotels/hostels are).

Possible hostels that we at least contacted over the last years (some of them might already be booked out by now!):
* [http://www.chab.be/ CHAB]
* [http://www.2go4.be/ 2go4] Note: groups bigger 6 are not allowed, so we can (officially) not form a complete Wesnoth group at this hostel, got to meet somewhere in town/at the university...
* [http://www.jeugdherbergen.be/brusselE.htm Bruegel YH]

On the official FOSDEM page [http://fosdem.org/2010/practical/accomodation some more possible hotels/hostels] are listed.

== Maps ==
* [http://tinyurl.com/3a65gr Bruegel YH]
* [http://tinyurl.com/35br9c Brussels Central (Train Station) → Bruegel YH]
* [http://tinyurl.com/37d9v4 Bruegel YH → Brussels Central (Train Station) → Novotel Grand Place]
* [http://tinyurl.com/2mzns6 Novotel Grand Place]
* [http://tinyurl.com/3dggg3 CrownePlaza (Europa)]
* [http://tinyurl.com/36epxj FOSDEM]
* [http://tinyurl.com/2w4bms Novotel Grand Place -> FOSDEM]

== Transportation ==
Information about how to reach the FOSDEM is listed at the [http://fosdem.org/2010/practical/transportation official transportation subpage].

Short version of how to get there for those that reside in Bruegel YH and Novotel Grand Place (basically town center):

* Enter Bus 71 (Debrouckere - Central Station ("Gare Centrale") - Delta) somewhere at 'Central Station'
* Leave the bus at "ULB" (crossroads Ave. Adolphe Buyl - Sq. Deveze)
* Walk down Ave. Paul Heger on your right hand.

== Wesnoth Hacking Room ==

Wesnoth will not have a room of its own. Instead we will use one of the "general hacking rooms". So far it is not sure which room it will be, if we do it like the last two years, it will be room number 115 in the building AW1. Last year this was the smaller of the two hacking rooms and we had no real problem with conquering (and holding) the first row in this room. There were not too many power outlets, so this year at least Ivanovic will bring one multi-outlet power strip plus some extension cable (5m or something like this). There is no wired network, everything wireless (and sometimes rather/very unstable!). Beside this you should bring laptops since there are no computers available for hacking.

Short version:
AW1 - Room 115

== Planned discussion ==
We usually discuss all sorts of things at FOSDEM, this section is here to have a small bullet list of things that we actively want to discuss at FOSDEM.
* GSOC 2010: finding mentors, organizing the submission etc..
* FOSDEM 2011 : trying to get a dev room with other games ?
* [wanted: discussion topics!]

== FOSDEM 2009 ==
We were already at FOSDEM 2009, here something as reference:

* [http://www.wesnoth.org/wiki/Fosdem2009 FOSDEM 2009 wiki page]

== FOSDEM 2008 ==
We were already at FOSDEM 2008, here something as reference:

* [http://www.wesnoth.org/forum/viewtopic.php?p=283649#p283649 Forum topic (with group photo)]
* [http://www.wesnoth.org/wiki/Fosdem2008 2008 wiki page]
* [https://mail.gna.org/public/wesnoth-dev/2008-02/msg00078.html Summary of FOSDEM 2008 results]

[[Category:Development]]
[[Category:Wesconf]]

FrenchTranslation

2009-01-25T20:59:34Z

Noyga: /* Aujourd'hui, qui fait quoi ? */

Battle for Wesnoth - Traduction française
== Le mot d'introduction ==

Cette page sert à mieux coordonner l'effort de tous et à donner les informations souvent demandées avant de se lancer dans la traduction française.

== Règles de traduction ==
=== Respect des termes de l'univers de Wesnoth ===
Pour améliorer la cohérence de l'ensemble des traductions, utilisez :
# le [http://units.wesnoth.org/1.4/fr_FR/mainline.html dictionnaire des unités], qui vous permet de voir les noms par langues, par races, et par campagnes ;
# le [[NomsCommuns | wiki des noms communs]] ;
# le [[NomsPropres | wiki des noms propres]] ;
# des [http://elsap1.unicaen.fr/cgi-bin/cherches.cgi synonymes] pour enrichir vos phrases.

=== Respect du contexte ===
Il est important de correctement traduire les différents textes. Il ne suffit pas de traduire mot à mot les différentes phrases, il faut aussi faire très attention au contexte.

=== Respect des règles de typographie ===

==== Titres ====
Les titres des campagnes, des scénarios et des chapitres doivent suivre les règles de la langue française. Ces règles se trouvent sur http://fr.wikipedia.org/wiki/Wikipédia:Conventions_typographiques.

==== Ponctuation ====
Les traductions doivent aussi suivre les règles de ponctuation de la langue française, essentielles à un bon affichage du texte ; par exemple, l'utilisation d'une espace fine avant le signe « : » évitera que ce signe ne se trouve en début de ligne d'un texte. Ces règles se trouvent sur http://www.reveenjoie-poesie.com/outils-linguistiques/Typographie_francaise.html.

Il est préférable de ne pas mettre de virgule ni avant le « et », ni avant le « ou » (contrairement à l'anglais).

Remarque :
- sous Windows, la combinaison Alt+(0160) permet d'écrire une espace fine (les parenthèses indiquent qu'il faut maintenir la touche Alt appuyée).
Voici d'autres raccourcis : http://www.crdp-montpellier.fr/cd48/tice/trucs/majuscules.htm#win
- sous linux cette même combinaison est Alt+espace

==== Majuscules ====
Les majuscules doivent être accentuées dans les textes traduits : À, Â, Æ, Ç, É, Ê, È, Î, Ô, Œ, Ù, Û...

Voici également quelques rappels sur des confusions fréquentes :
# pas de majuscules aux noms des races (« nains », « elfes », « orcs », etc.) ;
# majuscules aux noms de clans ou de factions (les humains de « l'Ordre de la Serre Pourpre ») ;
# majuscules aux points cardinaux quand on parle d'une partie d'un tout (« les forêts de l'Ouest » peuvent se trouver à l'est), et minuscule quand on parle de la direction (« aller vers le nord »).

=== Respect des règles de l'orthographe ===
Il est préférable de soigner sa grammaire et son orthographe :
# le CNRS et l'ATILF fournissent un dictionnaire en ligne performant et complet : http://atilf.atilf.fr/
# et vous pourrez vérifier la conjugaison de vos verbes ici : http://www.conjugue-moi.com/.

Les [http://www.academie-francaise.fr/langue/orthographe/regles.html rectifications de l'orthographe préconisées par l'Académie Française] peuvent s'appliquer.

== Principes de traduction pour Wesnoth ==
Le principe est de mettre à jour les fichiers .po, fichiers servant à gérer les traductions dans Wesnoth. Les échanges se font via la mailing list.

=== S'inscrire à la mailing list ===
La mailing list francophone de Wesnoth est l'outil privilégié pour
# d'abord avertir les traducteurs que vous allez commencer une traduction (et éviter de travailler sur le même fichier),
# envoyer ses traductions pour validation ou relecture,
# poser des questions.

Pour s'inscrire à la mailing list, envoyez un mail vide ayant comme sujet « subscribe » (il sera traité par un robot) ; ou cliquez directement ici mailto:wesnoth-request@ml.free.fr?subject=subscribe et envoyez...

Les responsables des différentes mailing list sont ici : [[WesnothTranslations]].

Les archives de la mailing list sont ici : http://news.gmane.org/gmane.games.wesnoth-fr ; vous pouvez vous abonner au serveur de news news.gmane.org (gmane.games.wesnoth-fr).

Il est également possible de discuter sur le canal IRC #wesnothfr (sur irc.freenode.net) ou sur le forum, mais l'équipe de traduction française ne s'y promène que rarement.

=== Récupérer les fichiers .po nécessaires ===
Les fichiers à traduire sont accessibles :
# soit par cette page : http://gettext.wesnoth.org/ (le plus simple),
# soit par le SVN (plus compliqué) : http://svn.gna.org/viewcvs/wesnoth/ (mainline) et http://svn.berlios.de/wsvn/wescamp-i18n (user campaigns).

=== Modifier les fichiers .po et vérifier le statut des lignes traduites ===
Plusieurs logiciels permettent de modifier ces fichiers :
# les éditeurs de texte
#* [http://notepad-plus.sourceforge.net/fr/site.htm notepad++] ;
#* [http://www.textpad.com/ textpad] ;
#* ou, pour Mac, [http://www.barebones.com/products/textwrangler/index.shtml Textwrangler] ;
#* et puis bien d'autres encore...
# ou des éditeurs spécifiques aux fichiers .po
#* [http://www.poedit.net/ poEdit], pour Mac et PC ;
#* [http://i18n.kde.org/tools/kbabel/ KBabel] ;
#* [http://gtranslator.sourceforge.net/ gtranslator].

Chaque champ de traduction possède un statut :
# si vous traduisez pour la première fois un champ, mettez-le en traduction approximative ("fuzzy" en anglais), et ce même si c'est une traduction très basique ; toute traduction doit être relue au moins une fois avant d'être approuvée ;
# si vous relisez un champ, libre à vous de décider de son statut après votre relecture ;
#* sortez-le de son état approximatif si vous le considérez incontestablement bien traduit ;
#* laissez-le à l'état approximatif et demandez une deuxième relecture si vous n'êtes pas sûr de la traduction.

=== Tester sa traduction ===
Si vous le désirez, vous pouvez immédiatement tester votre traduction :
# enlevez l'option fuzzy de la ligne (ou des lignes) que vous voulez vérifier ;
# générez un fichier compilé « .mo » à partir du fichier texte « .po » ;
#*En ligne de commande : la commande « msgfmt » peut être utilisée avec le nom du fichier « .po » (exemple : « msgfmt mon_fichier.po -o mon_fichier.mo » générera « mon_fichier.mo »).
#*Avec l'éditeur « poedit » : « Fichier -> Préférence », onglet « Editeur, cochez la case « Compiler automatiquement les fichiers .mo lors de la sauvegarde » ; sauvez le fichier.
# copiez votre fichier dans le répertoire contenant les traductions et renommez-le ;
#*Sous Windows, <Répertoire d'installation de Wesnoth>\fr\LC_MESSAGES\<Nom du fichier à tester> (Exemple : C:\Wesnoth\po\fr\LC_MESSAGES\wesnoth-utbs.mo) ;
#*Sous Linux, répertoire en fonction de la distribution (Exemple Mandriva : /usr/share/locale/fr/LC_MESSAGES).
# jouez.... jusqu'au moment où le texte traduit est censé apparaître ; il n'est pas nécessaire de tout reprendre depuis le début, une sauvegarde fonctionne. Un texte traduit sans erreur apparaît... traduit.

Remarque : pour accélérer les tests, vous pouvez utiliser le mode debug de Wesnoth :
#Pour passer en mode débug :
#*taper : (pour ouvrir le mode de commande), puis : debug<entrée>
#*ou taper "wesnoth.exe --debug",
#*ou taper "wesnoth.exe -d"
# pour utiliser le mode débug :
#*":debug" entre en mode debug
#*":n" termine le scénario immédiatement

=== Envoyer sa traduction ===
Une traduction terminée est compressée, puis envoyée à la ML.

Il est préférable, en cas de relecture, de signaler les modifications dans le corps du mail, par exemple en faisant comme ci-dessous :
#Exemple 1 (refonte d'une phrase) : N° ligne Anciene version => Nouvelle version.
#Exemple 2 (correction d'une faute, indiquée par des *) : N°Ligne Ancien*n*e version

Il est également possible de générer un fichier différentiel entre l'ancienne et la nouvelle version ; mais l'expérience semble montrer que cela est peu relu.
Cette techique est surtout à utiliser qu'en cas de modifications massives (cas où le suivi ligne à ligne serait complexe et lourd).

=== Attention ===
* Les variables sont indiquées par ''$'' ; il ne faut pas les traduire : par exemple, ''$gold_left'' se traduit par ''$gold_left'' et non pas par ''$or_restant''.

* Il y a un bug récurent dans les fichiers po : lorsque la phrase traduite '''commence''' par ''$'', rien ne s'affiche dans le jeu. Pour corriger le problème, il suffit de mettre un simple espace devant le signe.

* ''\n'' dans la chaîne originale permet de créer un saut de ligne. Il faut le traduire en mettant ''\n'' en français (c'est important : ''gettext'' bugge s'il n'y a pas le même nombre de ''\n'' des deux côtés).

== Aujourd'hui, qui fait quoi ? ==
Ce chapitre vous permet de savoir qui fait quoi...

Date de dernière mise à jour : 25/01/2009
* Traductions
** THoT : Aurélien
** Wesnoth-Editor : Benoît
** Wiki : Adrien (Cernunnos) (inactif ?)
* Relectures / À relire

[[Category:Translations]]

Fosdem2009

2008-12-29T19:41:45Z

Noyga: /* Schedule/Plans */

== General information ==
This page is meant to somehow coordinate the small Wesconf taking place at FOSDEM 2009. That is everyone attending should please list him/herself in the list of arrivals and stuff like this. FOSDEM 2009 will take place at the first weekend in Febuary 2009, on Saturday 7th and Sunday 8th.

* Fosdem - http://fosdem.org/2009/
* [http://www.wesnoth.org/forum/viewtopic.php?p=283311#283311 List with phone numbers] (forum moderators only)

== Schedule/Plans ==
{| border="1" width="100%"
|-
! (nick)name(s)
! Arrival
! Departure
! Accomodation
|-
| Ivanovic & Dragonking
| 6, late afternoon
| 8, evening
| Bruegel YH (not sure yet)
|-
| Mordante
| 6, afternoon (not sure yet)
| 8, evening
| Bruegel YH (not sure yet)
|-
| Boucman
| unknown
| unknown
| unknown
|-
| cib
| probably evening
| not sure yet
| not sure yet
|-
| Noyga
| unknown
| unknown
| unknown
|-
|}

For accomodations please keep in mind that parking in the center of Brussels is really problematic. It might make sense to drive to the University where FOSDEM takes place, park there and take the bus into the town center (where some of the hotels/hostels are).

On the official FOSDEM page [http://fosdem.org/2009/practical/accomodation some possible hotels/hostels] are listed.

== Maps ==
* [http://tinyurl.com/3a65gr Bruegel YH]
* [http://tinyurl.com/35br9c Brussels Central (Train Station) → Bruegel YH]
* [http://tinyurl.com/37d9v4 Bruegel YH → Brussels Central (Train Station) → Novotel Grand Place]
* [http://tinyurl.com/2mzns6 Novotel Grand Place]
* [http://tinyurl.com/3dggg3 CrownePlaza (Europa)]
* [http://tinyurl.com/36epxj FOSDEM]
* [http://tinyurl.com/2w4bms Novotel Grand Place -> FOSDEM]

== Transportation ==
Information about how to reach the FOSDEM is listed at the [http://fosdem.org/2009/practical/transportation official transportation subpage].

Short version of how to get there for those that reside in Bruegel YH and Novotel Grand Place:

* Enter Bus 71 (Debrouckere - Central Station ("Gare Centrale") - Delta) somewhere at 'Central Station'
* Leave the bus at "ULB" (crossroads Ave. Adolphe Buyl - Sq. Deveze)
* Walk down Ave. Paul Heger on your right hand.

== Wesnoth Hacking Room ==

Wesnoth will not have a room of its own. Instead we will use one of the "general hacking rooms". So far it is not sure which room it will be, if we do it like last year, it will be room number 115 in the building AW1. Last year this was the smaller of the two hacking rooms and we had no real problem with conquering (and holding) the first row in this room. There were not too many power outlets, so this year at least Ivanovic will bring one multi-outlet power strip plus some extension cable (5m or so). There is no wired network, everything wireless (and sometimes rather unstable!). Beside this you should bring laptops since there are no desktop machines available for hacking.

Short version:
AW1 - Room 115

== FOSDEM 2008 ==
We were already at FOSDEM 2008, here something as reference:

* [http://www.wesnoth.org/forum/viewtopic.php?p=283649#p283649 Forum topic (with group photo)]
* [http://www.wesnoth.org/wiki/Fosdem2008 2008 wiki page]
* [https://mail.gna.org/public/wesnoth-dev/2008-02/msg00078.html Summary of FOSDEM 2008 results]

[[Category:Development]]
[[Category:Wesconf]]

Fosdem2009

2008-12-29T19:41:10Z

Noyga: /* Schedule/Plans */

== General information ==
This page is meant to somehow coordinate the small Wesconf taking place at FOSDEM 2009. That is everyone attending should please list him/herself in the list of arrivals and stuff like this. FOSDEM 2009 will take place at the first weekend in Febuary 2009, on Saturday 7th and Sunday 8th.

* Fosdem - http://fosdem.org/2009/
* [http://www.wesnoth.org/forum/viewtopic.php?p=283311#283311 List with phone numbers] (forum moderators only)

== Schedule/Plans ==
{| border="1" width="100%"
|-
! (nick)name(s)
! Arrival
! Departure
! Accomodation
|-
| Ivanovic & Dragonking
| 6, late afternoon
| 8, evening
| Bruegel YH (not sure yet)
|-
| Mordante
| 6, afternoon (not sure yet)
| 8, evening
| Bruegel YH (not sure yet)
|-
| Boucman
| unknown
| unknown
| unknown
|-
| cib
| probably evening
| not sure yet
| not sure yet
|-
| Boucman
| unknown
| unknown
| unknown
-
|}

For accomodations please keep in mind that parking in the center of Brussels is really problematic. It might make sense to drive to the University where FOSDEM takes place, park there and take the bus into the town center (where some of the hotels/hostels are).

On the official FOSDEM page [http://fosdem.org/2009/practical/accomodation some possible hotels/hostels] are listed.

== Maps ==
* [http://tinyurl.com/3a65gr Bruegel YH]
* [http://tinyurl.com/35br9c Brussels Central (Train Station) → Bruegel YH]
* [http://tinyurl.com/37d9v4 Bruegel YH → Brussels Central (Train Station) → Novotel Grand Place]
* [http://tinyurl.com/2mzns6 Novotel Grand Place]
* [http://tinyurl.com/3dggg3 CrownePlaza (Europa)]
* [http://tinyurl.com/36epxj FOSDEM]
* [http://tinyurl.com/2w4bms Novotel Grand Place -> FOSDEM]

== Transportation ==
Information about how to reach the FOSDEM is listed at the [http://fosdem.org/2009/practical/transportation official transportation subpage].

Short version of how to get there for those that reside in Bruegel YH and Novotel Grand Place:

* Enter Bus 71 (Debrouckere - Central Station ("Gare Centrale") - Delta) somewhere at 'Central Station'
* Leave the bus at "ULB" (crossroads Ave. Adolphe Buyl - Sq. Deveze)
* Walk down Ave. Paul Heger on your right hand.

== Wesnoth Hacking Room ==

Wesnoth will not have a room of its own. Instead we will use one of the "general hacking rooms". So far it is not sure which room it will be, if we do it like last year, it will be room number 115 in the building AW1. Last year this was the smaller of the two hacking rooms and we had no real problem with conquering (and holding) the first row in this room. There were not too many power outlets, so this year at least Ivanovic will bring one multi-outlet power strip plus some extension cable (5m or so). There is no wired network, everything wireless (and sometimes rather unstable!). Beside this you should bring laptops since there are no desktop machines available for hacking.

Short version:
AW1 - Room 115

== FOSDEM 2008 ==
We were already at FOSDEM 2008, here something as reference:

* [http://www.wesnoth.org/forum/viewtopic.php?p=283649#p283649 Forum topic (with group photo)]
* [http://www.wesnoth.org/wiki/Fosdem2008 2008 wiki page]
* [https://mail.gna.org/public/wesnoth-dev/2008-02/msg00078.html Summary of FOSDEM 2008 results]

[[Category:Development]]
[[Category:Wesconf]]

FrenchTranslation

2008-10-17T22:26:22Z

Noyga:

Battle for Wesnoth - Traduction française
== Le mot d'introduction ==

Cette page sert à mieux coordonner l'effort de tous et à donner les informations souvent demandées avant de se lancer dans la traduction française.

== Règles de traduction ==
=== Respect des termes de l'univers de Wesnoth ===
Pour améliorer la cohérence de l'ensemble des traductions, utilisez :
# le [http://units.wesnoth.org/1.4/fr_FR/mainline.html dictionnaire des unités], qui vous permet de voir les noms par langues, par races, et par campagnes ;
# le [[NomsCommuns | wiki des noms communs]] ;
# le [[NomsPropres | wiki des noms propres]] ;
# des [http://elsap1.unicaen.fr/cgi-bin/cherches.cgi synonymes] pour enrichir vos phrases.

=== Respect du contexte ===
Il est important de correctement traduire les différents textes. Il ne suffit pas de traduire mot à mot les différentes phrases, il faut aussi faire très attention au contexte.

=== Respect des règles de typographie ===

==== Titres ====
Les titres des campagnes, des scénarios et des chapitres doivent suivre les règles de la langue française. Ces règles se trouvent sur http://fr.wikipedia.org/wiki/Wikipédia:Conventions_typographiques.

==== Ponctuation ====
Les traductions doivent aussi suivre les règles de ponctuation de la langue française, essentielles à un bon affichage du texte ; par exemple, l'utilisation d'une espace fine avant le signe « : » évitera que ce signe ne se trouve en début de ligne d'un texte. Ces règles se trouvent sur http://www.reveenjoie-poesie.com/outils-linguistiques/Typographie_francaise.html.

Il est préférable de ne pas mettre de virgule ni avant le « et », ni avant le « ou » (contrairement à l'anglais).

Remarque :
- sous Windows, la combinaison Alt+(0160) permet d'écrire une espace fine (les parenthèses indiquent qu'il faut maintenir la touche Alt appuyée).
Voici d'autres raccourcis : http://www.crdp-montpellier.fr/cd48/tice/trucs/majuscules.htm#win
- sous linux cette même combinaison est Alt+espace

==== Majuscules ====
Les majuscules doivent être accentuées dans les textes traduits : À, Â, Æ, Ç, É, Ê, È, Î, Ô, Œ, Ù, Û...

Voici également quelques rappels sur des confusions fréquentes :
# pas de majuscules aux noms des races (« nains », « elfes », « orcs », etc.) ;
# majuscules aux noms de clans ou de factions (les humains de « l'Ordre de la Serre Pourpre ») ;
# majuscules aux points cardinaux quand on parle d'une partie d'un tout (« les forêts de l'Ouest » peuvent se trouver à l'est), et minuscule quand on parle de la direction (« aller vers le nord »).

=== Respect des règles de l'orthographe ===
Il est préférable de soigner sa grammaire et son orthographe :
# le CNRS et l'ATILF fournissent un dictionnaire en ligne performant et complet : http://atilf.atilf.fr/
# et vous pourrez vérifier la conjugaison de vos verbes ici : http://www.conjugue-moi.com/.

Les [http://www.academie-francaise.fr/langue/orthographe/regles.html rectifications de l'orthographe préconisées par l'Académie Française] peuvent s'appliquer.

== Principes de traduction pour Wesnoth ==
Le principe est de mettre à jour les fichiers .po, fichiers servant à gérer les traductions dans Wesnoth. Les échanges se font via la mailing list.

=== S'inscrire à la mailing list ===
La mailing list francophone de Wesnoth est l'outil privilégié pour
# d'abord avertir les traducteurs que vous allez commencer une traduction (et éviter de travailler sur le même fichier),
# envoyer ses traductions pour validation ou relecture,
# poser des questions.

Pour s'inscrire à la mailing list, envoyez un mail vide ayant comme sujet « subscribe » (il sera traité par un robot) ; ou cliquez directement ici mailto:wesnoth-request@ml.free.fr?subject=subscribe et envoyez...

Les responsables des différentes mailing list sont ici : [[WesnothTranslations]].

Les archives de la mailing list sont ici : http://news.gmane.org/gmane.games.wesnoth-fr ; vous pouvez vous abonner au serveur de news news.gmane.org (gmane.games.wesnoth-fr).

Il est également possible de discuter sur le canal IRC #wesnothfr (sur irc.freenode.net) ou sur le forum, mais l'équipe de traduction française ne s'y promène que rarement.

=== Récupérer les fichiers .po nécessaires ===
Les fichiers à traduire sont accessibles :
# soit par cette page : http://gettext.wesnoth.org/ (le plus simple),
# soit par le SVN (plus compliqué) : http://svn.gna.org/viewcvs/wesnoth/ (mainline) et http://svn.berlios.de/wsvn/wescamp-i18n (user campaigns).

=== Modifier les fichiers .po et vérifier le statut des lignes traduites ===
Plusieurs logiciels permettent de modifier ces fichiers :
# les éditeurs de texte
#* [http://notepad-plus.sourceforge.net/fr/site.htm notepad++] ;
#* [http://www.textpad.com/ textpad] ;
#* ou, pour Mac, [http://www.barebones.com/products/textwrangler/index.shtml Textwrangler] ;
#* et puis bien d'autres encore...
# ou des éditeurs spécifiques aux fichiers .po
#* [http://www.poedit.net/ poEdit], pour Mac et PC ;
#* [http://i18n.kde.org/tools/kbabel/ KBabel] ;
#* [http://gtranslator.sourceforge.net/ gtranslator].

Chaque champ de traduction possède un statut :
# si vous traduisez pour la première fois un champ, mettez-le en traduction approximative ("fuzzy" en anglais), et ce même si c'est une traduction très basique ; toute traduction doit être relue au moins une fois avant d'être approuvée ;
# si vous relisez un champ, libre à vous de décider de son statut après votre relecture ;
#* sortez-le de son état approximatif si vous le considérez incontestablement bien traduit ;
#* laissez-le à l'état approximatif et demandez une deuxième relecture si vous n'êtes pas sûr de la traduction.

=== Tester sa traduction ===
Si vous le désirez, vous pouvez immédiatement tester votre traduction :
# enlevez l'option fuzzy de la ligne (ou des lignes) que vous voulez vérifier ;
# générez un fichier compilé « .mo » à partir du fichier texte « .po » ;
#*En ligne de commande : la commande « msgfmt » peut être utilisée avec le nom du fichier « .po » (exemple : « msgfmt mon_fichier.po -o mon_fichier.mo » générera « mon_fichier.mo »).
#*Avec l'éditeur « poedit » : « Fichier -> Préférence », onglet « Editeur, cochez la case « Compiler automatiquement les fichiers .mo lors de la sauvegarde » ; sauvez le fichier.
# copiez votre fichier dans le répertoire contenant les traductions et renommez-le ;
#*Sous Windows, <Répertoire d'installation de Wesnoth>\fr\LC_MESSAGES\<Nom du fichier à tester> (Exemple : C:\Wesnoth\po\fr\LC_MESSAGES\wesnoth-utbs.mo) ;
#*Sous Linux, répertoire en fonction de la distribution (Exemple Mandriva : /usr/share/locale/fr/LC_MESSAGES).
# jouez.... jusqu'au moment où le texte traduit est censé apparaître ; il n'est pas nécessaire de tout reprendre depuis le début, une sauvegarde fonctionne. Un texte traduit sans erreur apparaît... traduit.

Remarque : pour accélérer les tests, vous pouvez utiliser le mode debug de Wesnoth :
#Pour passer en mode débug :
#*taper : (pour ouvrir le mode de commande), puis : debug<entrée>
#*ou taper "wesnoth.exe --debug",
#*ou taper "wesnoth.exe -d"
# pour utiliser le mode débug :
#*":debug" entre en mode debug
#*":n" termine le scénario immédiatement

=== Envoyer sa traduction ===
Une traduction terminée est compressée, puis envoyée à la ML.

Il est préférable, en cas de relecture, de signaler les modifications dans le corps du mail, par exemple en faisant comme ci-dessous :
#Exemple 1 (refonte d'une phrase) : N° ligne Anciene version => Nouvelle version.
#Exemple 2 (correction d'une faute, indiquée par des *) : N°Ligne Ancien*n*e version

Il est également possible de générer un fichier différentiel entre l'ancienne et la nouvelle version ; mais l'expérience semble montrer que cela est peu relu.
Cette techique est surtout à utiliser qu'en cas de modifications massives (cas où le suivi ligne à ligne serait complexe et lourd).

=== Attention ===
* Les variables sont indiquées par ''$'' ; il ne faut pas les traduire : par exemple, ''$gold_left'' se traduit par ''$gold_left'' et non pas par ''$or_restant''.

* Il y a un bug récurent dans les fichiers po : lorsque la phrase traduite '''commence''' par ''$'', rien ne s'affiche dans le jeu. Pour corriger le problème, il suffit de mettre un simple espace devant le signe.

* ''\n'' dans la chaîne originale permet de créer un saut de ligne. Il faut le traduire en mettant ''\n'' en français (c'est important : ''gettext'' bugge s'il n'y a pas le même nombre de ''\n'' des deux côtés).

== Aujourd'hui, qui fait quoi ? ==
Ce chapitre vous permet de savoir qui fait quoi...

Date de dernière mise à jour : 18/10/2008
* Traductions
** The_Life_Of_A_Mage : Aurélien
** Wiki : Adrien (Cernunnos)
* Relectures / À relire

[[Category:Translations]]

FrenchTranslation

2008-10-17T22:25:50Z

Noyga: /* Aujourd'hui, qui fait quoi ? */

Battle for Wesnoth - Traduction française
== Le mot d'introduction ==

Cette page sert à mieux coordonner l'effort de tous et à donner les informations souvent demandées avant de se lancer dans la traduction française.

== Règles de traduction ==
=== Respect des termes de l'univers de Wesnoth ===
Pour améliorer la cohérence de l'ensemble des traductions, utilisez :
# le [http://units.wesnoth.org/1.4/fr_FR/mainline.html dictionnaire des unités], qui vous permet de voir les noms par langues, par races, et par campagnes ;
# le [[NomsCommuns | wiki des noms communs]] ;
# le [[NomsPropres | wiki des noms propres]] ;
# des [http://elsap1.unicaen.fr/cgi-bin/cherches.cgi synonymes] pour enrichir vos phrases.

=== Respect du contexte ===
Il est important de correctement traduire les différents textes. Il ne suffit pas de traduire mot à mot les différentes phrases, il faut aussi faire très attention au contexte.

=== Respect des règles de typographie ===

==== Titres ====
Les titres des campagnes, des scénarios et des chapitres doivent suivre les règles de la langue française. Ces règles se trouvent sur http://fr.wikipedia.org/wiki/Wikipédia:Conventions_typographiques.

==== Ponctuation ====
Les traductions doivent aussi suivre les règles de ponctuation de la langue française, essentielles à un bon affichage du texte ; par exemple, l'utilisation d'une espace fine avant le signe « : » évitera que ce signe ne se trouve en début de ligne d'un texte. Ces règles se trouvent sur http://www.reveenjoie-poesie.com/outils-linguistiques/Typographie_francaise.html.

Il est préférable de ne pas mettre de virgule ni avant le « et », ni avant le « ou » (contrairement à l'anglais).

Remarque :
- sous Windows, la combinaison Alt+(0160) permet d'écrire une espace fine (les parenthèses indiquent qu'il faut maintenir la touche Alt appuyée).
Voici d'autres raccourcis : http://www.crdp-montpellier.fr/cd48/tice/trucs/majuscules.htm#win
- sous linux cette même combinaison est Alt+espace

==== Majuscules ====
Les majuscules doivent être accentuées dans les textes traduits : À, Â, Æ, Ç, É, Ê, È, Î, Ô, Œ, Ù, Û...

Voici également quelques rappels sur des confusions fréquentes :
# pas de majuscules aux noms des races (« nains », « elfes », « orcs », etc.) ;
# majuscules aux noms de clans ou de factions (les humains de « l'Ordre de la Serre Pourpre ») ;
# majuscules aux points cardinaux quand on parle d'une partie d'un tout (« les forêts de l'Ouest » peuvent se trouver à l'est), et minuscule quand on parle de la direction (« aller vers le nord »).

=== Respect des règles de l'orthographe ===
Il est préférable de soigner sa grammaire et son orthographe :
# le CNRS et l'ATILF fournissent un dictionnaire en ligne performant et complet : http://atilf.atilf.fr/
# et vous pourrez vérifier la conjugaison de vos verbes ici : http://www.conjugue-moi.com/.

Les [http://www.academie-francaise.fr/langue/orthographe/regles.html rectifications de l'orthographe préconisées par l'Académie Française] peuvent s'appliquer.

== Principes de traduction pour Wesnoth ==
Le principe est de mettre à jour les fichiers .po, fichiers servant à gérer les traductions dans Wesnoth. Les échanges se font via la mailing list.

=== S'inscrire à la mailing list ===
La mailing list francophone de Wesnoth est l'outil privilégié pour
# d'abord avertir les traducteurs que vous allez commencer une traduction (et éviter de travailler sur le même fichier),
# envoyer ses traductions pour validation ou relecture,
# poser des questions.

Pour s'inscrire à la mailing list, envoyez un mail vide ayant comme sujet « subscribe » (il sera traité par un robot) ; ou cliquez directement ici mailto:wesnoth-request@ml.free.fr?subject=subscribe et envoyez...

Les responsables des différentes mailing list sont ici : [[WesnothTranslations]].

Les archives de la mailing list sont ici : http://news.gmane.org/gmane.games.wesnoth-fr ; vous pouvez vous abonner au serveur de news news.gmane.org (gmane.games.wesnoth-fr).

Il est également possible de discuter sur le canal IRC #wesnothfr (sur irc.freenode.net) ou sur le forum, mais l'équipe de traduction française ne s'y promène que rarement.

=== Récupérer les fichiers .po nécessaires ===
Les fichiers à traduire sont accessibles :
# soit par cette page : http://gettext.wesnoth.org/ (le plus simple),
# soit par le SVN (plus compliqué) : http://svn.gna.org/viewcvs/wesnoth/ (mainline) et http://svn.berlios.de/wsvn/wescamp-i18n (user campaigns).

=== Modifier les fichiers .po et vérifier le statut des lignes traduites ===
Plusieurs logiciels permettent de modifier ces fichiers :
# les éditeurs de texte
#* [http://notepad-plus.sourceforge.net/fr/site.htm notepad++] ;
#* [http://www.textpad.com/ textpad] ;
#* ou, pour Mac, [http://www.barebones.com/products/textwrangler/index.shtml Textwrangler] ;
#* et puis bien d'autres encore...
# ou des éditeurs spécifiques aux fichiers .po
#* [http://www.poedit.net/ poEdit], pour Mac et PC ;
#* [http://i18n.kde.org/tools/kbabel/ KBabel] ;
#* [http://gtranslator.sourceforge.net/ gtranslator].

Chaque champ de traduction possède un statut :
# si vous traduisez pour la première fois un champ, mettez-le en traduction approximative ("fuzzy" en anglais), et ce même si c'est une traduction très basique ; toute traduction doit être relue au moins une fois avant d'être approuvée ;
# si vous relisez un champ, libre à vous de décider de son statut après votre relecture ;
#* sortez-le de son état approximatif si vous le considérez incontestablement bien traduit ;
#* laissez-le à l'état approximatif et demandez une deuxième relecture si vous n'êtes pas sûr de la traduction.

=== Tester sa traduction ===
Si vous le désirez, vous pouvez immédiatement tester votre traduction :
# enlevez l'option fuzzy de la ligne (ou des lignes) que vous voulez vérifier ;
# générez un fichier compilé « .mo » à partir du fichier texte « .po » ;
#*En ligne de commande : la commande « msgfmt » peut être utilisée avec le nom du fichier « .po » (exemple : « msgfmt mon_fichier.po -o mon_fichier.mo » générera « mon_fichier.mo »).
#*Avec l'éditeur « poedit » : « Fichier -> Préférence », onglet « Editeur, cochez la case « Compiler automatiquement les fichiers .mo lors de la sauvegarde » ; sauvez le fichier.
# copiez votre fichier dans le répertoire contenant les traductions et renommez-le ;
#*Sous Windows, <Répertoire d'installation de Wesnoth>\fr\LC_MESSAGES\<Nom du fichier à tester> (Exemple : C:\Wesnoth\po\fr\LC_MESSAGES\wesnoth-utbs.mo) ;
#*Sous Linux, répertoire en fonction de la distribution (Exemple Mandriva : /usr/share/locale/fr/LC_MESSAGES).
# jouez.... jusqu'au moment où le texte traduit est censé apparaître ; il n'est pas nécessaire de tout reprendre depuis le début, une sauvegarde fonctionne. Un texte traduit sans erreur apparaît... traduit.

Remarque : pour accélérer les tests, vous pouvez utiliser le mode debug de Wesnoth :
#Pour passer en mode débug :
#*taper : (pour ouvrir le mode de commande), puis : debug<entrée>
#*ou taper "wesnoth.exe --debug",
#*ou taper "wesnoth.exe -d"
# pour utiliser le mode débug :
#*":debug" entre en mode debug
#*":n" termine le scénario immédiatement

=== Envoyer sa traduction ===
Une traduction terminée est compressée, puis envoyée à la ML.

Il est préférable, en cas de relecture, de signaler les modifications dans le corps du mail, par exemple en faisant comme ci-dessous :
#Exemple 1 (refonte d'une phrase) : N° ligne Anciene version => Nouvelle version.
#Exemple 2 (correction d'une faute, indiquée par des *) : N°Ligne Ancien*n*e version

Il est également possible de générer un fichier différentiel entre l'ancienne et la nouvelle version ; mais l'expérience semble montrer que cela est peu relu.
Cette techique est surtout à utiliser qu'en cas de modifications massives (cas où le suivi ligne à ligne serait complexe et lourd).

=== Attention ===
* Les variables sont indiquées par ''$'' ; il ne faut pas les traduire : par exemple, ''$gold_left'' se traduit par ''$gold_left'' et non pas par ''$or_restant''.

* Il y a un bug récurent dans les fichiers po : lorsque la phrase traduite '''commence''' par ''$'', rien ne s'affiche dans le jeu. Pour corriger le problème, il suffit de mettre un simple espace devant le signe.

* ''\n'' dans la chaîne originale permet de créer un saut de ligne. Il faut le traduire en mettant ''\n'' en français (c'est important : ''gettext'' bugge s'il n'y a pas le même nombre de ''\n'' des deux côtés).

== Aujourd'hui, qui fait quoi ? ==
Ce chapitre vous permet de savoir qui fait quoi...

Date de dernière mise à jour : 07/09/2008
* Traductions
** The_Life_Of_A_Mage : Aurélien
** Wiki : Adrien (Cernunnos)
* Relectures / À relire

[[Category:Translations]]

FrenchTranslation

2008-10-17T20:42:07Z

Noyga: /* Récupérer les fichiers .po nécessaires */

Battle for Wesnoth - Traduction française
== Le mot d'introduction ==

Cette page sert à mieux coordonner l'effort de tous et à donner les informations souvent demandées avant de se lancer dans la traduction française.

== Règles de traduction ==
=== Respect des termes de l'univers de Wesnoth ===
Pour améliorer la cohérence de l'ensemble des traductions, utilisez :
# le [http://units.wesnoth.org/1.4/fr_FR/mainline.html dictionnaire des unités], qui vous permet de voir les noms par langues, par races, et par campagnes ;
# le [[NomsCommuns | wiki des noms communs]] ;
# le [[NomsPropres | wiki des noms propres]] ;
# des [http://elsap1.unicaen.fr/cgi-bin/cherches.cgi synonymes] pour enrichir vos phrases.

=== Respect du contexte ===
Il est important de correctement traduire les différents textes. Il ne suffit pas de traduire mot à mot les différentes phrases, il faut aussi faire très attention au contexte.

=== Respect des règles de typographie ===

==== Titres ====
Les titres des campagnes, des scénarios et des chapitres doivent suivre les règles de la langue française. Ces règles se trouvent sur http://fr.wikipedia.org/wiki/Wikipédia:Conventions_typographiques.

==== Ponctuation ====
Les traductions doivent aussi suivre les règles de ponctuation de la langue française, essentielles à un bon affichage du texte ; par exemple, l'utilisation d'une espace fine avant le signe « : » évitera que ce signe ne se trouve en début de ligne d'un texte. Ces règles se trouvent sur http://www.reveenjoie-poesie.com/outils-linguistiques/Typographie_francaise.html.

Il est préférable de ne pas mettre de virgule ni avant le « et », ni avant le « ou » (contrairement à l'anglais).

Remarque :
- sous Windows, la combinaison Alt+(0160) permet d'écrire une espace fine (les parenthèses indiquent qu'il faut maintenir la touche Alt appuyée).
Voici d'autres raccourcis : http://www.crdp-montpellier.fr/cd48/tice/trucs/majuscules.htm#win
- sous linux cette même combinaison est Alt+espace

==== Majuscules ====
Les majuscules doivent être accentuées dans les textes traduits : À, Â, Æ, Ç, É, Ê, È, Î, Ô, Œ, Ù, Û...

Voici également quelques rappels sur des confusions fréquentes :
# pas de majuscules aux noms des races (« nains », « elfes », « orcs », etc.) ;
# majuscules aux noms de clans ou de factions (les humains de « l'Ordre de la Serre Pourpre ») ;
# majuscules aux points cardinaux quand on parle d'une partie d'un tout (« les forêts de l'Ouest » peuvent se trouver à l'est), et minuscule quand on parle de la direction (« aller vers le nord »).

=== Respect des règles de l'orthographe ===
Il est préférable de soigner sa grammaire et son orthographe :
# le CNRS et l'ATILF fournissent un dictionnaire en ligne performant et complet : http://atilf.atilf.fr/
# et vous pourrez vérifier la conjugaison de vos verbes ici : http://www.conjugue-moi.com/.

Les [http://www.academie-francaise.fr/langue/orthographe/regles.html rectifications de l'orthographe préconisées par l'Académie Française] peuvent s'appliquer.

== Principes de traduction pour Wesnoth ==
Le principe est de mettre à jour les fichiers .po, fichiers servant à gérer les traductions dans Wesnoth. Les échanges se font via la mailing list.

=== S'inscrire à la mailing list ===
La mailing list francophone de Wesnoth est l'outil privilégié pour
# d'abord avertir les traducteurs que vous allez commencer une traduction (et éviter de travailler sur le même fichier),
# envoyer ses traductions pour validation ou relecture,
# poser des questions.

Pour s'inscrire à la mailing list, envoyez un mail vide ayant comme sujet « subscribe » (il sera traité par un robot) ; ou cliquez directement ici mailto:wesnoth-request@ml.free.fr?subject=subscribe et envoyez...

Les responsables des différentes mailing list sont ici : [[WesnothTranslations]].

Les archives de la mailing list sont ici : http://news.gmane.org/gmane.games.wesnoth-fr ; vous pouvez vous abonner au serveur de news news.gmane.org (gmane.games.wesnoth-fr).

Il est également possible de discuter sur le canal IRC #wesnothfr (sur irc.freenode.net) ou sur le forum, mais l'équipe de traduction française ne s'y promène que rarement.

=== Récupérer les fichiers .po nécessaires ===
Les fichiers à traduire sont accessibles :
# soit par cette page : http://gettext.wesnoth.org/ (le plus simple),
# soit par le SVN (plus compliqué) : http://svn.gna.org/viewcvs/wesnoth/ (mainline) et http://svn.berlios.de/wsvn/wescamp-i18n (user campaigns).

=== Modifier les fichiers .po et vérifier le statut des lignes traduites ===
Plusieurs logiciels permettent de modifier ces fichiers :
# les éditeurs de texte
#* [http://notepad-plus.sourceforge.net/fr/site.htm notepad++] ;
#* [http://www.textpad.com/ textpad] ;
#* ou, pour Mac, [http://www.barebones.com/products/textwrangler/index.shtml Textwrangler] ;
#* et puis bien d'autres encore...
# ou des éditeurs spécifiques aux fichiers .po
#* [http://www.poedit.net/ poEdit], pour Mac et PC ;
#* [http://i18n.kde.org/tools/kbabel/ KBabel] ;
#* [http://gtranslator.sourceforge.net/ gtranslator].

Chaque champ de traduction possède un statut :
# si vous traduisez pour la première fois un champ, mettez-le en traduction approximative ("fuzzy" en anglais), et ce même si c'est une traduction très basique ; toute traduction doit être relue au moins une fois avant d'être approuvée ;
# si vous relisez un champ, libre à vous de décider de son statut après votre relecture ;
#* sortez-le de son état approximatif si vous le considérez incontestablement bien traduit ;
#* laissez-le à l'état approximatif et demandez une deuxième relecture si vous n'êtes pas sûr de la traduction.

=== Tester sa traduction ===
Si vous le désirez, vous pouvez immédiatement tester votre traduction :
# enlevez l'option fuzzy de la ligne (ou des lignes) que vous voulez vérifier ;
# générez un fichier compilé « .mo » à partir du fichier texte « .po » ;
#*En ligne de commande : la commande « msgfmt » peut être utilisée avec le nom du fichier « .po » (exemple : « msgfmt mon_fichier.po -o mon_fichier.mo » générera « mon_fichier.mo »).
#*Avec l'éditeur « poedit » : « Fichier -> Préférence », onglet « Editeur, cochez la case « Compiler automatiquement les fichiers .mo lors de la sauvegarde » ; sauvez le fichier.
# copiez votre fichier dans le répertoire contenant les traductions et renommez-le ;
#*Sous Windows, <Répertoire d'installation de Wesnoth>\fr\LC_MESSAGES\<Nom du fichier à tester> (Exemple : C:\Wesnoth\po\fr\LC_MESSAGES\wesnoth-utbs.mo) ;
#*Sous Linux, répertoire en fonction de la distribution (Exemple Mandriva : /usr/share/locale/fr/LC_MESSAGES).
# jouez.... jusqu'au moment où le texte traduit est censé apparaître ; il n'est pas nécessaire de tout reprendre depuis le début, une sauvegarde fonctionne. Un texte traduit sans erreur apparaît... traduit.

Remarque : pour accélérer les tests, vous pouvez utiliser le mode debug de Wesnoth :
#Pour passer en mode débug :
#*taper : (pour ouvrir le mode de commande), puis : debug<entrée>
#*ou taper "wesnoth.exe --debug",
#*ou taper "wesnoth.exe -d"
# pour utiliser le mode débug :
#*":debug" entre en mode debug
#*":n" termine le scénario immédiatement

=== Envoyer sa traduction ===
Une traduction terminée est compressée, puis envoyée à la ML.

Il est préférable, en cas de relecture, de signaler les modifications dans le corps du mail, par exemple en faisant comme ci-dessous :
#Exemple 1 (refonte d'une phrase) : N° ligne Anciene version => Nouvelle version.
#Exemple 2 (correction d'une faute, indiquée par des *) : N°Ligne Ancien*n*e version

Il est également possible de générer un fichier différentiel entre l'ancienne et la nouvelle version ; mais l'expérience semble montrer que cela est peu relu.
Cette techique est surtout à utiliser qu'en cas de modifications massives (cas où le suivi ligne à ligne serait complexe et lourd).

=== Attention ===
* Les variables sont indiquées par ''$'' ; il ne faut pas les traduire : par exemple, ''$gold_left'' se traduit par ''$gold_left'' et non pas par ''$or_restant''.

* Il y a un bug récurent dans les fichiers po : lorsque la phrase traduite '''commence''' par ''$'', rien ne s'affiche dans le jeu. Pour corriger le problème, il suffit de mettre un simple espace devant le signe.

* ''\n'' dans la chaîne originale permet de créer un saut de ligne. Il faut le traduire en mettant ''\n'' en français (c'est important : ''gettext'' bugge s'il n'y a pas le même nombre de ''\n'' des deux côtés).

== Aujourd'hui, qui fait quoi ? ==
Ce chapitre vous permet de savoir qui fait quoi...

Date de dernière mise à jour : 07/09/2008
* Traductions
** The_Life_Of_A_Mage : Aurélien
** ANL (version dev) : Benoît (Noyga)
** Wiki : Adrien (Cernunnos)
* Relectures / À relire

[[Category:Translations]]

FrenchTranslation

2008-09-07T14:30:15Z

Noyga: /* Aujourd'hui, qui fait quoi ? */

Battle for Wesnoth - Traduction française
== Le mot d'introduction ==

Cette page sert à mieux coordonner l'effort de tous et à donner les informations souvent demandées avant de se lancer dans la traduction française.

== Règles de traduction ==
=== Respect des termes de l'univers de Wesnoth ===
Pour améliorer la cohérence de l'ensemble des traductions, utilisez :
# le [http://units.wesnoth.org/1.4/fr_FR/mainline.html dictionnaire des unités], qui vous permet de voir les noms par langues, par races, et par campagnes ;
# le [[NomsCommuns | wiki des noms communs]] ;
# le [[NomsPropres | wiki des noms propres]] ;
# des [http://elsap1.unicaen.fr/cgi-bin/cherches.cgi synonymes] pour enrichir vos phrases.

=== Respect du contexte ===
Il est important de correctement traduire les différents textes. Il ne suffit pas de traduire mot à mot les différentes phrases, il faut aussi faire très attention au contexte.

=== Respect des règles de typographie ===

==== Titres ====
Les titres des campagnes, des scénarios et des chapitres doivent suivre les règles de la langue française. Ces règles se trouvent sur http://fr.wikipedia.org/wiki/Wikipédia:Conventions_typographiques.

==== Ponctuation ====
Les traductions doivent aussi suivre les règles de ponctuation de la langue française, essentielles à un bon affichage du texte ; par exemple, l'utilisation d'une espace fine avant le signe « : » évitera que ce signe ne se trouve en début de ligne d'un texte. Ces règles se trouvent sur http://www.reveenjoie-poesie.com/outils-linguistiques/Typographie_francaise.html.

Il est préférable de ne pas mettre de virgule ni avant le « et », ni avant le « ou » (contrairement à l'anglais).

Remarque :
- sous Windows, la combinaison Alt+(0160) permet d'écrire une espace fine (les parenthèses indiquent qu'il faut maintenir la touche Alt appuyée).
Voici d'autres raccourcis : http://www.crdp-montpellier.fr/cd48/tice/trucs/majuscules.htm#win
- sous linux cette même combinaison est Alt+espace

==== Majuscules ====
Les majuscules doivent être accentuées dans les textes traduits : À, Â, Æ, Ç, É, Ê, È, Î, Ô, Œ, Ù, Û...

Voici également quelques rappels sur des confusions fréquentes :
# pas de majuscules aux noms des races (« nains », « elfes », « orcs », etc.) ;
# majuscules aux noms de clans ou de factions (les humains de « l'Ordre de la Serre Pourpre ») ;
# majuscules aux points cardinaux quand on parle d'une partie d'un tout (« les forêts de l'Ouest » peuvent se trouver à l'est), et minuscule quand on parle de la direction (« aller vers le nord »).

=== Respect des règles de l'orthographe ===
Il est préférable de soigner sa grammaire et son orthographe :
# le CNRS et l'ATILF fournissent un dictionnaire en ligne performant et complet : http://atilf.atilf.fr/
# et vous pourrez vérifier la conjugaison de vos verbes ici : http://www.conjugue-moi.com/.

Les [http://www.academie-francaise.fr/langue/orthographe/regles.html rectifications de l'orthographe préconisées par l'Académie Française] peuvent s'appliquer.

== Principes de traduction pour Wesnoth ==
Le principe est de mettre à jour les fichiers .po, fichiers servant à gérer les traductions dans Wesnoth. Les échanges se font via la mailing list.

=== S'inscrire à la mailing list ===
La mailing list francophone de Wesnoth est l'outil privilégié pour
# d'abord avertir les traducteurs que vous allez commencer une traduction (et éviter de travailler sur le même fichier),
# envoyer ses traductions pour validation ou relecture,
# poser des questions.

Pour s'inscrire à la mailing list, envoyez un mail vide ayant comme sujet « subscribe » (il sera traité par un robot) ; ou cliquez directement ici mailto:wesnoth-request@ml.free.fr?subject=subscribe et envoyez...

Les responsables des différentes mailing list sont ici : [[WesnothTranslations]].

Les archives de la mailing list sont ici : http://news.gmane.org/gmane.games.wesnoth-fr ; vous pouvez vous abonner au serveur de news news.gmane.org (gmane.games.wesnoth-fr).

Il est également possible de discuter sur le canal IRC #wesnothfr (sur irc.freenode.net) ou sur le forum, mais l'équipe de traduction française ne s'y promène que rarement.

=== Récupérer les fichiers .po nécessaires ===
Les fichiers à traduire sont accessibles :
# soit par cette page : http://gettext.wesnoth.org/ (le plus simple),
# soit par le CVS : http://savannah.nongnu.org/cvs/?group=wesnoth (si on aime CVS).

=== Modifier les fichiers .po et vérifier le statut des lignes traduites ===
Plusieurs logiciels permettent de modifier ces fichiers :
# les éditeurs de texte
#* [http://notepad-plus.sourceforge.net/fr/site.htm notepad++] ;
#* [http://www.textpad.com/ textpad] ;
#* ou, pour Mac, [http://www.barebones.com/products/textwrangler/index.shtml Textwrangler] ;
#* et puis bien d'autres encore...
# ou des éditeurs spécifiques aux fichiers .po
#* [http://www.poedit.net/ poEdit], pour Mac et PC ;
#* [http://i18n.kde.org/tools/kbabel/ KBabel] ;
#* [http://gtranslator.sourceforge.net/ gtranslator].

Chaque champ de traduction possède un statut :
# si vous traduisez pour la première fois un champ, mettez-le en traduction approximative ("fuzzy" en anglais), et ce même si c'est une traduction très basique ; toute traduction doit être relue au moins une fois avant d'être approuvée ;
# si vous relisez un champ, libre à vous de décider de son statut après votre relecture ;
#* sortez-le de son état approximatif si vous le considérez incontestablement bien traduit ;
#* laissez-le à l'état approximatif et demandez une deuxième relecture si vous n'êtes pas sûr de la traduction.

=== Tester sa traduction ===
Si vous le désirez, vous pouvez immédiatement tester votre traduction :
# enlevez l'option fuzzy de la ligne (ou des lignes) que vous voulez vérifier ;
# générez un fichier compilé « .mo » à partir du fichier texte « .po » ;
#*En ligne de commande : la commande « msgfmt » peut être utilisée avec le nom du fichier « .po » (exemple : « msgfmt mon_fichier.po -o mon_fichier.mo » générera « mon_fichier.mo »).
#*Avec l'éditeur « poedit » : « Fichier -> Préférence », onglet « Editeur, cochez la case « Compiler automatiquement les fichiers .mo lors de la sauvegarde » ; sauvez le fichier.
# copiez votre fichier dans le répertoire contenant les traductions et renommez-le ;
#*Sous Windows, <Répertoire d'installation de Wesnoth>\fr\LC_MESSAGES\<Nom du fichier à tester> (Exemple : C:\Wesnoth\po\fr\LC_MESSAGES\wesnoth-utbs.mo) ;
#*Sous Linux, répertoire en fonction de la distribution (Exemple Mandriva : /usr/share/locale/fr/LC_MESSAGES).
# jouez.... jusqu'au moment où le texte traduit est censé apparaître ; il n'est pas nécessaire de tout reprendre depuis le début, une sauvegarde fonctionne. Un texte traduit sans erreur apparaît... traduit.

Remarque : pour accélérer les tests, vous pouvez utiliser le mode debug de Wesnoth :
#Pour passer en mode débug :
#*taper : (pour ouvrir le mode de commande), puis : debug<entrée>
#*ou taper "wesnoth.exe --debug",
#*ou taper "wesnoth.exe -d"
# pour utiliser le mode débug :
#*":debug" entre en mode debug
#*":n" termine le scénario immédiatement

=== Envoyer sa traduction ===
Une traduction terminée est compressée, puis envoyée à la ML.

Il est préférable, en cas de relecture, de signaler les modifications dans le corps du mail, par exemple en faisant comme ci-dessous :
#Exemple 1 (refonte d'une phrase) : N° ligne Anciene version => Nouvelle version.
#Exemple 2 (correction d'une faute, indiquée par des *) : N°Ligne Ancien*n*e version

Il est également possible de générer un fichier différentiel entre l'ancienne et la nouvelle version ; mais l'expérience semble montrer que cela est peu relu.
Cette techique est surtout à utiliser qu'en cas de modifications massives (cas où le suivi ligne à ligne serait complexe et lourd).

=== Attention ===
* Les variables sont indiquées par ''$'' ; il ne faut pas les traduire : par exemple, ''$gold_left'' se traduit par ''$gold_left'' et non pas par ''$or_restant''.

* Il y a un bug récurent dans les fichiers po : lorsque la phrase traduite '''commence''' par ''$'', rien ne s'affiche dans le jeu. Pour corriger le problème, il suffit de mettre un simple espace devant le signe.

* ''\n'' dans la chaîne originale permet de créer un saut de ligne. Il faut le traduire en mettant ''\n'' en français (c'est important : ''gettext'' bugge s'il n'y a pas le même nombre de ''\n'' des deux côtés).

== Aujourd'hui, qui fait quoi ? ==
Ce chapitre vous permet de savoir qui fait quoi...

Date de dernière mise à jour : 07/09/2008
* Traductions
** The_Life_Of_A_Mage : Aurélien
** ANL (version dev) : Benoît (Noyga)
** Wiki : Adrien (Cernunnos)
* Relectures / À relire

[[Category:Translations]]

FrenchTranslation

2008-08-09T21:22:35Z

Noyga:

Battle for Wesnoth - Traduction française
== Le mot d'introduction ==

Cette page sert à mieux coordonner l'effort de tous et à donner les informations souvent demandées avant de se lancer dans la traduction française.

== Règles de traduction ==
=== Respect des termes de l'univers de Wesnoth ===
Pour améliorer la cohérence de l'ensemble des traductions, utilisez :
# le [http://units.wesnoth.org/1.4/fr_FR/mainline.html dictionnaire des unités], qui vous permet de voir les noms par langues, par races, et par campagnes ;
# le [[NomsCommuns | wiki des noms communs]] ;
# le [[NomsPropres | wiki des noms propres]] ;
# des [http://elsap1.unicaen.fr/cgi-bin/cherches.cgi synonymes] pour enrichir vos phrases.

=== Respect du contexte ===
Il est important de correctement traduire les différents textes. Il ne suffit pas de traduire mot à mot les différentes phrases, il faut aussi faire très attention au contexte.

=== Respect des règles de typographie ===

==== Titres ====
Les titres des campagnes, des scénarios et des chapitres doivent suivre les règles de la langue française. Ces règles se trouvent sur http://fr.wikipedia.org/wiki/Wikipédia:Conventions_typographiques.

==== Ponctuation ====
Les traductions doivent aussi suivre les règles de ponctuation de la langue française, essentielles à un bon affichage du texte ; par exemple, l'utilisation d'une espace fine avant le signe « : » évitera que ce signe ne se trouve en début de ligne d'un texte. Ces règles se trouvent sur http://www.reveenjoie-poesie.com/outils-linguistiques/Typographie_francaise.html.

Il est préférable de ne pas mettre de virgule ni avant le « et », ni avant le « ou » (contrairement à l'anglais).

Remarque :
- sous Windows, la combinaison Alt+(0160) permet d'écrire une espace fine (les parenthèses indiquent qu'il faut maintenir la touche Alt appuyée).
Voici d'autres raccourcis : http://www.crdp-montpellier.fr/cd48/tice/trucs/majuscules.htm#win
- sous linux cette même combinaison est Alt+espace

==== Majuscules ====
Les majuscules doivent être accentuées dans les textes traduits : À, Â, Æ, Ç, É, Ê, È, Î, Ô, Œ, Ù, Û...

Voici également quelques rappels sur des confusions fréquentes :
# pas de majuscules aux noms des races (« nains », « elfes », « orcs », etc.) ;
# majuscules aux noms de clans ou de factions (les humains de « l'Ordre de la Serre Pourpre ») ;
# majuscules aux points cardinaux quand on parle d'une partie d'un tout (« les forêts de l'Ouest » peuvent se trouver à l'est), et minuscule quand on parle de la direction (« aller vers le nord »).

=== Respect des règles de l'orthographe ===
Il est préférable de soigner sa grammaire et son orthographe :
# le CNRS et l'ATILF fournissent un dictionnaire en ligne performant et complet : http://atilf.atilf.fr/
# et vous pourrez vérifier la conjugaison de vos verbes ici : http://www.conjugue-moi.com/.

Les [http://www.academie-francaise.fr/langue/orthographe/regles.html rectifications de l'orthographe préconisées par l'Académie Française] peuvent s'appliquer.

== Principes de traduction pour Wesnoth ==
Le principe est de mettre à jour les fichiers .po, fichiers servant à gérer les traductions dans Wesnoth. Les échanges se font via la mailing list.

=== S'inscrire à la mailing list ===
La mailing list francophone de Wesnoth est l'outil privilégié pour
# d'abord avertir les traducteurs que vous allez commencer une traduction (et éviter de travailler sur le même fichier),
# envoyer ses traductions pour validation ou relecture,
# poser des questions.

Pour s'inscrire à la mailing list, envoyez un mail vide ayant comme sujet « subscribe » (il sera traité par un robot) ; ou cliquez directement ici mailto:wesnoth-request@ml.free.fr?subject=subscribe et envoyez...

Les responsables des différentes mailing list sont ici : [[WesnothTranslations]].

Les archives de la mailing list sont ici : http://news.gmane.org/gmane.games.wesnoth-fr ; vous pouvez vous abonner au serveur de news news.gmane.org (gmane.games.wesnoth-fr).

Il est également possible de discuter sur le canal IRC #wesnothfr (sur irc.freenode.net) ou sur le forum, mais l'équipe de traduction française ne s'y promène que rarement.

=== Récupérer les fichiers .po nécessaires ===
Les fichiers à traduire sont accessibles :
# soit par cette page : http://gettext.wesnoth.org/ (le plus simple),
# soit par le CVS : http://savannah.nongnu.org/cvs/?group=wesnoth (si on aime CVS).

=== Modifier les fichiers .po et vérifier le statut des lignes traduites ===
Plusieurs logiciels permettent de modifier ces fichiers :
# les éditeurs de texte
#* [http://notepad-plus.sourceforge.net/fr/site.htm notepad++] ;
#* [http://www.textpad.com/ textpad] ;
#* ou, pour Mac, [http://www.barebones.com/products/textwrangler/index.shtml Textwrangler] ;
#* et puis bien d'autres encore...
# ou des éditeurs spécifiques aux fichiers .po
#* [http://www.poedit.net/ poEdit], pour Mac et PC ;
#* [http://i18n.kde.org/tools/kbabel/ KBabel] ;
#* [http://gtranslator.sourceforge.net/ gtranslator].

Chaque champ de traduction possède un statut :
# si vous traduisez pour la première fois un champ, mettez-le en traduction approximative ("fuzzy" en anglais), et ce même si c'est une traduction très basique ; toute traduction doit être relue au moins une fois avant d'être approuvée ;
# si vous relisez un champ, libre à vous de décider de son statut après votre relecture ;
#* sortez-le de son état approximatif si vous le considérez incontestablement bien traduit ;
#* laissez-le à l'état approximatif et demandez une deuxième relecture si vous n'êtes pas sûr de la traduction.

=== Tester sa traduction ===
Si vous le désirez, vous pouvez immédiatement tester votre traduction :
# enlevez l'option fuzzy de la ligne (ou des lignes) que vous voulez vérifier ;
# générez un fichier compilé « .mo » à partir du fichier texte « .po » ;
#*En ligne de commande : la commande « msgfmt » peut être utilisée avec le nom du fichier « .po » (exemple : « msgfmt mon_fichier.po -o mon_fichier.mo » générera « mon_fichier.mo »).
#*Avec l'éditeur « poedit » : « Fichier -> Préférence », onglet « Editeur, cochez la case « Compiler automatiquement les fichiers .mo lors de la sauvegarde » ; sauvez le fichier.
# copiez votre fichier dans le répertoire contenant les traductions et renommez-le ;
#*Sous Windows, <Répertoire d'installation de Wesnoth>\fr\LC_MESSAGES\<Nom du fichier à tester> (Exemple : C:\Wesnoth\po\fr\LC_MESSAGES\wesnoth-utbs.mo) ;
#*Sous Linux, répertoire en fonction de la distribution (Exemple Mandriva : /usr/share/locale/fr/LC_MESSAGES).
# jouez.... jusqu'au moment où le texte traduit est censé apparaître ; il n'est pas nécessaire de tout reprendre depuis le début, une sauvegarde fonctionne. Un texte traduit sans erreur apparaît... traduit.

Remarque : pour accélérer les tests, vous pouvez utiliser le mode debug de Wesnoth :
#Pour passer en mode débug :
#*taper : (pour ouvrir le mode de commande), puis : debug<entrée>
#*ou taper "wesnoth.exe --debug",
#*ou taper "wesnoth.exe -d"
# pour utiliser le mode débug :
#*":debug" entre en mode debug
#*":n" termine le scénario immédiatement

=== Envoyer sa traduction ===
Une traduction terminée est compressée, puis envoyée à la ML.

Il est préférable, en cas de relecture, de signaler les modifications dans le corps du mail, par exemple en faisant comme ci-dessous :
#Exemple 1 (refonte d'une phrase) : N° ligne Anciene version => Nouvelle version.
#Exemple 2 (correction d'une faute, indiquée par des *) : N°Ligne Ancien*n*e version

Il est également possible de générer un fichier différentiel entre l'ancienne et la nouvelle version ; mais l'expérience semble montrer que cela est peu relu.
Cette techique est surtout à utiliser qu'en cas de modifications massives (cas où le suivi ligne à ligne serait complexe et lourd).

=== Attention ===
* Les variables sont indiquées par ''$'' ; il ne faut pas les traduire : par exemple, ''$gold_left'' se traduit par ''$gold_left'' et non pas par ''$or_restant''.

* Il y a un bug récurent dans les fichiers po : lorsque la phrase traduite '''commence''' par ''$'', rien ne s'affiche dans le jeu. Pour corriger le problème, il suffit de mettre un simple espace devant le signe.

* ''\n'' dans la chaîne originale permet de créer un saut de ligne. Il faut le traduire en mettant ''\n'' en français (c'est important : ''gettext'' bugge s'il n'y a pas le même nombre de ''\n'' des deux côtés).

== Aujourd'hui, qui fait quoi ? ==
Ce chapitre vous permet de savoir qui fait quoi...

Date de dernière mise à jour : 09/08/2008
* Traductions
** The_Life_Of_A_Mage : Aurélien

* Relectures / À relire

[[Category:Translations]]

WesnothTranslations

2008-05-31T19:25:04Z

Noyga: /* Translations */

== Translations ==

Wesnoth is currently being translated into the following languages. Instructions on how to contribute are found here:
[[WesnothTranslationsHowTo]].
* [[AfrikaansTranslation|Afrikaans]] - maintainer: Friedel Wolff - [mailto:friedelATSIGNtranslateDOTorgDOTza]
* [[ArabicTranslation|Arabic]] - maintainer: Amnay Mokhtari - [mailto:amnayAToperamailDOTcom]
* [[BasqueTranslation|Basque]] - maintainer: Alfredo Beaumont (ziberpunk) - [mailto:alfredo.beaumontATgmailDOTcom]
* [[BulgarianTranslation|Bulgarian]] maintainer: Nikolay Vladimirov (Turki) - [mailto:nikolayATvladimiroffDOTcom]
* [[CatalanTranslation|Catalan]] - maintainer: Jordà Polo (ettin) - [mailto:jordaATettinDOTorg]
* [[ChineseTranslation|Chinese]] - maintainer: ???, Enter the Forum for information: [http://www.wesnoth.cn Wesnoth.CN]
* [[ChineseTaiwanTranslation|Chinese (Taiwan)]] - maintainer: ???
* [[CroatianTranslation|Croatian]] - maintainer: Nino Gunjača (nion) - [mailto:nino.gunjaca@zg.t-com.hr]
* [[CzechTranslation|Czech]] - maintainer: Vladimír Slávik - [mailto:slavikDOTvladimirATseznamDOTcz]
* [[DanishTranslation|Danish]] maintainer: Joe Hansen (joedalton) - [mailto:joedalton2ATyahooDOTdk]
* [[DutchTranslation|Dutch]] - maintainer: Foppe Benedictus (Fopper) - [mailto:foppeDOTbenedictusATgmailDOTcom]
* [[EnglishTranslation|English (US)]] ''(this is the default)'' - maintainer: Sirp - [mailto:davidnwhiteATcomcastDOTnet]
* [[EnglishGBTranslation|English (GB)]] - maintainer: pjr - [mailto:peadar.ruadh@btinternet.com]
* [[Esperanto_translation|Esperanto]] - maintainer: Viliam Bur - [mailto:viliamATburDOTsk]
* [[EstonianTranslation|Estonian]] - maintainer: Mart Tõnso (rinjin) - [mailto:tmATrinjinDOTpriDOTee]
* [[FilipinoTranslation|Filipino]] - maintainer: Karen Eso (keeve) - [mailto:eveUNDERSCOREesoATyahooDOTca]
* [[FinnishTranslation|Finnish]] - maintainer: Samu Voutilainen (Smar) - [mailto:ec5983ATkolumbusDOTfi]
* [[FrenchTranslation|French]] - maintainer: Benoît Timbert (Noyga) [mailto:benoitDOTtimbertATfreeDOTfr] - translation team mailing list [mailto:wesnothATmlDOTfreeDOTfr]
* [[FriulianTranslation|Friulian]] - maintainer: Michele Calligaris (MayBug) - [mailto:michele.calligaris-CAIUT-gmail.com]
* [[GalicianTranslation|Galician]] - maintainer: Leandro Regueiro - [mailto:leandroDOTregueiroATgmailDOTcom] [http://trasno.net Proxecto Trasno]
* [[GermanTranslation|German]] - maintainer: Christoph Berg (chrber) - [mailto:ChristophDOTBergATkpm-sportDOTde]
* [[GreekTranslation|Greek]] - maintainer: Konstantinos Egarhos [mailto:atixosATgmailDOTcom]
* [[HebrewTranslation|Hebrew]] - maintainer: Oron Peled - [mailto:oronATactcomDOTcoDOTil]
* [[HungarianTranslation|Hungarian]] - maintainer: Kádár-Németh Krisztián - [mailto:krisztian.kadATgmailDOTcom]; vice-maintainer: Németh Tamás [mailto:ntomaszATkabelnetDOThu]
* [[IndonesianTranslation|Indonesian]] - maintainer: Nicky Inkrais Witras [mailto:inkraiswitrasATyahooDOTcom]
* [[ItalianTranslation|Italian]] - maintainer: Luciano Montanaro - [mailto:mikelima@cirulla.net]
* [[JapaneseTranslation|Japanese]] - maintainer: Nobuhito Okada - [mailto:okyadaATgmailDOTcom]
* [[KoreanTranslation|Korean]] - maintainer: ???
* [[LatinTranslation|Latin]] - maintainer: Marc Polo ([http://www.wesnoth.org/forum/privmsg.php?mode=post&u=571 mpolo]) - No mail address specified
* [[LithuanianTranslation|Lithuanian]] - maintainer: Andrius Štikonas - [mailto:stikonasATgmailDOTcom]
* [[MacedonianTranslation|Macedonian]] - maintainer: Dimitar Ilccov (Mythological)
* [[NorwegianTranslation|Norwegian]] - maintainer: Gaute Jao (Gauteamus) - [mailto:gauteamusATgmailDOTcom]
* [[OccitanTranslation|Occitan]] - maintainer: Nobody, currently
* [[PolishTranslation|Polish]] - maintainer: Zbigniew Banach - [mailto:zDOTbanachATwsisizDOTeduDOTpl]
* [[PortugueseTranslation|Portuguese Brazilian]] - maintainer: Claus Aranha (caranha) - [mailto:caranhaATgmailDOTcom]
* [[PortugueseContinentalTranslation|Portuguese Continental(pt_PT)]] - maintainer: Sérgio Lopes [mailto:knitter.is@gmail.com]
* [[RomanianTranslation|Romanian]] - maintainer: ???
* [[RussianTranslation|Russian]] - maintainer: Victor Zabavin [mailto:viczaATzmailDOTru]
* [[SerbianTranslation|Serbian]] - maintainer: Srećko Toroman (freecraft)- [mailto:sreckotoromanATgmailDOTcom]
* [[(sk) Preklad|Slovak]] - maintainer: Viliam Bur - [mailto:viliamATburDOTsk]; wiki: [[(sk) Návod]]
* [[SlovenianTranslation|Slovenian]] - maintainer: Jaka Kranjc (lynx) - [mailto:lynxlupodianAThotmailDOTcom]
* [[SpanishTranslation|Spanish]] - maintainer: Sergi March [mailto:sergiPUNTOmarchENgmail.com]
* [[SwedishTranslation|Swedish]] - maintainer: Gustav Tiger (Tigge) - [mailto:adminATtiggeDOTorg]
* [[TurkishTranslation|Turkish]] - maintainer: Nilgün Belma Bugüner - [mailto:nilgunATbelgelerDOTgenDOTtr]
* [[Wesnoth-in-Valencian|Valencian]] - maintainer: Mario (Mavorte) - [mailto:mavorte1ATyahooDOTes]
* [[VietnameseTranslation|Vietnamese]] - maintainer: Do Hong Minh - [mailto:minhdhAThutticDOTcom]

Other ideas (remember, these are just ideas):
* Translations into Asian languages
** Asian languages are already supported. See [[WesnothAsianLanguages]].

== Mailing List ==

There now is a mailinglist dedicated to translation matters. It is mainly intended to be used for informing translation maintainers about important changes, to announce string freezes and other special things. Everyone is free to subscribe to this list. You can find this list, entitled wesnoth-i18n at the listing of all Wesnoth mailing lists:

[http://gna.org/mail/?group=wesnoth http://gna.org/mail/?group=wesnoth]

The archive for this list is to be found [http://mail.gna.org/public/wesnoth-i18n/ here].
Please keep in mind that this list is not meant for discussing changes for one single translation but stuff that is relevant to all translations.

== See also ==

* [[WesnothTranslationsHowTo]]
* [[GetText]]
* [http://gettext.wesnoth.org Translations statistics (stable)]
* [http://gettext.wesnoth.org/index.php?version=trunk&package=alloff Translations statistics (development)]
* [[WesCamp| Translating User made Campaigns (featuring WesCamp-i18n)]]
* [[SpellingMistakes]]

[[Category:Translations|*]]

WesnothTranslations

2008-05-31T19:17:21Z

Noyga: /* Translations */

== Translations ==

Wesnoth is currently being translated into the following languages. Instructions on how to contribute are found here:
[[WesnothTranslationsHowTo]].
* [[AfrikaansTranslation|Afrikaans]] - maintainer: Friedel Wolff - [mailto:friedelATSIGNtranslateDOTorgDOTza]
* [[ArabicTranslation|Arabic]] - maintainer: Amnay Mokhtari - [mailto:amnayAToperamailDOTcom]
* [[BasqueTranslation|Basque]] - maintainer: Alfredo Beaumont (ziberpunk) - [mailto:alfredo.beaumontATgmailDOTcom]
* [[BulgarianTranslation|Bulgarian]] maintainer: Nikolay Vladimirov (Turki) - [mailto:nikolayATvladimiroffDOTcom]
* [[CatalanTranslation|Catalan]] - maintainer: Jordà Polo (ettin) - [mailto:jordaATettinDOTorg]
* [[ChineseTranslation|Chinese]] - maintainer: ???, Enter the Forum for information: [http://www.wesnoth.cn Wesnoth.CN]
* [[ChineseTaiwanTranslation|Chinese (Taiwan)]] - maintainer: ???
* [[CroatianTranslation|Croatian]] - maintainer: Nino Gunjača (nion) - [mailto:nino.gunjaca@zg.t-com.hr]
* [[CzechTranslation|Czech]] - maintainer: Vladimír Slávik - [mailto:slavikDOTvladimirATseznamDOTcz]
* [[DanishTranslation|Danish]] maintainer: Joe Hansen (joedalton) - [mailto:joedalton2ATyahooDOTdk]
* [[DutchTranslation|Dutch]] - maintainer: Foppe Benedictus (Fopper) - [mailto:foppeDOTbenedictusATgmailDOTcom]
* [[EnglishTranslation|English (US)]] ''(this is the default)'' - maintainer: Sirp - [mailto:davidnwhiteATcomcastDOTnet]
* [[EnglishGBTranslation|English (GB)]] - maintainer: pjr - [mailto:peadar.ruadh@btinternet.com]
* [[Esperanto_translation|Esperanto]] - maintainer: Viliam Bur - [mailto:viliamATburDOTsk]
* [[EstonianTranslation|Estonian]] - maintainer: Mart Tõnso (rinjin) - [mailto:tmATrinjinDOTpriDOTee]
* [[FilipinoTranslation|Filipino]] - maintainer: Karen Eso (keeve) - [mailto:eveUNDERSCOREesoATyahooDOTca]
* [[FinnishTranslation|Finnish]] - maintainer: Samu Voutilainen (Smar) - [mailto:ec5983ATkolumbusDOTfi]
* [[FrenchTranslation|French]] - maintainer: Benoît Timbert (Noyga) [mailto:benoitDOTtimbertATfreeDOTfr] - translation team mailing list [mailto:wesnothATmlDOTfreeDOTfr]
* [[FriulianTranslation|Friulian]] - maintainer: ???
* [[GalicianTranslation|Galician]] - maintainer: Leandro Regueiro - [mailto:leandroDOTregueiroATgmailDOTcom] [http://trasno.net Proxecto Trasno]
* [[GermanTranslation|German]] - maintainer: Christoph Berg (chrber) - [mailto:ChristophDOTBergATkpm-sportDOTde]
* [[GreekTranslation|Greek]] - maintainer: Konstantinos Egarhos [mailto:atixosATgmailDOTcom]
* [[HebrewTranslation|Hebrew]] - maintainer: Oron Peled - [mailto:oronATactcomDOTcoDOTil]
* [[HungarianTranslation|Hungarian]] - maintainer: Kádár-Németh Krisztián - [mailto:krisztian.kadATgmailDOTcom]; vice-maintainer: Németh Tamás [mailto:ntomaszATkabelnetDOThu]
* [[IndonesianTranslation|Indonesian]] - maintainer: Nicky Inkrais Witras [mailto:inkraiswitrasATyahooDOTcom]
* [[ItalianTranslation|Italian]] - maintainer: Luciano Montanaro - [mailto:mikelima@cirulla.net]
* [[JapaneseTranslation|Japanese]] - maintainer: Nobuhito Okada - [mailto:okyadaATgmailDOTcom]
* [[KoreanTranslation|Korean]] - maintainer: ???
* [[LatinTranslation|Latin]] - maintainer: Marc Polo ([http://www.wesnoth.org/forum/privmsg.php?mode=post&u=571 mpolo]) - No mail address specified
* [[LithuanianTranslation|Lithuanian]] - maintainer: Andrius Štikonas - [mailto:stikonasATgmailDOTcom]
* [[MacedonianTranslation|Macedonian]] - maintainer: Dimitar Ilccov (Mythological)
* [[NorwegianTranslation|Norwegian]] - maintainer: Gaute Jao (Gauteamus) - [mailto:gauteamusATgmailDOTcom]
* [[OccitanTranslation|Occitan]] - maintainer: Nobody, currently
* [[PolishTranslation|Polish]] - maintainer: Zbigniew Banach - [mailto:zDOTbanachATwsisizDOTeduDOTpl]
* [[PortugueseTranslation|Portuguese Brazilian]] - maintainer: Claus Aranha (caranha) - [mailto:caranhaATgmailDOTcom]
* [[PortugueseContinentalTranslation|Portuguese Continental(pt_PT)]] - maintainer: Sérgio Lopes [mailto:knitter.is@gmail.com]
* [[RomanianTranslation|Romanian]] - maintainer: ???
* [[RussianTranslation|Russian]] - maintainer: Victor Zabavin [mailto:viczaATzmailDOTru]
* [[SerbianTranslation|Serbian]] - maintainer: Srećko Toroman (freecraft)- [mailto:sreckotoromanATgmailDOTcom]
* [[(sk) Preklad|Slovak]] - maintainer: Viliam Bur - [mailto:viliamATburDOTsk]; wiki: [[(sk) Návod]]
* [[SlovenianTranslation|Slovenian]] - maintainer: Jaka Kranjc (lynx) - [mailto:lynxlupodianAThotmailDOTcom]
* [[SpanishTranslation|Spanish]] - maintainer: Sergi March [mailto:sergiPUNTOmarchENgmail.com]
* [[SwedishTranslation|Swedish]] - maintainer: Gustav Tiger (Tigge) - [mailto:adminATtiggeDOTorg]
* [[TurkishTranslation|Turkish]] - maintainer: Nilgün Belma Bugüner - [mailto:nilgunATbelgelerDOTgenDOTtr]
* [[Wesnoth-in-Valencian|Valencian]] - maintainer: Mario (Mavorte) - [mailto:mavorte1ATyahooDOTes]
* [[VietnameseTranslation|Vietnamese]] - maintainer: Do Hong Minh - [mailto:minhdhAThutticDOTcom]

Other ideas (remember, these are just ideas):
* Translations into Asian languages
** Asian languages are already supported. See [[WesnothAsianLanguages]].

== Mailing List ==

There now is a mailinglist dedicated to translation matters. It is mainly intended to be used for informing translation maintainers about important changes, to announce string freezes and other special things. Everyone is free to subscribe to this list. You can find this list, entitled wesnoth-i18n at the listing of all Wesnoth mailing lists:

[http://gna.org/mail/?group=wesnoth http://gna.org/mail/?group=wesnoth]

The archive for this list is to be found [http://mail.gna.org/public/wesnoth-i18n/ here].
Please keep in mind that this list is not meant for discussing changes for one single translation but stuff that is relevant to all translations.

== See also ==

* [[WesnothTranslationsHowTo]]
* [[GetText]]
* [http://gettext.wesnoth.org Translations statistics (stable)]
* [http://gettext.wesnoth.org/index.php?version=trunk&package=alloff Translations statistics (development)]
* [[WesCamp| Translating User made Campaigns (featuring WesCamp-i18n)]]
* [[SpellingMistakes]]

[[Category:Translations|*]]

WesnothTranslations

2008-05-31T19:16:19Z

Noyga: /* Translations */

== Translations ==

Wesnoth is currently being translated into the following languages. Instructions on how to contribute are found here:
[[WesnothTranslationsHowTo]].
* [[AfrikaansTranslation|Afrikaans]] - maintainer: Friedel Wolff - [mailto:friedelATSIGNtranslateDOTorgDOTza]
* [[ArabicTranslation|Arabic]] - maintainer: Amnay Mokhtari - [mailto:amnayAToperamailDOTcom]
* [[BasqueTranslation|Basque]] - maintainer: Alfredo Beaumont (ziberpunk) - [mailto:alfredo.beaumontATgmailDOTcom]
* [[BulgarianTranslation|Bulgarian]] maintainer: Nikolay Vladimirov (Turki) - [mailto:nikolayATvladimiroffDOTcom]
* [[CatalanTranslation|Catalan]] - maintainer: Jordà Polo (ettin) - [mailto:jordaATettinDOTorg]
* [[ChineseTranslation|Chinese]] - maintainer: ???, Enter the Forum for information: [http://www.wesnoth.cn Wesnoth.CN]
* [[ChineseTaiwanTranslation|Chinese (Taiwan)]] - maintainer: ???
* [[CroatianTranslation|Croatian]] - maintainer: Nino Gunjača (nion) - [mailto:nino.gunjaca@zg.t-com.hr]
* [[CzechTranslation|Czech]] - maintainer: Vladimír Slávik - [mailto:slavikDOTvladimirATseznamDOTcz]
* [[DanishTranslation|Danish]] maintainer: Joe Hansen (joedalton) - [mailto:joedalton2ATyahooDOTdk]
* [[DutchTranslation|Dutch]] - maintainer: Foppe Benedictus (Fopper) - [mailto:foppeDOTbenedictusATgmailDOTcom]
* [[EnglishTranslation|English (US)]] ''(this is the default)'' - maintainer: Sirp - [mailto:davidnwhiteATcomcastDOTnet]
* [[EnglishGBTranslation|English (GB)]] - maintainer: pjr - [mailto:peadar.ruadh@btinternet.com]
* [[Esperanto_translation|Esperanto]] - maintainer: Viliam Bur - [mailto:viliamATburDOTsk]
* [[EstonianTranslation|Estonian]] - maintainer: Mart Tõnso (rinjin) - [mailto:tmATrinjinDOTpriDOTee]
* [[FilipinoTranslation|Filipino]] - maintainer: Karen Eso (keeve) - [mailto:eveUNDERSCOREesoATyahooDOTca]
* [[FinnishTranslation|Finnish]] - maintainer: Samu Voutilainen (Smar) - [mailto:ec5983ATkolumbusDOTfi]
* [[FrenchTranslation|French]] - maintainer: Benoît Timbert (Noyga) [mailto:benoitDOTtimbertATfreeDOTfr] - translation team mailing list [mailto:wesnothATmlDOTfreeDOTfr]
* [[FriulianTranslation|Friulian]] - ???
* [[GalicianTranslation|Galician]] - maintainer: Leandro Regueiro - [mailto:leandroDOTregueiroATgmailDOTcom] [http://trasno.net Proxecto Trasno]
* [[GermanTranslation|German]] - maintainer: Christoph Berg (chrber) - [mailto:ChristophDOTBergATkpm-sportDOTde]
* [[GreekTranslation|Greek]] - maintainer: Konstantinos Egarhos [mailto:atixosATgmailDOTcom]
* [[HebrewTranslation|Hebrew]] - maintainer: Oron Peled - [mailto:oronATactcomDOTcoDOTil]
* [[HungarianTranslation|Hungarian]] - maintainer: Kádár-Németh Krisztián - [mailto:krisztian.kadATgmailDOTcom]; vice-maintainer: Németh Tamás [mailto:ntomaszATkabelnetDOThu]
* [[IndonesianTranslation|Indonesian]] - maintainer: Nicky Inkrais Witras [mailto:inkraiswitrasATyahooDOTcom]
* [[ItalianTranslation|Italian]] - maintainer: Luciano Montanaro - [mailto:mikelima@cirulla.net]
* [[JapaneseTranslation|Japanese]] - maintainer: Nobuhito Okada - [mailto:okyadaATgmailDOTcom]
* [[KoreanTranslation|Korean]] - maintainer: ???
* [[LatinTranslation|Latin]] - maintainer: Marc Polo ([http://www.wesnoth.org/forum/privmsg.php?mode=post&u=571 mpolo]) - No mail address specified
* [[LithuanianTranslation|Lithuanian]] - maintainer: Andrius Štikonas - [mailto:stikonasATgmailDOTcom]
* [[MacedonianTranslation|Macedonian]] - maintainer: Dimitar Ilccov (Mythological)
* [[NorwegianTranslation|Norwegian]] - maintainer: Gaute Jao (Gauteamus) - [mailto:gauteamusATgmailDOTcom]
* [[OccitanTranslation|Occitan]] - maintainer: Nobody, currently
* [[PolishTranslation|Polish]] - maintainer: Zbigniew Banach - [mailto:zDOTbanachATwsisizDOTeduDOTpl]
* [[PortugueseTranslation|Portuguese Brazilian]] - maintainer: Claus Aranha (caranha) - [mailto:caranhaATgmailDOTcom]
* [[PortugueseContinentalTranslation|Portuguese Continental(pt_PT)]] - maintainer: Sérgio Lopes [mailto:knitter.is@gmail.com]
* [[RomanianTranslation|Romanian]] - ???
* [[RussianTranslation|Russian]] - maintainer: Victor Zabavin [mailto:viczaATzmailDOTru]
* [[SerbianTranslation|Serbian]] - maintainer: Srećko Toroman (freecraft)- [mailto:sreckotoromanATgmailDOTcom]
* [[(sk) Preklad|Slovak]] - maintainer: Viliam Bur - [mailto:viliamATburDOTsk]; wiki: [[(sk) Návod]]
* [[SlovenianTranslation|Slovenian]] - maintainer: Jaka Kranjc (lynx) - [mailto:lynxlupodianAThotmailDOTcom]
* [[SpanishTranslation|Spanish]] - maintainer: Sergi March [mailto:sergiPUNTOmarchENgmail.com]
* [[SwedishTranslation|Swedish]] - maintainer: Gustav Tiger (Tigge) - [mailto:adminATtiggeDOTorg]
* [[TurkishTranslation|Turkish]] - maintainer: Nilgün Belma Bugüner - [mailto:nilgunATbelgelerDOTgenDOTtr]
* [[Wesnoth-in-Valencian|Valencian]] - maintainer: Mario (Mavorte) - [mailto:mavorte1ATyahooDOTes]
* [[VietnameseTranslation|Vietnamese]] - maintainer: Do Hong Minh - [mailto:minhdhAThutticDOTcom]

Other ideas (remember, these are just ideas):
* Translations into Asian languages
** Asian languages are already supported. See [[WesnothAsianLanguages]].

== Mailing List ==

There now is a mailinglist dedicated to translation matters. It is mainly intended to be used for informing translation maintainers about important changes, to announce string freezes and other special things. Everyone is free to subscribe to this list. You can find this list, entitled wesnoth-i18n at the listing of all Wesnoth mailing lists:

[http://gna.org/mail/?group=wesnoth http://gna.org/mail/?group=wesnoth]

The archive for this list is to be found [http://mail.gna.org/public/wesnoth-i18n/ here].
Please keep in mind that this list is not meant for discussing changes for one single translation but stuff that is relevant to all translations.

== See also ==

* [[WesnothTranslationsHowTo]]
* [[GetText]]
* [http://gettext.wesnoth.org Translations statistics (stable)]
* [http://gettext.wesnoth.org/index.php?version=trunk&package=alloff Translations statistics (development)]
* [[WesCamp| Translating User made Campaigns (featuring WesCamp-i18n)]]
* [[SpellingMistakes]]

[[Category:Translations|*]]

FrenchTranslation

2008-05-31T19:04:41Z

Noyga: /* Ponctuation */

Battle for Wesnoth - Traduction française
== Le mot d'introduction ==

Cette page sert à mieux coordonner l'effort de tous et à donner les informations souvent demandées avant de se lancer dans la traduction française.

== Règles de traduction ==
=== Respect des termes de l'univers de Wesnoth ===
Pour améliorer la cohérence de l'ensemble des traductions, utilisez :
# le [http://units.wesnoth.org/1.4/fr_FR/mainline.html dictionnaire des unités], qui vous permet de voir les noms par langues, par races, et par campagnes ;
# le [[NomsCommuns | wiki des noms communs]] ;
# le [[NomsPropres | wiki des noms propres]] ;
# des [http://elsap1.unicaen.fr/cgi-bin/cherches.cgi synonymes] pour enrichir vos phrases.

=== Respect du contexte ===
Il est important de correctement traduire les différents textes. Il ne suffit pas de traduire mot à mot les différentes phrases, il faut aussi faire très attention au contexte.

=== Respect des règles de typographie ===

==== Titres ====
Les titres des campagnes, des scénarios et des chapitres doivent suivre les règles de la langue française. Ces règles se trouvent sur http://fr.wikipedia.org/wiki/Wikipédia:Conventions_typographiques.

==== Ponctuation ====
Les traductions doivent aussi suivre les règles de ponctuation de la langue française, essentielles à un bon affichage du texte ; par exemple, l'utilisation d'une espace fine avant le signe « : » évitera que ce signe ne se trouve en début de ligne d'un texte. Ces règles se trouvent sur http://www.reveenjoie-poesie.com/outils-linguistiques/Typographie_francaise.html.

Il est préférable de ne pas mettre de virgule ni avant le « et », ni avant le « ou » (contrairement à l'anglais).

Remarque :
- sous Windows, la combinaison Alt+(0160) permet d'écrire une espace fine (les parenthèses indiquent qu'il faut maintenir la touche Alt appuyée).
Voici d'autres raccourcis : http://www.crdp-montpellier.fr/cd48/tice/trucs/majuscules.htm#win
- sous linux cette même combinaison est Alt+espace

==== Majuscules ====
Les majuscules doivent être accentuées dans les textes traduits : À, Â, Æ, Ç, É, Ê, È, Î, Ô, Œ, Ù, Û...

Voici également quelques rappels sur des confusions fréquentes :
# pas de majuscules aux noms des races (« nains », « elfes », « orcs », etc.) ;
# majuscules aux noms de clans ou de factions (les humains de « l'Ordre de la Serre Pourpre ») ;
# majuscules aux points cardinaux quand on parle d'une partie d'un tout (« les forêts de l'Ouest » peuvent se trouver à l'est), et minuscule quand on parle de la direction (« aller vers le nord »).

=== Respect des règles de l'orthographe ===
Il est préférable de soigner sa grammaire et son orthographe :
# le CNRS et l'ATILF fournissent un dictionnaire en ligne performant et complet : http://atilf.atilf.fr/
# et vous pourrez vérifier la conjugaison de vos verbes ici : http://www.conjugue-moi.com/.

Les [http://www.academie-francaise.fr/langue/orthographe/regles.html rectifications de l'orthographe préconisées par l'Académie Française] peuvent s'appliquer.

== Principes de traduction pour Wesnoth ==
Le principe est de mettre à jour les fichiers .po, fichiers servant à gérer les traductions dans Wesnoth. Les échanges se font via la mailing list.

=== S'inscrire à la mailing list ===
La mailing list francophone de Wesnoth est l'outil privilégié pour
# d'abord avertir les traducteurs que vous allez commencer une traduction (et éviter de travailler sur le même fichier),
# envoyer ses traductions pour validation ou relecture,
# poser des questions.

Pour s'inscrire à la mailing list, envoyez un mail vide ayant comme sujet « subscribe » (il sera traité par un robot) ; ou cliquez directement ici mailto:wesnoth-request@ml.free.fr?subject=subscribe et envoyez...

Les responsables des différentes mailing list sont ici : [[WesnothTranslations]].

Les archives de la mailing list sont ici : http://news.gmane.org/gmane.games.wesnoth-fr ; vous pouvez vous abonner au serveur de news news.gmane.org (gmane.games.wesnoth-fr).

Il est également possible de discuter sur le canal IRC #wesnothfr (sur irc.freenode.net) ou sur le forum, mais l'équipe de traduction française ne s'y promène que rarement.

=== Récupérer les fichiers .po nécessaires ===
Les fichiers à traduire sont accessibles :
# soit par cette page : http://gettext.wesnoth.org/ (le plus simple),
# soit par le CVS : http://savannah.nongnu.org/cvs/?group=wesnoth (si on aime CVS).

=== Modifier les fichiers .po et vérifier le statut des lignes traduites ===
Plusieurs logiciels permettent de modifier ces fichiers :
# les éditeurs de texte
#* [http://notepad-plus.sourceforge.net/fr/site.htm notepad++] ;
#* [http://www.textpad.com/ textpad] ;
#* ou, pour Mac, [http://www.barebones.com/products/textwrangler/index.shtml Textwrangler] ;
#* et puis bien d'autres encore...
# ou des éditeurs spécifiques aux fichiers .po
#* [http://www.poedit.net/ poEdit], pour Mac et PC ;
#* [http://i18n.kde.org/tools/kbabel/ KBabel] ;
#* [http://gtranslator.sourceforge.net/ gtranslator].

Chaque champ de traduction possède un statut :
# si vous traduisez pour la première fois un champ, mettez-le en traduction approximative ("fuzzy" en anglais), et ce même si c'est une traduction très basique ; toute traduction doit être relue au moins une fois avant d'être approuvée ;
# si vous relisez un champ, libre à vous de décider de son statut après votre relecture ;
#* sortez-le de son état approximatif si vous le considérez incontestablement bien traduit ;
#* laissez-le à l'état approximatif et demandez une deuxième relecture si vous n'êtes pas sûr de la traduction.

=== Tester sa traduction ===
Si vous le désirez, vous pouvez immédiatement tester votre traduction :
# enlevez l'option fuzzy de la ligne (ou des lignes) que vous voulez vérifier ;
# générez un fichier compilé « .mo » à partir du fichier texte « .po » ;
#*En ligne de commande : la commande « msgfmt » peut être utilisée avec le nom du fichier « .po » (exemple : « msgfmt mon_fichier.po -o mon_fichier.mo » générera « mon_fichier.mo »).
#*Avec l'éditeur « poedit » : « Fichier -> Préférence », onglet « Editeur, cochez la case « Compiler automatiquement les fichiers .mo lors de la sauvegarde » ; sauvez le fichier.
# copiez votre fichier dans le répertoire contenant les traductions et renommez-le ;
#*Sous Windows, <Répertoire d'installation de Wesnoth>\fr\LC_MESSAGES\<Nom du fichier à tester> (Exemple : C:\Wesnoth\po\fr\LC_MESSAGES\wesnoth-utbs.mo) ;
#*Sous Linux, répertoire en fonction de la distribution (Exemple Mandriva : /usr/share/locale/fr/LC_MESSAGES).
# jouez.... jusqu'au moment où le texte traduit est censé apparaître ; il n'est pas nécessaire de tout reprendre depuis le début, une sauvegarde fonctionne. Un texte traduit sans erreur apparaît... traduit.

Remarque : pour accélérer les tests, vous pouvez utiliser le mode debug de Wesnoth :
#Pour passer en mode débug :
#*taper : (pour ouvrir le mode de commande), puis : debug<entrée>
#*ou taper "wesnoth.exe --debug",
#*ou taper "wesnoth.exe -d"
# pour utiliser le mode débug :
#*":debug" entre en mode debug
#*":n" termine le scénario immédiatement

=== Envoyer sa traduction ===
Une traduction terminée est compressée, puis envoyée à la ML.

Il est préférable, en cas de relecture, de signaler les modifications dans le corps du mail, par exemple en faisant comme ci-dessous :
#Exemple 1 (refonte d'une phrase) : N° ligne Anciene version => Nouvelle version.
#Exemple 2 (correction d'une faute, indiquée par des *) : N°Ligne Ancien*n*e version

Il est également possible de générer un fichier différentiel entre l'ancienne et la nouvelle version ; mais l'expérience semble montrer que cela est peu relu.
Cette techique est surtout à utiliser qu'en cas de modifications massives (cas où le suivi ligne à ligne serait complexe et lourd).

=== Attention ===
* Les variables sont indiquées par ''$'' ; il ne faut pas les traduire : par exemple, ''$gold_left'' se traduit par ''$gold_left'' et non pas par ''$or_restant''.

* Il y a un bug récurent dans les fichiers po : lorsque la phrase traduite '''commence''' par ''$'', rien ne s'affiche dans le jeu. Pour corriger le problème, il suffit de mettre un simple espace devant le signe.

* ''\n'' dans la chaîne originale permet de créer un saut de ligne. Il faut le traduire en mettant ''\n'' en français (c'est important : ''gettext'' bugge s'il n'y a pas le même nombre de ''\n'' des deux côtés).

== Aujourd'hui, qui fait quoi ? ==
Ce chapitre vous permet de savoir qui fait quoi...

Date de dernière mise à jour : 22/05/2008
* Traductions
** wesnoth-thot (The Hammer of Thursagan) : Aurélien
** Invasion from the unknow : Damien

* Relectures / À relire

[[Category:Translations]]

WesnothTranslations

2008-05-31T19:00:04Z

Noyga: /* Translations */

== Translations ==

Wesnoth is currently being translated into the following languages. Instructions on how to contribute are found here:
[[WesnothTranslationsHowTo]].
* [[AfrikaansTranslation|Afrikaans]] - maintainer: Friedel Wolff - [mailto:friedelATSIGNtranslateDOTorgDOTza]
* [[ArabicTranslation|Arabic]] - maintainer: Amnay Mokhtari - [mailto:amnayAToperamailDOTcom]
* [[BasqueTranslation|Basque]] - maintainer: Alfredo Beaumont (ziberpunk) - [mailto:alfredo.beaumontATgmailDOTcom]
* [[BulgarianTranslation|Bulgarian]] maintainer: Nikolay Vladimirov (Turki) - [mailto:nikolayATvladimiroffDOTcom]
* [[CatalanTranslation|Catalan]] - maintainer: Jordà Polo (ettin) - [mailto:jordaATettinDOTorg]
* [[ChineseTranslation|Chinese]] - maintainer: ???, Enter the Forum for information: [http://www.wesnoth.cn Wesnoth.CN]
* [[ChineseTaiwanTranslation|Chinese (Taiwan)]] - maintainer: ???
* [[CroatianTranslation|Croatian]] - maintainer: Nino Gunjača (nion) - [mailto:nino.gunjaca@zg.t-com.hr]
* [[CzechTranslation|Czech]] - maintainer: Vladimír Slávik - [mailto:slavikDOTvladimirATseznamDOTcz]
* [[DanishTranslation|Danish]] maintainer: Joe Hansen (joedalton) - [mailto:joedalton2ATyahooDOTdk]
* [[DutchTranslation|Dutch]] - maintainer: Foppe Benedictus (Fopper) - [mailto:foppeDOTbenedictusATgmailDOTcom]
* [[EnglishTranslation|English (US)]] ''(this is the default)'' - maintainer: Sirp - [mailto:davidnwhiteATcomcastDOTnet]
* [[EnglishGBTranslation|English (GB)]] - maintainer: pjr - [mailto:peadar.ruadh@btinternet.com]
* [[Esperanto_translation|Esperanto]] - maintainer: Viliam Bur - [mailto:viliamATburDOTsk]
* [[EstonianTranslation|Estonian]] - maintainer: Mart Tõnso (rinjin) - [mailto:tmATrinjinDOTpriDOTee]
* [[FilipinoTranslation|Filipino]] - maintainer: Karen Eso (keeve) - [mailto:eveUNDERSCOREesoATyahooDOTca]
* [[FinnishTranslation|Finnish]] - maintainer: Samu Voutilainen (Smar) - [mailto:ec5983ATkolumbusDOTfi]
* [[FrenchTranslation|French]] - maintainer: Benoît Timbert (Noyga) [mailto:benoitDOTtimbertATfreeDOTfr] - translation team mailing list [mailto:wesnothATmlDOTfreeDOTfr]
* [[GalicianTranslation|Galician]] - maintainer: Leandro Regueiro - [mailto:leandroDOTregueiroATgmailDOTcom] [http://trasno.net Proxecto Trasno]
* [[GermanTranslation|German]] - maintainer: Christoph Berg (chrber) - [mailto:ChristophDOTBergATkpm-sportDOTde]
* [[GreekTranslation|Greek]] - maintainer: Konstantinos Egarhos [mailto:atixosATgmailDOTcom]
* [[HebrewTranslation|Hebrew]] - maintainer: Oron Peled - [mailto:oronATactcomDOTcoDOTil]
* [[HungarianTranslation|Hungarian]] - maintainer: Kádár-Németh Krisztián - [mailto:krisztian.kadATgmailDOTcom]; vice-maintainer: Németh Tamás [mailto:ntomaszATkabelnetDOThu]
* [[IndonesianTranslation|Indonesian]] - maintainer: Nicky Inkrais Witras [mailto:inkraiswitrasATyahooDOTcom]
* [[ItalianTranslation|Italian]] - maintainer: Luciano Montanaro - [mailto:mikelima@cirulla.net]
* [[JapaneseTranslation|Japanese]] - maintainer: Nobuhito Okada - [mailto:okyadaATgmailDOTcom]
* [[KoreanTranslation|Korean]] - maintainer: ???
* [[LatinTranslation|Latin]] - maintainer: Marc Polo ([http://www.wesnoth.org/forum/privmsg.php?mode=post&u=571 mpolo]) - No mail address specified
* [[LithuanianTranslation|Lithuanian]] - maintainer: Andrius Štikonas - [mailto:stikonasATgmailDOTcom]
* [[MacedonianTranslation|Macedonian]] - maintainer: Dimitar Ilccov (Mythological)
* [[NorwegianTranslation|Norwegian]] - maintainer: Gaute Jao (Gauteamus) - [mailto:gauteamusATgmailDOTcom]
* [[OccitanTranslation|Occitan]] - maintainer: Nobody, currently
* [[PolishTranslation|Polish]] - maintainer: Zbigniew Banach - [mailto:zDOTbanachATwsisizDOTeduDOTpl]
* [[PortugueseTranslation|Portuguese Brazilian]] - maintainer: Claus Aranha (caranha) - [mailto:caranhaATgmailDOTcom]
* [[PortugueseContinentalTranslation|Portuguese Continental(pt_PT)]] - maintainer: Sérgio Lopes [mailto:knitter.is@gmail.com]
* [[RussianTranslation|Russian]] - maintainer: Victor Zabavin [mailto:viczaATzmailDOTru]
* [[SerbianTranslation|Serbian]] - maintainer: Srećko Toroman (freecraft)- [mailto:sreckotoromanATgmailDOTcom]
* [[(sk) Preklad|Slovak]] - maintainer: Viliam Bur - [mailto:viliamATburDOTsk]; wiki: [[(sk) Návod]]
* [[SlovenianTranslation|Slovenian]] - maintainer: Jaka Kranjc (lynx) - [mailto:lynxlupodianAThotmailDOTcom]
* [[SpanishTranslation|Spanish]] - maintainer: Sergi March [mailto:sergiPUNTOmarchENgmail.com]
* [[SwedishTranslation|Swedish]] - maintainer: Gustav Tiger (Tigge) - [mailto:adminATtiggeDOTorg]
* [[TurkishTranslation|Turkish]] - maintainer: Nilgün Belma Bugüner - [mailto:nilgunATbelgelerDOTgenDOTtr]
* [[Wesnoth-in-Valencian|Valencian]] - maintainer: Mario (Mavorte) - [mailto:mavorte1ATyahooDOTes]
* [[VietnameseTranslation|Vietnamese]] - maintainer: Do Hong Minh - [mailto:minhdhAThutticDOTcom]

Other ideas (remember, these are just ideas):
* Translations into Asian languages
** Asian languages are already supported. See [[WesnothAsianLanguages]].

== Mailing List ==

There now is a mailinglist dedicated to translation matters. It is mainly intended to be used for informing translation maintainers about important changes, to announce string freezes and other special things. Everyone is free to subscribe to this list. You can find this list, entitled wesnoth-i18n at the listing of all Wesnoth mailing lists:

[http://gna.org/mail/?group=wesnoth http://gna.org/mail/?group=wesnoth]

The archive for this list is to be found [http://mail.gna.org/public/wesnoth-i18n/ here].
Please keep in mind that this list is not meant for discussing changes for one single translation but stuff that is relevant to all translations.

== See also ==

* [[WesnothTranslationsHowTo]]
* [[GetText]]
* [http://gettext.wesnoth.org Translations statistics (stable)]
* [http://gettext.wesnoth.org/index.php?version=trunk&package=alloff Translations statistics (development)]
* [[WesCamp| Translating User made Campaigns (featuring WesCamp-i18n)]]
* [[SpellingMistakes]]

[[Category:Translations|*]]

WesnothTranslations

2008-05-31T18:58:06Z

Noyga: /* Translations */

== Translations ==

Wesnoth is currently being translated into the following languages. Instructions on how to contribute are found here:
[[WesnothTranslationsHowTo]].
* [[AfrikaansTranslation|Afrikaans]] - maintainer: Friedel Wolff - [mailto:friedelATSIGNtranslateDOTorgDOTza]
* [[ArabicTranslation|Arabic]] - maintainer: Amnay Mokhtari - [mailto:amnayAToperamailDOTcom]
* [[BasqueTranslation|Basque]] - maintainer: Alfredo Beaumont (ziberpunk) - [mailto:alfredo.beaumontATgmailDOTcom]
* [[BulgarianTranslation|Bulgarian]] maintainer: Nikolay Vladimirov (Turki) - [mailto:nikolayATvladimiroffDOTcom]
* [[CatalanTranslation|Catalan]] - maintainer: Jordà Polo (ettin) - [mailto:jordaATettinDOTorg]
* [[ChineseTranslation|Chinese]] - maintainer: ???, Enter the Forum for information: [http://www.wesnoth.cn Wesnoth.CN]
* [[ChineseTaiwanTranslation|Chinese (Taiwan)]] - maintainer: ???
* [[CroatianTranslation|Croatian]] - maintainer: Nino Gunjača (nion) - [mailto:nino.gunjaca@zg.t-com.hr]
* [[CzechTranslation|Czech]] - maintainer: Vladimír Slávik - [mailto:slavikDOTvladimirATseznamDOTcz]
* [[DanishTranslation|Danish]] maintainer: Joe Hansen (joedalton) - [mailto:joedalton2ATyahooDOTdk]
* [[DutchTranslation|Dutch]] - maintainer: Foppe Benedictus (Fopper) - [mailto:foppeDOTbenedictusATgmailDOTcom]
* [[EnglishTranslation|English (US)]] ''(this is the default)'' - maintainer: Sirp - [mailto:davidnwhiteATcomcastDOTnet]
* [[EnglishGBTranslation|English (GB)]] - maintainer: pjr - [mailto:peadar.ruadh@btinternet.com]
* [[Esperanto_translation|Esperanto]] - maintainer: Viliam Bur - [mailto:viliamATburDOTsk]
* [[EstonianTranslation|Estonian]] - maintainer: Mart Tõnso (rinjin) - [mailto:tmATrinjinDOTpriDOTee]
* [[FilipinoTranslation|Filipino]] - maintainer: Karen Eso (keeve) - [mailto:eveUNDERSCOREesoATyahooDOTca]
* [[FinnishTranslation|Finnish]] - maintainer: Samu Voutilainen (Smar) - [mailto:ec5983ATkolumbusDOTfi]
* [[FrenchTranslation|French]] - maintainer: Benoît Timbert (Noyga) [mailto:benoitDOTtimbertATfreeDOTfr] - translation team mailing list [mailto:wesnothATmlDOTfreeDOTfr]
* [[GalicianTranslation|Galician]] - maintainer: Leandro Regueiro - [mailto:leandroDOTregueiroATgmailDOTcom] [http://trasno.net Proxecto Trasno]
* [[GermanTranslation|German]] - maintainer: Christoph Berg (chrber) - [mailto:ChristophDOTBergATkpm-sportDOTde]
* [[GreekTranslation|Greek]] - maintainer: Konstantinos Egarhos [mailto:atixosATgmailDOTcom]
* [[HebrewTranslation|Hebrew]] - maintainer: Oron Peled - [mailto:oronATactcomDOTcoDOTil]
* [[HungarianTranslation|Hungarian]] - maintainer: Kádár-Németh Krisztián - [mailto:krisztian.kadATgmailDOTcom]; vice-maintainer: Németh Tamás [mailto:ntomaszATkabelnetDOThu]
* [[IndonesianTranslation|Indonesian]] - maintainer: Nicky Inkrais Witras [mailto:inkraiswitrasATyahooDOTcom]
* [[ItalianTranslation|Italian]] - maintainer: Luciano Montanaro - [mailto:mikelima@cirulla.net]
* [[JapaneseTranslation|Japanese]] - maintainer: Nobuhito Okada - [mailto:okyadaATgmailDOTcom]
* [[KoreanTranslation|Korean]] - maintainer: ???
* [[LatinTranslation|Latin]] - maintainer: Marc Polo ([http://www.wesnoth.org/forum/privmsg.php?mode=post&u=571 mpolo]) - No mail address specified
* [[LithuanianTranslation|Lithuanian]] - maintainer: Andrius Štikonas - [mailto:stikonasATgmailDOTcom]
* [[MacedonianTranslation|Macedonian]] - maintainer: Dimitar Ilccov
* [[NorwegianTranslation|Norwegian]] - maintainer: Gaute Jao (Gauteamus) - [mailto:gauteamusATgmailDOTcom]
* [[OccitanTranslation|Occitan]] - maintainer: Nobody, currently
* [[PolishTranslation|Polish]] - maintainer: Zbigniew Banach - [mailto:zDOTbanachATwsisizDOTeduDOTpl]
* [[PortugueseTranslation|Portuguese Brazilian]] - maintainer: Claus Aranha (caranha) - [mailto:caranhaATgmailDOTcom]
* [[PortugueseContinentalTranslation|Portuguese Continental(pt_PT)]] - maintainer: Sérgio Lopes [mailto:knitter.is@gmail.com]
* [[RussianTranslation|Russian]] - maintainer: Victor Zabavin [mailto:viczaATzmailDOTru]
* [[SerbianTranslation|Serbian]] - maintainer: Srećko Toroman (freecraft)- [mailto:sreckotoromanATgmailDOTcom]
* [[(sk) Preklad|Slovak]] - maintainer: Viliam Bur - [mailto:viliamATburDOTsk]; wiki: [[(sk) Návod]]
* [[SlovenianTranslation|Slovenian]] - maintainer: Jaka Kranjc (lynx) - [mailto:lynxlupodianAThotmailDOTcom]
* [[SpanishTranslation|Spanish]] - maintainer: Sergi March [mailto:sergiPUNTOmarchENgmail.com]
* [[SwedishTranslation|Swedish]] - maintainer: Gustav Tiger (Tigge) - [mailto:adminATtiggeDOTorg]
* [[TurkishTranslation|Turkish]] - maintainer: Nilgün Belma Bugüner - [mailto:nilgunATbelgelerDOTgenDOTtr]
* [[Wesnoth-in-Valencian|Valencian]] - maintainer: Mario (Mavorte) - [mailto:mavorte1ATyahooDOTes]
* [[VietnameseTranslation|Vietnamese]] - maintainer: Do Hong Minh - [mailto:minhdhAThutticDOTcom]

Other ideas (remember, these are just ideas):
* Translations into Asian languages
** Asian languages are already supported. See [[WesnothAsianLanguages]].

== Mailing List ==

There now is a mailinglist dedicated to translation matters. It is mainly intended to be used for informing translation maintainers about important changes, to announce string freezes and other special things. Everyone is free to subscribe to this list. You can find this list, entitled wesnoth-i18n at the listing of all Wesnoth mailing lists:

[http://gna.org/mail/?group=wesnoth http://gna.org/mail/?group=wesnoth]

The archive for this list is to be found [http://mail.gna.org/public/wesnoth-i18n/ here].
Please keep in mind that this list is not meant for discussing changes for one single translation but stuff that is relevant to all translations.

== See also ==

* [[WesnothTranslationsHowTo]]
* [[GetText]]
* [http://gettext.wesnoth.org Translations statistics (stable)]
* [http://gettext.wesnoth.org/index.php?version=trunk&package=alloff Translations statistics (development)]
* [[WesCamp| Translating User made Campaigns (featuring WesCamp-i18n)]]
* [[SpellingMistakes]]

[[Category:Translations|*]]

WesnothTranslations

2008-05-31T18:54:35Z

Noyga: /* Translations */

== Translations ==

Wesnoth is currently being translated into the following languages. Instructions on how to contribute are found here:
[[WesnothTranslationsHowTo]].
* [[AfrikaansTranslation|Afrikaans]] - maintainer: Friedel Wolff - [mailto:friedelATSIGNtranslateDOTorgDOTza]
* [[ArabicTranslation|Arabic]] - maintainer: Amnay Mokhtari - [mailto:amnayAToperamailDOTcom]
* [[BasqueTranslation|Basque]] - maintainer: Alfredo Beaumont (ziberpunk) - [mailto:alfredo.beaumontATgmailDOTcom]
* [[BulgarianTranslation|Bulgarian]] maintainer: Nikolay Vladimirov (Turki) - [mailto:nikolayATvladimiroffDOTcom]
* [[CatalanTranslation|Catalan]] - maintainer: Jordà Polo (ettin) - [mailto:jordaATettinDOTorg]
* [[ChineseTranslation|Chinese]] - maintainer: ???, Enter the Forum for information: [http://www.wesnoth.cn Wesnoth.CN]
* [[ChineseTaiwanTranslation|Chinese (Taiwan)]] - maintainer: ???
* [[CroatianTranslation|Croatian]] - maintainer: Nino Gunjača (nion) - [mailto:nino.gunjaca@zg.t-com.hr]
* [[CzechTranslation|Czech]] - maintainer: Vladimír Slávik - [mailto:slavikDOTvladimirATseznamDOTcz]
* [[DanishTranslation|Danish]] maintainer: Joe Hansen (joedalton) - [mailto:joedalton2ATyahooDOTdk]
* [[DutchTranslation|Dutch]] - maintainer: Foppe Benedictus (Fopper) - [mailto:foppeDOTbenedictusATgmailDOTcom]
* [[EnglishTranslation|English (US)]] ''(this is the default)'' - maintainer: Sirp - [mailto:davidnwhiteATcomcastDOTnet]
* [[EnglishGBTranslation|English (GB)]] - maintainer: pjr - [mailto:peadar.ruadh@btinternet.com]
* [[Esperanto_translation|Esperanto]] - maintainer: Viliam Bur - [mailto:viliamATburDOTsk]
* [[EstonianTranslation|Estonian]] - maintainer: Mart Tõnso (rinjin) - [mailto:tmATrinjinDOTpriDOTee]
* [[FilipinoTranslation|Filipino]] - maintainer: Karen Eso (keeve) - [mailto:eveUNDERSCOREesoATyahooDOTca]
* [[FinnishTranslation|Finnish]] - maintainer: Samu Voutilainen (Smar) - [mailto:ec5983ATkolumbusDOTfi]
* [[FrenchTranslation|French]] - maintainer: Benoît Timbert (Noyga) [mailto:benoitDOTtimbertATfreeDOTfr]
* [[GalicianTranslation|Galician]] - maintainer: Leandro Regueiro - [mailto:leandroDOTregueiroATgmailDOTcom] [http://trasno.net Proxecto Trasno]
* [[GermanTranslation|German]] - maintainer: Christoph Berg (chrber) - [mailto:ChristophDOTBergATkpm-sportDOTde]
* [[GreekTranslation|Greek]] - maintainer: Konstantinos Egarhos [mailto:atixosATgmailDOTcom]
* [[HebrewTranslation|Hebrew]] - maintainer: Oron Peled - [mailto:oronATactcomDOTcoDOTil]
* [[HungarianTranslation|Hungarian]] - maintainer: Kádár-Németh Krisztián - [mailto:krisztian.kadATgmailDOTcom]; vice-maintainer: Németh Tamás [mailto:ntomaszATkabelnetDOThu]
* [[IndonesianTranslation|Indonesian]] - maintainer: Nicky Inkrais Witras [mailto:inkraiswitrasATyahooDOTcom]
* [[ItalianTranslation|Italian]] - maintainer: Luciano Montanaro - [mailto:mikelima@cirulla.net]
* [[JapaneseTranslation|Japanese]] - maintainer: Nobuhito Okada - [mailto:okyadaATgmailDOTcom]
* [[KoreanTranslation|Korean]] - maintainer: ???
* [[LatinTranslation|Latin]] - maintainer: Marc Polo ([http://www.wesnoth.org/forum/privmsg.php?mode=post&u=571 mpolo]) - No mail address specified
* [[LithuanianTranslation|Lithuanian]] - maintainer: Andrius Štikonas - [mailto:stikonasATgmailDOTcom]
* [[MacedonianTranslation|Macedonian]] - maintainer: Dimitar Ilccov
* [[NorwegianTranslation|Norwegian]] - maintainer: Gaute Jao (Gauteamus) - [mailto:gauteamusATgmailDOTcom]
* [[OccitanTranslation|Occitan]] - maintainer: Nobody, currently
* [[PolishTranslation|Polish]] - maintainer: Zbigniew Banach - [mailto:zDOTbanachATwsisizDOTeduDOTpl]
* [[PortugueseTranslation|Portuguese Brazilian]] - maintainer: Claus Aranha (caranha) - [mailto:caranhaATgmailDOTcom]
* [[PortugueseContinentalTranslation|Portuguese Continental(pt_PT)]] - maintainer: Sérgio Lopes [mailto:knitter.is@gmail.com]
* [[RussianTranslation|Russian]] - maintainer: Victor Zabavin [mailto:viczaATzmailDOTru]
* [[SerbianTranslation|Serbian]] - maintainer: Srećko Toroman (freecraft)- [mailto:sreckotoromanATgmailDOTcom]
* [[(sk) Preklad|Slovak]] - maintainer: Viliam Bur - [mailto:viliamATburDOTsk]; wiki: [[(sk) Návod]]
* [[SlovenianTranslation|Slovenian]] - maintainer: Jaka Kranjc (lynx) - [mailto:lynxlupodianAThotmailDOTcom]
* [[SpanishTranslation|Spanish]] - maintainer: Sergi March [mailto:sergiPUNTOmarchENgmail.com]
* [[SwedishTranslation|Swedish]] - maintainer: Gustav Tiger (Tigge) - [mailto:adminATtiggeDOTorg]
* [[TurkishTranslation|Turkish]] - maintainer: Nilgün Belma Bugüner - [mailto:nilgunATbelgelerDOTgenDOTtr]
* [[Wesnoth-in-Valencian|Valencian]] - maintainer: Mario (Mavorte) - [mailto:mavorte1ATyahooDOTes]
* [[VietnameseTranslation|Vietnamese]] - maintainer: Do Hong Minh - [mailto:minhdhAThutticDOTcom]

Other ideas (remember, these are just ideas):
* Translations into Asian languages
** Asian languages are already supported. See [[WesnothAsianLanguages]].

== Mailing List ==

There now is a mailinglist dedicated to translation matters. It is mainly intended to be used for informing translation maintainers about important changes, to announce string freezes and other special things. Everyone is free to subscribe to this list. You can find this list, entitled wesnoth-i18n at the listing of all Wesnoth mailing lists:

[http://gna.org/mail/?group=wesnoth http://gna.org/mail/?group=wesnoth]

The archive for this list is to be found [http://mail.gna.org/public/wesnoth-i18n/ here].
Please keep in mind that this list is not meant for discussing changes for one single translation but stuff that is relevant to all translations.

== See also ==

* [[WesnothTranslationsHowTo]]
* [[GetText]]
* [http://gettext.wesnoth.org Translations statistics (stable)]
* [http://gettext.wesnoth.org/index.php?version=trunk&package=alloff Translations statistics (development)]
* [[WesCamp| Translating User made Campaigns (featuring WesCamp-i18n)]]
* [[SpellingMistakes]]

[[Category:Translations|*]]

WesnothTranslations

2008-05-31T18:50:30Z

Noyga: /* Translations */

== Translations ==

Wesnoth is currently being translated into the following languages. Instructions on how to contribute are found here:
[[WesnothTranslationsHowTo]].
* [[AfrikaansTranslation|Afrikaans]] - maintainer: Friedel Wolff - [mailto:friedelATSIGNtranslateDOTorgDOTza]
* [[ArabicTranslation|Arabic]] - maintainer: Amnay Mokhtari - [mailto:amnayAToperamailDOTcom]
* [[BasqueTranslation|Basque]] - maintainer: Alfredo Beaumont (ziberpunk) - [mailto:alfredo.beaumontATgmailDOTcom]
* [[BulgarianTranslation|Bulgarian]] maintainer: Nikolay Vladimirov (Turki) - [mailto:nikolayATvladimiroffDOTcom]
* [[CatalanTranslation|Catalan]] - maintainer: Jordà Polo (ettin) - [mailto:jordaATettinDOTorg]
* [[ChineseTranslation|Chinese]] - maintainer: ???, Enter the Forum for information: [http://www.wesnoth.cn Wesnoth.CN]
* [[ChineseTaiwanTranslation|Chinese (Taiwan)]] - maintainer: ???
* [[CroatianTranslation|Croatian]] - maintainer: Nino Gunjača (nion) - [mailto:nino.gunjaca@zg.t-com.hr]
* [[CzechTranslation|Czech]] - maintainer: Vladimír Slávik - [mailto:slavikDOTvladimirATseznamDOTcz]
* [[DanishTranslation|Danish]] maintainer: Joe Hansen (joedalton) - [mailto:joedalton2ATyahooDOTdk]
* [[DutchTranslation|Dutch]] - maintainer: Foppe Benedictus (Fopper) - [mailto:foppeDOTbenedictusATgmailDOTcom]
* [[EnglishTranslation|English (US)]] ''(this is the default)'' - maintainer: Sirp - [mailto:davidnwhiteATcomcastDOTnet]
* [[EnglishGBTranslation|English (GB)]] - maintainer: pjr - [mailto:peadar.ruadh@btinternet.com]
* [[Esperanto_translation|Esperanto]] - maintainer: Viliam Bur - [mailto:viliamATburDOTsk]
* [[EstonianTranslation|Estonian]] - maintainer: Mart Tõnso (rinjin) - [mailto:tmATrinjinDOTpriDOTee]
* [[FilipinoTranslation|Filipino]] - maintainer: Karen Eso (keeve) - [mailto:eveUNDERSCOREesoATyahooDOTca]
* [[FinnishTranslation|Finnish]] - maintainer: Samu Voutilainen (Smar) - [mailto:ec5983ATkolumbusDOTfi]
* [[FrenchTranslation|French]] - maintainer: Benoît Timbert (Noyga) [mailto:benoitDOTtimbertATfreeDOTfr] (interim) or: Guillaume Massart (Piou2fois) - [mailto:massartDOTguillaumeATwanadooDOTfr] (currently away)
* [[GalicianTranslation|Galician]] - maintainer: Leandro Regueiro - [mailto:leandroDOTregueiroATgmailDOTcom] [http://trasno.net Proxecto Trasno]
* [[GermanTranslation|German]] - maintainer: Christoph Berg (chrber) - [mailto:ChristophDOTBergATkpm-sportDOTde]
* [[GreekTranslation|Greek]] - maintainer: Konstantinos Egarhos [mailto:atixosATgmailDOTcom]
* [[HebrewTranslation|Hebrew]] - maintainer: Oron Peled - [mailto:oronATactcomDOTcoDOTil]
* [[HungarianTranslation|Hungarian]] - maintainer: Kádár-Németh Krisztián - [mailto:krisztian.kadATgmailDOTcom]; vice-maintainer: Németh Tamás [mailto:ntomaszATkabelnetDOThu]
* [[IndonesianTranslation|Indonesian]] - maintainer: Nicky Inkrais Witras [mailto:inkraiswitrasATyahooDOTcom]
* [[ItalianTranslation|Italian]] - maintainer: Luciano Montanaro - [mailto:mikelima@cirulla.net]
* [[JapaneseTranslation|Japanese]] - maintainer: Nobuhito Okada - [mailto:okyadaATgmailDOTcom]
* [[KoreanTranslation|Korean]] - maintainer: ???
* [[LatinTranslation|Latin]] - maintainer: Marc Polo ([http://www.wesnoth.org/forum/privmsg.php?mode=post&u=571 mpolo]) - No mail address specified
* [[LithuanianTranslation|Lithuanian]] - maintainer: Andrius Štikonas - [mailto:stikonasATgmailDOTcom]
* [[MacedonianTranslation|Macedonian]] - maintainer: Dimitar Ilccov
* [[NorwegianTranslation|Norwegian]] - maintainer: Gaute Jao (Gauteamus) - [mailto:gauteamusATgmailDOTcom]
* [[OccitanTranslation|Occitan]] - maintainer: Nobody, currently
* [[PolishTranslation|Polish]] - maintainer: Zbigniew Banach - [mailto:zDOTbanachATwsisizDOTeduDOTpl]
* [[PortugueseTranslation|Portuguese Brazilian]] - maintainer: Claus Aranha (caranha) - [mailto:caranhaATgmailDOTcom]
* [[PortugueseContinentalTranslation|Portuguese Continental(pt_PT)]] - maintainer: Sérgio Lopes [mailto:knitter.is@gmail.com]
* [[RussianTranslation|Russian]] - maintainer: Victor Zabavin [mailto:viczaATzmailDOTru]
* [[SerbianTranslation|Serbian]] - maintainer: Srećko Toroman (freecraft)- [mailto:sreckotoromanATgmailDOTcom]
* [[(sk) Preklad|Slovak]] - maintainer: Viliam Bur - [mailto:viliamATburDOTsk]; wiki: [[(sk) Návod]]
* [[SlovenianTranslation|Slovenian]] - maintainer: Jaka Kranjc (lynx) - [mailto:lynxlupodianAThotmailDOTcom]
* [[SpanishTranslation|Spanish]] - maintainer: Sergi March [mailto:sergiPUNTOmarchENgmail.com]
* [[SwedishTranslation|Swedish]] - maintainer: Gustav Tiger (Tigge) - [mailto:adminATtiggeDOTorg]
* [[TurkishTranslation|Turkish]] - maintainer: Nilgün Belma Bugüner - [mailto:nilgunATbelgelerDOTgenDOTtr]
* [[Wesnoth-in-Valencian|Valencian]] - maintainer: Mario (Mavorte) - [mailto:mavorte1ATyahooDOTes]
* [[VietnameseTranslation|Vietnamese]] - maintainer: Do Hong Minh - [mailto:minhdhAThutticDOTcom]

Other ideas (remember, these are just ideas):
* Translations into Asian languages
** Asian languages are already supported. See [[WesnothAsianLanguages]].

== Mailing List ==

There now is a mailinglist dedicated to translation matters. It is mainly intended to be used for informing translation maintainers about important changes, to announce string freezes and other special things. Everyone is free to subscribe to this list. You can find this list, entitled wesnoth-i18n at the listing of all Wesnoth mailing lists:

[http://gna.org/mail/?group=wesnoth http://gna.org/mail/?group=wesnoth]

The archive for this list is to be found [http://mail.gna.org/public/wesnoth-i18n/ here].
Please keep in mind that this list is not meant for discussing changes for one single translation but stuff that is relevant to all translations.

== See also ==

* [[WesnothTranslationsHowTo]]
* [[GetText]]
* [http://gettext.wesnoth.org Translations statistics (stable)]
* [http://gettext.wesnoth.org/index.php?version=trunk&package=alloff Translations statistics (development)]
* [[WesCamp| Translating User made Campaigns (featuring WesCamp-i18n)]]
* [[SpellingMistakes]]

[[Category:Translations|*]]

WesnothTranslations

2008-05-31T18:46:23Z

Noyga: /* Translations */

== Translations ==

Wesnoth is currently being translated into the following languages. Instructions on how to contribute are found here:
[[WesnothTranslationsHowTo]].
* [[AfrikaansTranslation|Afrikaans]] - maintainer: Friedel Wolff - [mailto:friedelATSIGNtranslateDOTorgDOTza]
* [[ArabicTranslation|Arabic]] - maintainer: Amnay Mokhtari - [mailto:amnayAToperamailDOTcom]
* [[BasqueTranslation|Basque]] - maintainer: Alfredo Beaumont (ziberpunk) - [mailto:alfredo.beaumontATgmailDOTcom]
* [[BulgarianTranslation|Bulgarian]] maintainer: Nikolay Vladimirov (Turki) - [mailto:nikolayATvladimiroffDOTcom]
* [[CatalanTranslation|Catalan]] - maintainer: Jordà Polo (ettin) - [mailto:jordaATettinDOTorg]
* [[ChineseTranslation|Chinese]] - maintainer: ???, Enter the Forum for information: [http://www.wesnoth.cn Wesnoth.CN]
* [[ChineseTaiwanTranslation|Chinese (Taiwan)]] - maintainer: ???
* [[CroatianTranslation|Croatian]] - maintainer: Nino Gunjača (nion) - [mailto:nino.gunjaca@zg.t-com.hr]
* [[CzechTranslation|Czech]] - maintainer: Vladimír Slávik - [mailto:slavikDOTvladimirATseznamDOTcz]
* [[DanishTranslation|Danish]] maintainer: Joe Hansen (joedalton) - [mailto:joedalton2ATyahooDOTdk]
* [[DutchTranslation|Dutch]] - maintainer: Foppe Benedictus (Fopper) - [mailto:foppeDOTbenedictusATgmailDOTcom]
* [[EnglishTranslation|English (US)]] ''(this is the default)'' - maintainer: Sirp - [mailto:davidnwhiteATcomcastDOTnet]
* [[EnglishGBTranslation|English (GB)]] - maintainer: pjr - [mailto:peadar.ruadh@btinternet.com]
* [[Esperanto_translation|Esperanto]] - maintainer: Viliam Bur - [mailto:viliamATburDOTsk]
* [[EstonianTranslation|Estonian]] - maintainer: Mart Tõnso (rinjin) - [mailto:tmATrinjinDOTpriDOTee]
* [[FilipinoTranslation|Filipino]] - maintainer: Karen Eso (keeve) - [mailto:eveUNDERSCOREesoATyahooDOTca]
* [[FinnishTranslation|Finnish]] - maintainer: Samu Voutilainen (Smar) - [mailto:ec5983ATkolumbusDOTfi]
* [[FrenchTranslation|French]] - maintainer: Benoît Timbert (Noyga) [mailto:benoitDOTtimbertATfreeDOTfr] (interim) or: Guillaume Massart (Piou2fois) - [mailto:massartDOTguillaumeATwanadooDOTfr] (currently away)
* [[GalicianTranslation|Galician]] - maintainer: Leandro Regueiro - [mailto:leandroDOTregueiroATgmailDOTcom] [http://trasno.net Proxecto Trasno]
* [[GermanTranslation|German]] - maintainer: Christoph Berg (chrber) - [mailto:ChristophDOTBergATkpm-sportDOTde]
* [[GreekTranslation|Greek]] - maintainer: Konstantinos Egarhos [mailto:atixosATgmailDOTcom]
* [[HebrewTranslation|Hebrew]] - maintainer: Oron Peled - [mailto:oronATactcomDOTcoDOTil]
* [[HungarianTranslation|Hungarian]] - maintainer: Kádár-Németh Krisztián - [mailto:krisztian.kadATgmailDOTcom]; vice-maintainer: Németh Tamás [mailto:ntomaszATkabelnetDOThu]
* [[IndonesianTranslation|Indonesian]] - maintainer: Nicky Inkrais Witras [mailto:inkraiswitrasATyahooDOTcom]
* [[ItalianTranslation|Italian]] - maintainer: Luciano Montanaro - [mailto:mikelima@cirulla.net]
* [[JapaneseTranslation|Japanese]] - maintainer: Nobuhito Okada - [mailto:okyadaATgmailDOTcom]
* [[KoreanTranslation|Korean]] - maintainer: ???
* [[LatinTranslation|Latin]] - maintainer: Marc Polo ([http://www.wesnoth.org/forum/privmsg.php?mode=post&u=571 mpolo]) - No mail address specified
* [[LithuanianTranslation|Lithuanian]] - maintainer: Andrius Štikonas - [mailto:stikonasATgmailDOTcom]
* [[MacedonianTranslation|Macedonian]] - maintainer: Dimitar Ilccov (Mythological)([http://www.wesnoth.org/forum/privmsg.php?mode=post&u=571 mythological]) - No mail address specified
* [[NorwegianTranslation|Norwegian]] - maintainer: Gaute Jao (Gauteamus) - [mailto:gauteamusATgmailDOTcom]
* [[OccitanTranslation|Occitan]] - maintainer: Nobody, currently
* [[PolishTranslation|Polish]] - maintainer: Zbigniew Banach - [mailto:zDOTbanachATwsisizDOTeduDOTpl]
* [[PortugueseTranslation|Portuguese Brazilian]] - maintainer: Claus Aranha (caranha) - [mailto:caranhaATgmailDOTcom]
* [[PortugueseContinentalTranslation|Portuguese Continental(pt_PT)]] - maintainer: Sérgio Lopes [mailto:knitter.is@gmail.com]
* [[RussianTranslation|Russian]] - maintainer: Victor Zabavin [mailto:viczaATzmailDOTru]
* [[SerbianTranslation|Serbian]] - maintainer: Srećko Toroman (freecraft)- [mailto:sreckotoromanATgmailDOTcom]
* [[(sk) Preklad|Slovak]] - maintainer: Viliam Bur - [mailto:viliamATburDOTsk]; wiki: [[(sk) Návod]]
* [[SlovenianTranslation|Slovenian]] - maintainer: Jaka Kranjc (lynx) - [mailto:lynxlupodianAThotmailDOTcom]
* [[SpanishTranslation|Spanish]] - maintainer: Sergi March [mailto:sergiPUNTOmarchENgmail.com]
* [[SwedishTranslation|Swedish]] - maintainer: Gustav Tiger (Tigge) - [mailto:adminATtiggeDOTorg]
* [[TurkishTranslation|Turkish]] - maintainer: Nilgün Belma Bugüner - [mailto:nilgunATbelgelerDOTgenDOTtr]
* [[Wesnoth-in-Valencian|Valencian]] - maintainer: Mario (Mavorte) - [mailto:mavorte1ATyahooDOTes]
* [[VietnameseTranslation|Vietnamese]] - maintainer: Do Hong Minh - [mailto:minhdhAThutticDOTcom]

Other ideas (remember, these are just ideas):
* Translations into Asian languages
** Asian languages are already supported. See [[WesnothAsianLanguages]].

== Mailing List ==

There now is a mailinglist dedicated to translation matters. It is mainly intended to be used for informing translation maintainers about important changes, to announce string freezes and other special things. Everyone is free to subscribe to this list. You can find this list, entitled wesnoth-i18n at the listing of all Wesnoth mailing lists:

[http://gna.org/mail/?group=wesnoth http://gna.org/mail/?group=wesnoth]

The archive for this list is to be found [http://mail.gna.org/public/wesnoth-i18n/ here].
Please keep in mind that this list is not meant for discussing changes for one single translation but stuff that is relevant to all translations.

== See also ==

* [[WesnothTranslationsHowTo]]
* [[GetText]]
* [http://gettext.wesnoth.org Translations statistics (stable)]
* [http://gettext.wesnoth.org/index.php?version=trunk&package=alloff Translations statistics (development)]
* [[WesCamp| Translating User made Campaigns (featuring WesCamp-i18n)]]
* [[SpellingMistakes]]

[[Category:Translations|*]]

WesnothTranslations

2008-05-31T18:42:19Z

Noyga: /* Translations */

== Translations ==

Wesnoth is currently being translated into the following languages. Instructions on how to contribute are found here:
[[WesnothTranslationsHowTo]].
* [[AfrikaansTranslation|Afrikaans]] - maintainer: Friedel Wolff - [mailto:friedelATSIGNtranslateDOTorgDOTza]
* [[ArabicTranslation|Arabic]] - maintainer: Amnay Mokhtari - [mailto:amnayAToperamailDOTcom]
* [[BasqueTranslation|Basque]] - maintainer: Alfredo Beaumont (ziberpunk) - [mailto:alfredo.beaumontATgmailDOTcom]
* [[BulgarianTranslation|Bulgarian]] maintainer: Nikolay Vladimirov (Turki) - [mailto:nikolayATvladimiroffDOTcom]
* [[CatalanTranslation|Catalan]] - maintainer: Jordà Polo (ettin) - [mailto:jordaATettinDOTorg]
* [[ChineseTranslation|Chinese]] - maintainer: ???, Enter the Forum for information: [http://www.wesnoth.cn Wesnoth.CN]
* [[ChineseTaiwanTranslation|Chinese (Taiwan)]] - maintainer: ???
* [[CroatianTranslation|Croatian]] - maintainer: Nino Gunjača (nion) - [mailto:nino.gunjaca@zg.t-com.hr]
* [[CzechTranslation|Czech]] - maintainer: Vladimír Slávik - [mailto:slavikDOTvladimirATseznamDOTcz]
* [[DanishTranslation|Danish]] maintainer: Joe Hansen (joedalton) - [mailto:joedalton2ATyahooDOTdk]
* [[DutchTranslation|Dutch]] - maintainer: Foppe Benedictus (Fopper) - [mailto:foppeDOTbenedictusATgmailDOTcom]
* [[EnglishTranslation|English (US)]] ''(this is the default)'' - maintainer: Sirp - [mailto:davidnwhiteATcomcastDOTnet]
* [[EnglishGBTranslation|English (GB)]] - maintainer: pjr - [mailto:peadar.ruadh@btinternet.com]
* [[Esperanto_translation|Esperanto]] - maintainer: Viliam Bur - [mailto:viliamATburDOTsk]
* [[EstonianTranslation|Estonian]] - maintainer: Mart Tõnso (rinjin) - [mailto:tmATrinjinDOTpriDOTee]
* [[FilipinoTranslation|Filipino]] - maintainer: Karen Eso (keeve) - [mailto:eveUNDERSCOREesoATyahooDOTca]
* [[FinnishTranslation|Finnish]] - maintainer: Samu Voutilainen (Smar) - [mailto:ec5983ATkolumbusDOTfi]
* [[FrenchTranslation|French]] - maintainer: Benoît Timbert (Noyga) [mailto:benoitDOTtimbertATfreeDOTfr] (interim) or: Guillaume Massart (Piou2fois) - [mailto:massartDOTguillaumeATwanadooDOTfr] (currently away)
* [[GalicianTranslation|Galician]] - maintainer: Leandro Regueiro - [mailto:leandroDOTregueiroATgmailDOTcom] [http://trasno.net Proxecto Trasno]
* [[GermanTranslation|German]] - maintainer: Christoph Berg (chrber) - [mailto:ChristophDOTBergATkpm-sportDOTde]
* [[GreekTranslation|Greek]] - maintainer: Konstantinos Egarhos [mailto:atixosATgmailDOTcom]
* [[HebrewTranslation|Hebrew]] - maintainer: Oron Peled - [mailto:oronATactcomDOTcoDOTil]
* [[HungarianTranslation|Hungarian]] - maintainer: Kádár-Németh Krisztián - [mailto:krisztian.kadATgmailDOTcom]; vice-maintainer: Németh Tamás [mailto:ntomaszATkabelnetDOThu]
* [[IndonesianTranslation|Indonesian]] - maintainer: Nicky Inkrais Witras [mailto:inkraiswitrasATyahooDOTcom]
* [[ItalianTranslation|Italian]] - maintainer: Luciano Montanaro - [mailto:mikelima@cirulla.net]
* [[JapaneseTranslation|Japanese]] - maintainer: Nobuhito Okada - [mailto:okyadaATgmailDOTcom]
* [[KoreanTranslation|Korean]] - maintainer: ???
* [[LatinTranslation|Latin]] - maintainer: Marc Polo ([http://www.wesnoth.org/forum/privmsg.php?mode=post&u=571 mpolo]) - No mail address specified
* [[LithuanianTranslation|Lithuanian]] - maintainer: Andrius Štikonas - [mailto:stikonasATgmailDOTcom]
* [[NorwegianTranslation|Norwegian]] - maintainer: Gaute Jao (Gauteamus) - [mailto:gauteamusATgmailDOTcom]
* [[OccitanTranslation|Occitan]] - maintainer: Nobody, currently
* [[PolishTranslation|Polish]] - maintainer: Zbigniew Banach - [mailto:zDOTbanachATwsisizDOTeduDOTpl]
* [[PortugueseTranslation|Portuguese Brazilian]] - maintainer: Claus Aranha (caranha) - [mailto:caranhaATgmailDOTcom]
* [[PortugueseContinentalTranslation|Portuguese Continental(pt_PT)]] - maintainer: Sérgio Lopes [mailto:knitter.is@gmail.com]
* [[RussianTranslation|Russian]] - maintainer: Victor Zabavin [mailto:viczaATzmailDOTru]
* [[SerbianTranslation|Serbian]] - maintainer: Srećko Toroman (freecraft)- [mailto:sreckotoromanATgmailDOTcom]
* [[(sk) Preklad|Slovak]] - maintainer: Viliam Bur - [mailto:viliamATburDOTsk]; wiki: [[(sk) Návod]]
* [[SlovenianTranslation|Slovenian]] - maintainer: Jaka Kranjc (lynx) - [mailto:lynxlupodianAThotmailDOTcom]
* [[SpanishTranslation|Spanish]] - maintainer: Sergi March [mailto:sergiPUNTOmarchENgmail.com]
* [[SwedishTranslation|Swedish]] - maintainer: Gustav Tiger (Tigge) - [mailto:adminATtiggeDOTorg]
* [[TurkishTranslation|Turkish]] - maintainer: Nilgün Belma Bugüner - [mailto:nilgunATbelgelerDOTgenDOTtr]
* [[Wesnoth-in-Valencian|Valencian]] - maintainer: Mario (Mavorte) - [mailto:mavorte1ATyahooDOTes]
* [[VietnameseTranslation|Vietnamese]] - maintainer: Do Hong Minh - [mailto:minhdhAThutticDOTcom]

Other ideas (remember, these are just ideas):
* Translations into Asian languages
** Asian languages are already supported. See [[WesnothAsianLanguages]].

== Mailing List ==

There now is a mailinglist dedicated to translation matters. It is mainly intended to be used for informing translation maintainers about important changes, to announce string freezes and other special things. Everyone is free to subscribe to this list. You can find this list, entitled wesnoth-i18n at the listing of all Wesnoth mailing lists:

[http://gna.org/mail/?group=wesnoth http://gna.org/mail/?group=wesnoth]

The archive for this list is to be found [http://mail.gna.org/public/wesnoth-i18n/ here].
Please keep in mind that this list is not meant for discussing changes for one single translation but stuff that is relevant to all translations.

== See also ==

* [[WesnothTranslationsHowTo]]
* [[GetText]]
* [http://gettext.wesnoth.org Translations statistics (stable)]
* [http://gettext.wesnoth.org/index.php?version=trunk&package=alloff Translations statistics (development)]
* [[WesCamp| Translating User made Campaigns (featuring WesCamp-i18n)]]
* [[SpellingMistakes]]

[[Category:Translations|*]]

SideWML

2008-05-18T10:29:16Z

Noyga: /* the [side] tag */

{{WML Tags}}
== the [side] tag ==

The [side] tag is used to describe a side in a particular scenario.

The following keys are recognized:

* '''side''': a digit. The leader of this side is placed on the tile represented by this digit (see [[BuildingMaps]]). When defining sides, they must be defined in order since the side number is checked against the number of sides seen so far.

* '''controller''': how moves for this side should be inputted.
** '''ai''': the Wesnoth AI makes this side's moves. This is the default setting.
** '''human''': a player controls this side's moves.
** '''null''': the side doesn't get a turn to move and doesn't have a leader generated from the contents of the [side] tag. (It still can get units from [unit] tags in the [side] tag.)

* '''no_leader''': if "no" (default), then keys describing a unit which will begin on the side's keep will be the remainder of the '''[side]''' tag, See [[SingleUnitWML]]. Note that if the keys '''x''', '''y''' are included, the leader will begin there regardless of keep location. If this side has a recall list from a previous level, then the recall list will be searched for a leader (using '''canrecruit=yes''') and if one is found it will be used instead of the one described in the '''[side]''' tag. Typical keys used for defining the leader unit are '''type''' (mandatory), '''description''', '''id''' {{DevFeature}}, '''user_description''', '''name''' {{DevFeature}} and '''unrenamable=yes''', see [[UnitWML]].

* '''recruit''': a list of unit types. At the beginning of the scenario, the side gains recruitment of these units.

* '''gold''': the starting gold for this side. Default 100. (If gold is carried over from a previous scenario, this value is the minimum starting gold.)

* '''income''': the base income for this side, default 0. This is added to ''base_income'', '''[game_config]''' to determine the side's base income. (see [[GameConfigWML]]).

* '''fog''': if 'yes', this side cannot see any tiles it is not within vision of, except at the start.

* '''shroud''': if 'yes', this side cannot see any tiles it has not moved within sight of.

* '''shroud_data''': describes the area which this team has de-shrouded. An example:
|
|00011111000
This would leave the first column on the map unaltered and would change the second column for 11 tiles. A '0' means: shrouded, '1' means unshrouded. You can either call an external file using {@filename} (see [[PreprocessorRef]]) or place the data in quotes. For making an external file see [[BuildingScenariosShroudData]].

* '''persistent''': whether the side exists in any other scenarios. If '1'(yes), then ''save_id''(see below) becomes active for this side. Default '0'(no); when '''controller=human''', this is always '1'.

* '''save_id''': default ''description'' if available, 'Unknown' otherwise. The ID of the side with respect to the previous and next scenarios. Used to carry over the side's recall list (including the side's leader), recruitment list, and starting gold from scenario to scenario. Also used for the side's displayed name in the victory gold-calculation dialog.

* '''team_name''': a non translatable string representing the team's description. Sides with the same team_name are allied. Default ''side''.

* '''user_team_name''': a translatable string representing the team's description. This has no effect on alliances. Default ''team_name''.

* '''colour''': May be either a numeric color index or a color name (e.g. 'blue', 'purple', 'orange', etc.). The numeric form is deprecated. The default list of numbers and corresponding colours can be found in data/core/team_colors.cfg.

* '''flag''': a custom flag animation to use instead of the default one to mark captured villages. An automatic side-coloring is applied.
** Example animation that has three frames and loops every 750ms: ''flag=misc/myflag-1.png:250,misc/myflag-2.png:250,misc/myflag-3.png:250''

* '''flag_icon''': a custom flag icon to indicate the side playing in the statusbar (a size of 24x16 is recommended). An automatic side-coloring is applied.

* '''village_gold''': the amount of gold given to this side per village it controls per turn. Default specified in ''village_income'', '''[game_config]''' ([[GameConfigWML]]). '''Note:''' If you need village gold to be 0. Set the variable to -1.

* '''share_maps''': whether sides allied with this side see all terrains that this side sees, if they are on shroud.

* '''share_view''': whether sides allied with this side see the units that this side sees, if they are on FoW (fog).

* '''disallow_observers''': prevents observers from seeing this side turn. (default: no)

* '''name''', '''id''', '''leader''': not used; see [[EraWML]].

* ''music'' music to play for this player. Default specified in [scenario] (see [[ScenarioWML]]).

* '''[ai]''' if '''controller=ai''', gives parameters to the AI. See [[AiWML]].

* '''[village]''' describes a village the side begins in control of.
** ''x'', ''y'' the location of the village.

* '''[unit]''' describes a unit which begins on the side. See [[SingleUnitWML]]. If the side has a recall list and the unit is not given a location, it will start on the recall list. Note that the ''side'' attribute under '''[unit]''' will be ignored, as the side will come from the ''side'' attribute of '''[side]'''.

The following keys are multiplayer only:

* '''allow_player''': if false then this side will not be allowed to be modified and will be hidden during game creation.

* '''team_lock''': if true then this side's team is not allowed to be modified.

* '''colour_lock''': if true then this side's color is not allowed to be modified.

* '''gold_lock''': if true then this side's gold is not allowed to be modified.

* '''income_lock''': if true then this side's income is not allowed to be modified.

* '''faction''': this lock this side to this faction.

* '''faction_from_recruit''' {{DevFeature}}: if true then this side will be locked to the faction that matches the recruits better. (this was enabled by default in 1.4)

== See Also ==
* [[EraWML]]
* [[ScenarioWML]]
* [[ReferenceWML]]

[[Category: WML Reference]]

InternalActionsWML

2008-04-03T22:26:17Z

Noyga: /* [event] */

{{WML Tags}}
== Internal actions ==

Internal actions are actions that WML uses internally that do not directly affect gameplay, for example storing a variable.

The internal actions '''[if]''', '''[while]''', and '''[event]''' describe when/whether sets of actions should be executed.

== [if] ==

Executes different sets of actions based on whether the conditions described in the condition tags are true or not.

Condition tags:
* '''[have_unit]''': a unit passing this filter with >0 HP exists
** [[StandardUnitFilter]] (almost... '''Note:''' does not check for matching units in the recall list)

* '''[have_location]''': a location passing this filter exists
** [[StandardLocationFilter]]

* '''[and]''': If an [and] is present, all must evaluate to true in order for the [if] to evaluate true. Useful as a bracket for complex conditions, but not strictly necessary.
** condition tags as in [if]: if these evaluate to true, [and] evaluates to true.

* '''[or]''': If an [or] is present, one must evaluate to true in order for the [if] to evaluate true. ([[AdvancedConditionalWML|Example]])
** condition tags as in [if]: if these evaluate to true, '''[or]''' evaluates to true.

* '''[not]''': If a [not] is present, none must evaluate to true in order for the [if] to evaluate true.
** condition tags as in [if]: if these evaluate to true, [not] evaluates to false.

* '''[and],[or],[not]''': all top-level filters will support in-order conditional handling of and, or, and not. One important thing to remember is, if you have multiple [or]s, you should not wrap your first conditional statement into an [or] block.

* '''[variable]''': tests something about the value of a WML variable (see [[VariablesWML]])
** '''name''': the name of the variable to test the value of Only one of the following keys should be used for comparing the value of the variable to another value:
** '''equals''': $name is equal (string wise) to this
** '''not_equals''': $name is not equal to this
** '''greater_than''': $name is numerically greater than this
** '''less_than''': $name is less than this
** '''greater_than_equal_to''': $name is not less than this
** '''less_than_equal_to''': $name is not greater than this
** '''numerical_not_equals''': $name is greater than or less than this
** '''numerical_equals''': $name is not greater than or less than this
** '''boolean_equals''': $name has the same boolean value (e.g. off, false, 0, no)
** '''contains''': $name contains this string
** {{DevFeature}} '''boolean_not_equals''': $name has not the same boolean value. Strictly a syntactic shortcut for the following syntax that served its absence in 1.4:
[not]
[variable]
name=...
boolean_equals=...
[/variable]
[/not]

After condition tags:
* '''[then]''': contains a set of action tags which should be executed if all conditions are true, or all conditions in any single [or] are true
* '''[else]''': contains a set of action tags which should be executed if any condition is false, and all [or] tags are false

== [switch] {{DevFeature}} ==

Executes different sets of action based on the value of a variable.
[switch]
variable=foo
[case]
value="A"
... WML if foo=A ...
[/case]
[case]
value="B"
... WML if foo=B ...
[/case]
[else]
... WML if not foo=A nor foo=B ...
[/else]
[/switch]

* '''variable''': name of the variable to check.
* '''[case]''': Case block. Contains:
** '''value''': value to test the variable against.
** the action WML to execute if the variable matches the value (rest of the block).
* '''[else]''': Block of action WML to execute if no '''[case]''' block matches.

== [while] ==

Executes commands if all conditions are true.
Continues to execute them until a condition is not true.

Executes a maximum of 1024 iterations per invocation.
Condition tags are the same as for [if]

After condition tags:
* '''[do]''': contains actions that should be executed repeatedly until some condition is false.

The '''[while]''' tag is useful for iterating over an array.
An array is a list of values.
The ''number''th value in the array '''array''' is stored in the WML variable '''''array''[number]'''.
Note that if '''number''' is the value of the variable '''variable''',
the expression '''$''array''[$variable]''' will return the ''number''th value in ''array''.
The macros 'FOREACH' and 'NEXT' ([[UtilWML]]) can be used to iterate over an array;
i.e. run a set of actions once per element of the array.

=== {FOREACH} ===
If you wish to use a "for-each" iteration format (useful for example when you want to do an iteration for each row in a table) you can use the [http://www.wesnoth.org/macro-reference.xhtml FOREACH] and [http://www.wesnoth.org/macro-reference.xhtml NEXT] prededined macros.

=== {REPEAT} ===
You can use the REPEAT macro to perform a quick iteration for a number of times you specify.

== [event] ==

This adds a new event to the scenario.
The event is in the normal format for an '''[event]''' tag (See [[EventWML]]).
This is useful if you want an event that can only be triggered when a prior event is fulfilled

These tags describe actions that affect the values of WML variables
(see [[VariablesWML]] for information on WML variables,
and [[UtilWML]] for convenient macro shortcuts for some of these):
* '''[set_variable]''': manipulates a WML variable. {{Note:Predefined Macro|VARIABLE}}
** '''name''': the name of the variable to manipulate
** '''value''': set the variable to the given value (can be numeric or string). This only interprets dollars signs if it is the very first character, and then the entire value must be a simple variable name. (in 1.3.2, has the same effect as format. Use literal for no substitution)
** '''literal''': set the variable to the given value (can be numeric or string). This does not interpret any dollars signs.
** '''format''': set the variable to the given value. Interprets the dollar sign to a higher degree than most actions. (see [[VariablesWML]])
** '''to_variable''': Fully processes its value as in ''format'', and then gets the variable with that name.
** '''add''': add the given amount to the variable. To subtract, add a negative number.
** '''multiply''': multiply the variable by the given number. To divide, multiply by the inverse eg: 4/2 = 4 * 1/2 = 4 * 0.5. To negate, multiply by -1. The result is an integer.
** '''divide''': divide the variable by the given number. The result is an integer.
** '''modulo''': returns the remainder of an integer division. Both variables need to be an integer, the result is also an integer. eg 5 % 2 = 1.
** '''random''': the variable will be randomly set. You may provide a comma separated list of possibilities, e.g. 'random=Bob,Bill,Bella'. You may provide a range of numbers (integers), e.g. 'random=3..5'. You may combine these, e.g. 'random=100,1..9', in which case there would be 1/10th chance of getting 100, just like for each of 1 to 9. Dollars signs are only normally interpreted here, so it is harder to have a dynamically determined range. You would need to create the random-string with ''format''.
** '''rand''': does the same as random, but has better MP support. See [[BuildingMultiplayerExamples]] for more info on the MP case. '''It is highly recommended that you use this feature for randomization.'''
** '''time=stamp''': Retrieves a timestamp in milliseconds since wesnoth was started, can be used as timing aid. Don't try to use this as random value in MP since it will cause an OOS.
** {{DevFeature}} '''string_length''': Retrieves the length in characters of the string passed as this attribute's value; such string is parsed and variable substitution applied automatically (see [[VariablesWML]] for details).
** {{DevFeature}} '''[join]''' joins an array of strings to a textual list
***variable: name of the array
***key: array[$i].key to look for the strings
***separator: separator to connect the elements
***remove_empty: wether to ignore empty elements

* {{DevFeature}} '''[set_variables]''': manipulates a WML array
** '''name''': the name of the container to manipulate
** '''mode''': one of the following values:
***replace: will clean the array '''name''' and replace it with given data
***append: will append given data to the current array
***merge: will merge in the given data into '''name'''
** '''to_variable''': data will be set to the given array
** '''[value]''': the WML inside the [value] tags will be stored in data, variables will be interpolated directly, use $| in order to escape the $ sign, you can store arrays of WML by supplying multiple [value] tags, example:
[set_variables]
name=arr
mode=replace
[value]
foo=bar
[/value]
[value]
foo=more
[/value]
[/set_variables]
{DEBUG_MSG $arr[0].foo}
{DEBUG_MSG $arr[1].foo}
=>bar; more
** '''[literal]''': same as '''[value]''', but variables will not be substituted, '''[literal]''' and '''[value]''' can not be used in the same [set_variables] tag, i.e. you can not create arrays by piling a mix of '''[value]''' and '''[literal]''' tags
**'''[split]''' splits a textual list into an array which will then be set to data
***list: textual list to split
***key: array[$i].key to put the elements in
***separator: separator to separate the elements
***remove_empty: wether to ignore empty elements

* {{DevFeature}} '''[fire_event]''': trigger a WML event
** '''name''': the name of event to trigger
** '''[primary_unit]''': primary unit for the event (usually the attacker) (optional)
** '''[secondary_unit]''': secondary unit for the event (usually the defender) (optional)
** both tags have some keys which are optional :
*** '''x,y''': location of this unit
*** '''weapon''': weapon that this unit was supposed to use for this event

* '''[store_unit]''': stores details about units into game variables. Common usage is to manipulate a unit by using [store_unit] to store it into a variable, followed by manipulation of the variable, and then [unstore_unit] to re-create the unit with the modified variables. Note: stored units also exist on the field, and modifying the stored variable will not automatically change the stats of the units. You need to use [unstore_unit]. See also [unstore_unit], [[DirectActionsWML]], and '''FOREACH''', [[UtilWML]]
** '''[filter]''': [[StandardUnitFilter]] all units matching this filter will be stored. If there are multiple units, they will be stored into an array of variables.
** '''variable''': the name of the variable into which to store the unit(s)
** '''mode''': defaults to ''always_clear'', which clears the variable, whether or not a match is found. If mode is set to ''replace'', the variable will only be cleared if a match is found. If mode is set to ''append'', the variable will not be cleared.
** '''kill''': if 'yes' the units that are stored will be removed from play. This is useful for instance to remove access to a player's recall list, with the intent to restore the recall list later.
:When a unit is stored, the following values may be manipulated with '''[set_variable]'''
:* description
:* experience
:* facing
:* gender
:* canrecruit
:* overlays
:* goto_x
:* goto_y
:* hitpoints
:* moves
:* resting
:* side
:* type
:* unrenamable
:* upkeep
:* user_description
:* x
:* y
:* [variables]
:* [status]
:* [modifications]
Variables, status, and modifications are children of the stored unit variable. Example:
[set_variable]
name=unit_store.status.poisoned
value=yes
[/set_variable]

:All keys and tags in the unit definition may be manipulated, including some others. Here is a sample list. If you have a doubt about what keys are valid or what the valid value range is for each key, code a [store_unit] event, save the game, and examine what keys are in the file.
:* advanceto
:* alignment
:* alpha
:* attacks_left
:* canrecruit
:* controller
:* cost
:* description
:* experience
:* facing
:* flying
:* fog
:* gender
:* get_hit_sound
:* gold
:* goto_x
:* goto_y
:* hitpoints
:* id
:* image
:* image_defensive
:* income
:* language_name (same as the name key in the unit config)
:* level
:* max_attacks
:* max_experience
:* max_hitpoints
:* max_moves
:* movement
:* movement_type
:* moves
:* race
:* resting
:* shroud
:* side
:* team_name
:* type
:* unit_description
:* unrenamable
:* usage
:* value
:* x
:* y
:* zoc
:* [advancement]
:* [/advancement]
:* [movement_costs]
:* [/movement_costs]
:* [defense]
:* [/defense]
:* [resistance]
:* [/resistance]
:* [variables]
:* [/variables]
:* [status]
:* [/status]
:* [attack]
:* [/attack]
:* [modifications_description]
:* [/modifications_description]
:* [modifications]
:* [/modifications]

* '''[store_starting_location]''': Stores the starting location of a side's leader in a variable. The variable is a composite type which will have members 'x', 'y', 'terrain' (the terrain type for a starting location is always 'K' unless it has been changed) and {{DevFeature}} 'owner_side' (villages only)
** '''side''': the side whose starting location is to be stored
** '''variable''': (default='location'): the name of the variable to store the location in
* '''[store_locations]''': Stores a series of locations that pass certain criteria into an array. Each member of the array has members 'x' and 'y' (the position) and 'terrain' (the terrain type) and {{DevFeature}} 'owner_side' (villages only).
** [[StandardLocationFilter]]: a location or location range which specifies the locations to store. You must specify this or no locations will be stored.
** '''variable''': the name of the variable (array) into which to store the locations
** '''terrain''': a comma-sperated list of terrain codes. (See [[TerrainCodesWML]] for possible values.) If present, locations will only be chosen if the code for the terrain type of that location is listed.
** '''radius''': if present, any locations which are within '''radius''' hexes of the location filter will also be stored
** '''[filter]''': [[StandardUnitFilter]] only locations with units on them that match the filter will be stored. Use a blank filter to only store locations with units.
* '''[store_villages]''': Stores a series of locations of villages that pass certain criteria into an array. Each member of the array has members 'x' and 'y' (the position) and 'terrain' (the terrain type) and {{DevFeature}} 'owner_side'.
** '''owner_side''': a side number. If present, only villages owned by this side will be choosen. If owner_side=0, store the unowned villages.
** '''variable''': the name of the variable (array) into which to store the locations
** '''terrain''': a series of terrain characters. (See [[TerrainLettersWML]] for possible values.) If present, villages will only be chosen if the terrain code of the terrain type of that location is listed. You may give a comma separated list of terrains.
** '''side''': (default=1) the side for which the gold should be stored
** '''variable''': (default='gold') the name of the variable to store the gold in
* '''[store_side]''': stores information about a certain side in a variable. The variable will contain the member variables 'name', 'team_name', 'gold' and 'income', 'fog', 'shroud', 'user_team_name', 'colour', 'controller', 'village_gold' and 'recruit'.)
** '''side''': the side whose information should be stored
** '''variable''': the name of the variable to store the information in
* '''[clear_variable]''': This will delete the given variable or array. This is good to use to clean up the set of variables -- e.g. a well-behaved scenario will delete any variables that shouldn't be kept for the next scenario before the end of the scenario. Tags and variables of stored units can also be cleared, meaning that [trait]s and [object]s, for example, can be removed.
** '''name''': the name of the variable to clear.
* '''[role]''': tries to find a unit to assign a role to. This is useful if you want to choose a non-major character to say some things during the game. Once a role is assigned, you can use '''role=''' in a unit filter to identify the unit with that role (See [[FilterWML]]). However, there is no guarantee that roles will ever be assigned. You can use '''[have_unit]''' (see [if]) to see whether a role was assigned. This tag uses a [[StandardUnitFilter]] with the modification to order the search by type, mark only the first unit found with the role, and the role attribute is not used in the search. If for some reason you want to search for units that have or don't have existing roles, you can use one or more [not] filters. The will check recall lists in addition to units on the map. In normal use, you will probably want to include a ''side'' attribute to force the unit to be on a particular side.
** '''role''': the value to store as the unit's role. This role is not used in the [[StandardUnitFilter]] when doing the search for the unit to assign this role to.
** '''type''': a comma-separated list of possible types the unit can be. If any types are given, then units will be searched by type in the order listed. If no type is given, then no particular order with respect to type is guaranteed.
* {{DevFeature}} '''[store_map_dimensions]''': Stores the map dimensions in a variable.
** '''variable''': the name of the variable where the values will be saved into. If it is skipped, a variable 'map_size' is used, and its contents overridden, if they existed already. The result is a container variable, with members ''width'' and ''height''.

== See Also ==
* [[VariablesWML]]
* [[DirectActionsWML]]
* [[InterfaceActionsWML]]
* [[EventWML]]
* [[ReferenceWML]]

[[Category: WML Reference]]

InternalActionsWML

2008-04-03T22:23:59Z

Noyga: /* [event] */

{{WML Tags}}
== Internal actions ==

Internal actions are actions that WML uses internally that do not directly affect gameplay, for example storing a variable.

The internal actions '''[if]''', '''[while]''', and '''[event]''' describe when/whether sets of actions should be executed.

== [if] ==

Executes different sets of actions based on whether the conditions described in the condition tags are true or not.

Condition tags:
* '''[have_unit]''': a unit passing this filter with >0 HP exists
** [[StandardUnitFilter]] (almost... '''Note:''' does not check for matching units in the recall list)

* '''[have_location]''': a location passing this filter exists
** [[StandardLocationFilter]]

* '''[and]''': If an [and] is present, all must evaluate to true in order for the [if] to evaluate true. Useful as a bracket for complex conditions, but not strictly necessary.
** condition tags as in [if]: if these evaluate to true, [and] evaluates to true.

* '''[or]''': If an [or] is present, one must evaluate to true in order for the [if] to evaluate true. ([[AdvancedConditionalWML|Example]])
** condition tags as in [if]: if these evaluate to true, '''[or]''' evaluates to true.

* '''[not]''': If a [not] is present, none must evaluate to true in order for the [if] to evaluate true.
** condition tags as in [if]: if these evaluate to true, [not] evaluates to false.

* '''[and],[or],[not]''': all top-level filters will support in-order conditional handling of and, or, and not. One important thing to remember is, if you have multiple [or]s, you should not wrap your first conditional statement into an [or] block.

* '''[variable]''': tests something about the value of a WML variable (see [[VariablesWML]])
** '''name''': the name of the variable to test the value of Only one of the following keys should be used for comparing the value of the variable to another value:
** '''equals''': $name is equal (string wise) to this
** '''not_equals''': $name is not equal to this
** '''greater_than''': $name is numerically greater than this
** '''less_than''': $name is less than this
** '''greater_than_equal_to''': $name is not less than this
** '''less_than_equal_to''': $name is not greater than this
** '''numerical_not_equals''': $name is greater than or less than this
** '''numerical_equals''': $name is not greater than or less than this
** '''boolean_equals''': $name has the same boolean value (e.g. off, false, 0, no)
** '''contains''': $name contains this string
** {{DevFeature}} '''boolean_not_equals''': $name has not the same boolean value. Strictly a syntactic shortcut for the following syntax that served its absence in 1.4:
[not]
[variable]
name=...
boolean_equals=...
[/variable]
[/not]

After condition tags:
* '''[then]''': contains a set of action tags which should be executed if all conditions are true, or all conditions in any single [or] are true
* '''[else]''': contains a set of action tags which should be executed if any condition is false, and all [or] tags are false

== [switch] {{DevFeature}} ==

Executes different sets of action based on the value of a variable.
[switch]
variable=foo
[case]
value="A"
... WML if foo=A ...
[/case]
[case]
value="B"
... WML if foo=B ...
[/case]
[else]
... WML if not foo=A nor foo=B ...
[/else]
[/switch]

* '''variable''': name of the variable to check.
* '''[case]''': Case block. Contains:
** '''value''': value to test the variable against.
** the action WML to execute if the variable matches the value (rest of the block).
* '''[else]''': Block of action WML to execute if no '''[case]''' block matches.

== [while] ==

Executes commands if all conditions are true.
Continues to execute them until a condition is not true.

Executes a maximum of 1024 iterations per invocation.
Condition tags are the same as for [if]

After condition tags:
* '''[do]''': contains actions that should be executed repeatedly until some condition is false.

The '''[while]''' tag is useful for iterating over an array.
An array is a list of values.
The ''number''th value in the array '''array''' is stored in the WML variable '''''array''[number]'''.
Note that if '''number''' is the value of the variable '''variable''',
the expression '''$''array''[$variable]''' will return the ''number''th value in ''array''.
The macros 'FOREACH' and 'NEXT' ([[UtilWML]]) can be used to iterate over an array;
i.e. run a set of actions once per element of the array.

=== {FOREACH} ===
If you wish to use a "for-each" iteration format (useful for example when you want to do an iteration for each row in a table) you can use the [http://www.wesnoth.org/macro-reference.xhtml FOREACH] and [http://www.wesnoth.org/macro-reference.xhtml NEXT] prededined macros.

=== {REPEAT} ===
You can use the REPEAT macro to perform a quick iteration for a number of times you specify.

== [event] ==

This adds a new event to the scenario.
The event is in the normal format for an '''[event]''' tag (See [[EventWML]]).
This is useful if you want an event that can only be triggered when a prior event is fulfilled

These tags describe actions that affect the values of WML variables
(see [[VariablesWML]] for information on WML variables,
and [[UtilWML]] for convenient macro shortcuts for some of these):
* '''[set_variable]''': manipulates a WML variable. {{Note:Predefined Macro|VARIABLE}}
** '''name''': the name of the variable to manipulate
** '''value''': set the variable to the given value (can be numeric or string). This only interprets dollars signs if it is the very first character, and then the entire value must be a simple variable name. (in 1.3.2, has the same effect as format. Use literal for no substitution)
** '''literal''': set the variable to the given value (can be numeric or string). This does not interpret any dollars signs.
** '''format''': set the variable to the given value. Interprets the dollar sign to a higher degree than most actions. (see [[VariablesWML]])
** '''to_variable''': Fully processes its value as in ''format'', and then gets the variable with that name.
** '''add''': add the given amount to the variable. To subtract, add a negative number.
** '''multiply''': multiply the variable by the given number. To divide, multiply by the inverse eg: 4/2 = 4 * 1/2 = 4 * 0.5. To negate, multiply by -1. The result is an integer.
** '''divide''': divide the variable by the given number. The result is an integer.
** '''modulo''': returns the remainder of an integer division. Both variables need to be an integer, the result is also an integer. eg 5 % 2 = 1.
** '''random''': the variable will be randomly set. You may provide a comma separated list of possibilities, e.g. 'random=Bob,Bill,Bella'. You may provide a range of numbers (integers), e.g. 'random=3..5'. You may combine these, e.g. 'random=100,1..9', in which case there would be 1/10th chance of getting 100, just like for each of 1 to 9. Dollars signs are only normally interpreted here, so it is harder to have a dynamically determined range. You would need to create the random-string with ''format''.
** '''rand''': does the same as random, but has better MP support. See [[BuildingMultiplayerExamples]] for more info on the MP case. '''It is highly recommended that you use this feature for randomization.'''
** '''time=stamp''': Retrieves a timestamp in milliseconds since wesnoth was started, can be used as timing aid. Don't try to use this as random value in MP since it will cause an OOS.
** {{DevFeature}} '''string_length''': Retrieves the length in characters of the string passed as this attribute's value; such string is parsed and variable substitution applied automatically (see [[VariablesWML]] for details).
** {{DevFeature}} '''[join]''' joins an array of strings to a textual list
***variable: name of the array
***key: array[$i].key to look for the strings
***separator: separator to connect the elements
***remove_empty: wether to ignore empty elements

* {{DevFeature}} '''[set_variables]''': manipulates a WML array
** '''name''': the name of the container to manipulate
** '''mode''': one of the following values:
***replace: will clean the array '''name''' and replace it with given data
***append: will append given data to the current array
***merge: will merge in the given data into '''name'''
** '''to_variable''': data will be set to the given array
** '''[value]''': the WML inside the [value] tags will be stored in data, variables will be interpolated directly, use $| in order to escape the $ sign, you can store arrays of WML by supplying multiple [value] tags, example:
[set_variables]
name=arr
mode=replace
[value]
foo=bar
[/value]
[value]
foo=more
[/value]
[/set_variables]
{DEBUG_MSG $arr[0].foo}
{DEBUG_MSG $arr[1].foo}
=>bar; more
** '''[literal]''': same as '''[value]''', but variables will not be substituted, '''[literal]''' and '''[value]''' can not be used in the same [set_variables] tag, i.e. you can not create arrays by piling a mix of '''[value]''' and '''[literal]''' tags
**'''[split]''' splits a textual list into an array which will then be set to data
***list: textual list to split
***key: array[$i].key to put the elements in
***separator: separator to separate the elements
***remove_empty: wether to ignore empty elements

* {{DevFeature}} '''[fire_event]''': trigger a WML event
** '''name''': the name of event to trigger
** '''[primary_unit]''': primary unit for the event (usually the attacker) (optional)
** '''[secondary_unit]''': secondary unit for the event (usually the defender) (optional)
** both tags have some keys which are optional :
*** '''x,y''': location of this unit
*** '''weapon''': weapon that this unit was supposed to use for this event

* '''[store_unit]''': stores details about units into game variables. Common usage is to manipulate a unit by using [store_unit] to store it into a variable, followed by manipulation of the variable, and then [unstore_unit] to re-create the unit with the modified variables. Note: stored units also exist on the field, and modifying the stored variable will not automatically change the stats of the units. You need to use [unstore_unit]. See also [unstore_unit], [[DirectActionsWML]], and '''FOREACH''', [[UtilWML]]
** '''[filter]''': [[StandardUnitFilter]] all units matching this filter will be stored. If there are multiple units, they will be stored into an array of variables.
** '''variable''': the name of the variable into which to store the unit(s)
** '''mode''': defaults to ''always_clear'', which clears the variable, whether or not a match is found. If mode is set to ''replace'', the variable will only be cleared if a match is found. If mode is set to ''append'', the variable will not be cleared.
** '''kill''': if 'yes' the units that are stored will be removed from play. This is useful for instance to remove access to a player's recall list, with the intent to restore the recall list later.
:When a unit is stored, the following values may be manipulated with '''[set_variable]'''
:* description
:* experience
:* facing
:* gender
:* canrecruit
:* overlays
:* goto_x
:* goto_y
:* hitpoints
:* moves
:* resting
:* side
:* type
:* unrenamable
:* upkeep
:* user_description
:* x
:* y
:* [variables]
:* [status]
:* [modifications]
Variables, status, and modifications are children of the stored unit variable. Example:
[set_variable]
name=unit_store.status.poisoned
value=yes
[/set_variable]

:All keys and tags in the unit definition may be manipulated, including some others. Here is a sample list. If you have a doubt about what keys are valid or what the valid value range is for each key, code a [store_unit] event, save the game, and examine what keys are in the file.
:* advanceto
:* alignment
:* alpha
:* attacks_left
:* canrecruit
:* controller
:* cost
:* description
:* experience
:* facing
:* flying
:* fog
:* gender
:* get_hit_sound
:* gold
:* goto_x
:* goto_y
:* hitpoints
:* id
:* image
:* image_defensive
:* income
:* language_name (same as the name key in the unit config)
:* level
:* max_attacks
:* max_experience
:* max_hitpoints
:* max_moves
:* movement
:* movement_type
:* moves
:* race
:* resting
:* shroud
:* side
:* team_name
:* type
:* unit_description
:* unrenamable
:* usage
:* value
:* x
:* y
:* zoc
:* [advancement]
:* [/advancement]
:* [movement_costs]
:* [/movement_costs]
:* [defense]
:* [/defense]
:* [resistance]
:* [/resistance]
:* [variables]
:* [/variables]
:* [status]
:* [/status]
:* [attack]
:* [/attack]
:* [modifications_description]
:* [/modifications_description]
:* [modifications]
:* [/modifications]

* '''[store_starting_location]''': Stores the starting location of a side's leader in a variable. The variable is a composite type which will have members 'x', 'y', 'terrain' (the terrain type for a starting location is always 'K' unless it has been changed) and {{DevFeature}} 'owner_side' (villages only)
** '''side''': the side whose starting location is to be stored
** '''variable''': (default='location'): the name of the variable to store the location in
* '''[store_locations]''': Stores a series of locations that pass certain criteria into an array. Each member of the array has members 'x' and 'y' (the position) and 'terrain' (the terrain type) and {{DevFeature}} 'owner_side' (villages only).
** [[StandardLocationFilter]]: a location or location range which specifies the locations to store. You must specify this or no locations will be stored.
** '''variable''': the name of the variable (array) into which to store the locations
** '''terrain''': a comma-sperated list of terrain codes. (See [[TerrainCodesWML]] for possible values.) If present, locations will only be chosen if the code for the terrain type of that location is listed.
** '''radius''': if present, any locations which are within '''radius''' hexes of the location filter will also be stored
** '''[filter]''': [[StandardUnitFilter]] only locations with units on them that match the filter will be stored. Use a blank filter to only store locations with units.
* '''[store_villages]''': Stores a series of locations of villages that pass certain criteria into an array. Each member of the array has members 'x' and 'y' (the position) and 'terrain' (the terrain type) and {{DevFeature}} 'owner_side' (villages only).
** '''owner_side''': a side number. If present, only villages owned by this side will be choosen. If owner_side=0, store the unowned villages.
** '''variable''': the name of the variable (array) into which to store the locations
** '''terrain''': a series of terrain characters. (See [[TerrainLettersWML]] for possible values.) If present, villages will only be chosen if the terrain code of the terrain type of that location is listed. You may give a comma separated list of terrains.
** '''side''': (default=1) the side for which the gold should be stored
** '''variable''': (default='gold') the name of the variable to store the gold in
* '''[store_side]''': stores information about a certain side in a variable. The variable will contain the member variables 'name', 'team_name', 'gold' and 'income', 'fog', 'shroud', 'user_team_name', 'colour', 'controller', 'village_gold' and 'recruit'.)
** '''side''': the side whose information should be stored
** '''variable''': the name of the variable to store the information in
* '''[clear_variable]''': This will delete the given variable or array. This is good to use to clean up the set of variables -- e.g. a well-behaved scenario will delete any variables that shouldn't be kept for the next scenario before the end of the scenario. Tags and variables of stored units can also be cleared, meaning that [trait]s and [object]s, for example, can be removed.
** '''name''': the name of the variable to clear.
* '''[role]''': tries to find a unit to assign a role to. This is useful if you want to choose a non-major character to say some things during the game. Once a role is assigned, you can use '''role=''' in a unit filter to identify the unit with that role (See [[FilterWML]]). However, there is no guarantee that roles will ever be assigned. You can use '''[have_unit]''' (see [if]) to see whether a role was assigned. This tag uses a [[StandardUnitFilter]] with the modification to order the search by type, mark only the first unit found with the role, and the role attribute is not used in the search. If for some reason you want to search for units that have or don't have existing roles, you can use one or more [not] filters. The will check recall lists in addition to units on the map. In normal use, you will probably want to include a ''side'' attribute to force the unit to be on a particular side.
** '''role''': the value to store as the unit's role. This role is not used in the [[StandardUnitFilter]] when doing the search for the unit to assign this role to.
** '''type''': a comma-separated list of possible types the unit can be. If any types are given, then units will be searched by type in the order listed. If no type is given, then no particular order with respect to type is guaranteed.
* {{DevFeature}} '''[store_map_dimensions]''': Stores the map dimensions in a variable.
** '''variable''': the name of the variable where the values will be saved into. If it is skipped, a variable 'map_size' is used, and its contents overridden, if they existed already. The result is a container variable, with members ''width'' and ''height''.

== See Also ==
* [[VariablesWML]]
* [[DirectActionsWML]]
* [[InterfaceActionsWML]]
* [[EventWML]]
* [[ReferenceWML]]

[[Category: WML Reference]]

EventWML

2008-03-28T01:02:01Z

Noyga: /* The [event] tag */

{{WML Tags}}
== The [event] tag ==

This tag is a subtag of [scenario] (or [unit] - see '''event''', [[UnitWML]]) which is used to describe a set of actions
which trigger at a certain point in the scenario.

Keys and tags that describe when the event should trigger:
* '''name''': this is not like a normal 'name' key. It is a basic description of when the event will trigger.
* '''prestart''': the event is triggered before a scenario 'starts' -- before anything is shown on the screen at all. You can use this event to set up things like village ownership. For things displayed on-screen such as character dialog, use '''start'''.
* '''start''': this event triggers after the map is shown but before the scenario begins
* '''new turn''': this event triggers whenever the last player ends their turn. See also '''first_time_only=no'''. When the last player ends their turn, before any events of this type trigger, the value of the WML variable '''turn_number''' is set to the number of the turn that is beginning.
* '''side turn''': this event triggers when a side is about to start its turn. Before events of this type trigger, the value of the WML variable '''side_number''' is set to the number of the side of the player about to take their turn. This is before any healing takes place for that side, before calculating income, and before restoring unit movement and status.
* '''turn refresh''': this event triggers just before a side is taking control after healing, calculating income, and restoring unit movement and status.
* '''turn X''': (for X some number) this event triggers at the start of turn ''X''. ''X'' cannot be 1.
* '''time over''': this event triggers on turn ''turns''. (''turns'' is specified in [scenario])
* '''enemies defeated''': this event triggers when all units with '''canrecruit=yes''' (i.e. all leaders) not allied with side 1 are killed.
* '''victory''': in this scenario, any tag of the form '''[endlevel] result=victory [/endlevel]''' will be automatically preceded by all actions in this tag. It helps debugging if the victory event allows you to safely advance to any of the possible next maps after using the ":n" command. Scenarios where key units are picked up before the victory, or where some action chosen earlier determines which map to advance to, make it hard to quickly test scenarios in a campaign. (See also [endlevel], [[DirectActionsWML]])
* '''defeat''': in this scenario, any tag of the form '''[endlevel] result=defeat [/endlevel]''' will be automatically preceded by all actions in this tag. (See also [endlevel], [[DirectActionsWML]])
* '''ai turn''': is triggered just before the AI is invoked for a side. This is called after ''side turn'', and thus the WML variable '''side_number''' still holds the number of this side.

Filters can be applied to the following event triggers (see [[FilterWML]]; see also below). The actions specified in the event tag will be executed only if the filter returns true.
These event triggers are all actions by units ('''moveto''', '''attack''') or things that happen to units ('''recruit''', '''advance'''). When one of these events is triggered, the position of the active unit (referred to as the '''primary unit''') is stored in the variables '''x1''' and '''y1''' and the position of any unit that primary unit does something to is stored in the variables '''x2''' and '''y2''' (this unit is referred to as the '''secondary unit''' below). '' These units are also automatically stored in the variables 'unit' and 'second_unit' as if they had been stored using the '''[store_unit]''' tag. see [[SingleUnitWML]]

* '''moveto'''': triggers after the primary unit moves. Typically this is used when the primary unit gets to a particular location and a filter for the location of the primary unit is included; remember that this is the location that the primary unit lands on, not the location it started on or any location it travels on.
* '''sighted''': this event triggers when the primary unit moves to a location where the secondary unit is in sight range of the primary unit. Works only in shroud or fog.
* '''attack''': this event triggers when the primary unit attacks the secondary_unit.
* '''attacker_hits''': this event triggers when the the primary unit (the attacker) hits the secondary unit (the defender).
* '''attacker_misses''': same as ''attacker_hits'', but is triggered when the attacker misses.
* '''defender_hits''': this event triggers when the primary unit (the attacker) is hit in retaliation by the secondary unit (the defender).
* '''defender_misses''': same as ''defender_hits'', but is triggered when the defender misses.
* '''attack_end''': is similar to '''attack''', but is instead triggered after the fight, not before. Note that if either unit is killed during the fight, this event triggers before any '''die''' events.
* '''stone''': this event triggers when the primary unit is hit by an attack with the 'stones' ability (See ''stones'', [[AbilitiesWML]]) by the secondary unit (the unit with the 'stones' ability).
* '''last breath''': this event triggers when the primary unit is killed by the secondary unit, but before the death animation is triggered.
* '''die''': this event triggers when the primary unit is killed by the secondary unit.
* '''capture''': this event triggers when the primary unit captures a village. The village may have been previously neutral, or previously owned by another side; merely moving into your own villages does not constitute a capture.
* '''recruit''': this event triggers when the primary unit is recruited or recalled. (That is, when a unit is recruited or recalled, it will trigger this event and this event's filter will filter that unit.)
* '''prerecruit''': this event triggers when the primary unit is recruited, but before it is displayed.
* '''advance''': this event triggers just before the primary unit is going to advance to another unit.
* '''post_advance''': this event triggers just after the primary unit has advanced to another unit.
* '''select''': triggers when the primary unit is selected. ''Note: in networked multiplayer, these events are only executed by the client on which the event is triggered, leading to out of sync errors if you modify the game state in the event.''
* '''menu item X''': triggers when a WML menu item with id=X is selected. ''Note: if the menu item has a [command], this event may be executed before or after the command; there is no guarantee.''
* {{DevFeature}} other events with a custom name may be invoked from [fire_event]

An '''[allow_undo]''' tag anywhere within a moveto event will cancel any lack of undo functionality the event would have caused. Note that undo functionality will only move the unit back to its former location; it will not other changes to the game caused by the event. Thus it is up to the scenario designer to use this tag correctly.

The primary unit can be referred to as '''unit''' and the secondary unit can be referred to as '''second_unit''' in [message] tags using the speaker= key. For example:

[event]
name=die
[message]
speaker=second_unit
message="Hahaha, I finally killed you!"
[/message]

[message]
speaker=unit
message="It's not over yet! I'll come back to haunt you!"
[/message]
[/event]

These keys and tags are more complex ways to filter when an event should trigger:
* '''first_time_only''': whether the event should be removed from the scenario after it is triggered. Default is '''yes'''.
* '''[filter]''': the event will only trigger if the primary unit matches this filter.
** [[StandardUnitFilter]]: selection criteria
* '''[filter_second]''': is like [filter], but for the secondary unit.
** [[StandardUnitFilter]]: selection criteria
* '''[special_filter]''' and '''[special_filter_second]''': can be used to set some additional filtering criteria for the primary unit and the secondary unit that are not generally available in a standard unit filter. Can be used in events ''attack'', ''attacker_hits'', ''attacker_misses'', ''defender_hits'', ''defender_misses'' and ''attack_end''.
** '''weapon''': the name of the weapon used.
** '''terrain''': the code for the terrain the unit is on.

=== Actions triggered by [event] ===

After the trigger conditions have been met, all action tags within the [event] tag are executed in the order they are written in.

There are 3 main types of actions:
* direct actions ([[DirectActionsWML]]) which have a direct effect on gameplay
* display actions ([[InterfaceActionsWML]]) which show something to the user
* internal actions ([[InternalActionsWML]]) which are used by WML internally

Several actions use standard filters to find out which units
to execute the command on. These are denoted by the phrases
"standard unit filter" and "standard location filter".

=== Nested events ===

There is 1 special type of action: event creation. By placing an '''[event]''' tag inside another '''[event]''' tag, the nested event is created when the nested event is encountered (when executing the contents of the event). For example, you could create a portal that opens on turn 10. The outer event executes on turn 10, creating the nested moveto event, which executes when a player steps on a certain spot. An equivalent way of doing this would be to a single moveto event with an if statement to check for turn number, but using nested '''[event]''' tags is a simple and elegant way to accomplish more complex tasks without resorting to excessive if statements.

Example:

[event]
name=turn 10

[event]
name=moveto

[filter]
x,y=5,8
[/filter]

# moving to 5,8 will trigger this event only on turn 10 and after
[/event]
[/event]

== See Also ==

* [[DirectActionsWML]]
* [[InternalActionsWML]]
* [[InterfaceActionsWML]]
* [[FilterWML]]
* [[ReferenceWML]]

[[Category: WML Reference]]

InternalActionsWML

2008-03-28T00:37:17Z

Noyga: /* [event] */

{{WML Tags}}
== Internal actions ==

Internal actions are actions that WML uses internally that do not directly affect gameplay, for example storing a variable.

The internal actions '''[if]''', '''[while]''', and '''[event]''' describe when/whether sets of actions should be executed.

== [if] ==

Executes different sets of actions based on whether the conditions described in the condition tags are true or not.

Condition tags:
* '''[have_unit]''': a unit passing this filter with >0 HP exists
** [[StandardUnitFilter]] (almost... '''Note:''' does not check for matching units in the recall list)

* '''[have_location]''': a location passing this filter exists
** [[StandardLocationFilter]]

* '''[and]''': If an [and] is present, all must evaluate to true in order for the [if] to evaluate true. Useful as a bracket for complex conditions, but not strictly necessary.
** condition tags as in [if]: if these evaluate to true, [and] evaluates to true.

* '''[or]''': If an [or] is present, one must evaluate to true in order for the [if] to evaluate true. ([[AdvancedConditionalWML|Example]])
** condition tags as in [if]: if these evaluate to true, '''[or]''' evaluates to true.

* '''[not]''': If a [not] is present, none must evaluate to true in order for the [if] to evaluate true.
** condition tags as in [if]: if these evaluate to true, [not] evaluates to false.

* '''[and],[or],[not]''': all top-level filters will support in-order conditional handling of and, or, and not. One important thing to remember is, if you have multiple [or]s, you should not wrap your first conditional statement into an [or] block.

* '''[variable]''': tests something about the value of a WML variable (see [[VariablesWML]])
** '''name''': the name of the variable to test the value of Only one of the following keys should be used for comparing the value of the variable to another value:
** '''equals''': $name is equal (string wise) to this
** '''not_equals''': $name is not equal to this
** '''greater_than''': $name is numerically greater than this
** '''less_than''': $name is less than this
** '''greater_than_equal_to''': $name is not less than this
** '''less_than_equal_to''': $name is not greater than this
** '''numerical_not_equals''': $name is greater than or less than this
** '''numerical_equals''': $name is not greater than or less than this
** '''boolean_equals''': $name has the same boolean value (e.g. off, false, 0, no)
** '''contains''': $name contains this string
** {{DevFeature}} '''boolean_not_equals''': $name has not the same boolean value. Strictly a syntactic shortcut for the following syntax that served its absence in 1.4:
[not]
[variable]
name=...
boolean_equals=...
[/variable]
[/not]

After condition tags:
* '''[then]''': contains a set of action tags which should be executed if all conditions are true, or all conditions in any single [or] are true
* '''[else]''': contains a set of action tags which should be executed if any condition is false, and all [or] tags are false

== [switch] {{DevFeature}} ==

Executes different sets of action based on the value of a variable.
[switch]
variable=foo
[case]
value="A"
... WML if foo=A ...
[/case]
[case]
value="B"
... WML if foo=B ...
[/case]
[else]
... WML if not foo=A nor foo=B ...
[/else]
[/switch]

* '''variable''': name of the variable to check.
* '''[case]''': Case block. Contains:
** '''value''': value to test the variable against.
** the action WML to execute if the variable matches the value (rest of the block).
* '''[else]''': Block of action WML to execute if no '''[case]''' block matches.

== [while] ==

Executes commands if all conditions are true.
Continues to execute them until a condition is not true.

Executes a maximum of 1024 iterations per invocation.
Condition tags are the same as for [if]

After condition tags:
* '''[do]''': contains actions that should be executed repeatedly until some condition is false.

The '''[while]''' tag is useful for iterating over an array.
An array is a list of values.
The ''number''th value in the array '''array''' is stored in the WML variable '''''array''[number]'''.
Note that if '''number''' is the value of the variable '''variable''',
the expression '''$''array''[$variable]''' will return the ''number''th value in ''array''.
The macros 'FOREACH' and 'NEXT' ([[UtilWML]]) can be used to iterate over an array;
i.e. run a set of actions once per element of the array.

=== {FOREACH} ===
If you wish to use a "for-each" iteration format (useful for example when you want to do an iteration for each row in a table) you can use the [http://www.wesnoth.org/macro-reference.xhtml FOREACH] and [http://www.wesnoth.org/macro-reference.xhtml NEXT] prededined macros.

=== {REPEAT} ===
You can use the REPEAT macro to perform a quick iteration for a number of times you specify.

== [event] ==

This adds a new event to the scenario.
The event is in the normal format for an '''[event]''' tag (See [[EventWML]]).
This is useful if you want an event that can only be triggered when a prior event is fulfilled

These tags describe actions that affect the values of WML variables
(see [[VariablesWML]] for information on WML variables,
and [[UtilWML]] for convenient macro shortcuts for some of these):
* '''[set_variable]''': manipulates a WML variable. {{Note:Predefined Macro|VARIABLE}}
** '''name''': the name of the variable to manipulate
** '''value''': set the variable to the given value (can be numeric or string). This only interprets dollars signs if it is the very first character, and then the entire value must be a simple variable name. (in 1.3.2, has the same effect as format. Use literal for no substitution)
** '''literal''': set the variable to the given value (can be numeric or string). This does not interpret any dollars signs.
** '''format''': set the variable to the given value. Interprets the dollar sign to a higher degree than most actions. (see [[VariablesWML]])
** '''to_variable''': Fully processes its value as in ''format'', and then gets the variable with that name.
** '''add''': add the given amount to the variable. To subtract, add a negative number.
** '''multiply''': multiply the variable by the given number. To divide, multiply by the inverse eg: 4/2 = 4 * 1/2 = 4 * 0.5. To negate, multiply by -1. The result is an integer.
** '''divide''': divide the variable by the given number. The result is an integer.
** '''modulo''': returns the remainder of an integer division. Both variables need to be an integer, the result is also an integer. eg 5 % 2 = 1.
** '''random''': the variable will be randomly set. You may provide a comma separated list of possibilities, e.g. 'random=Bob,Bill,Bella'. You may provide a range of numbers (integers), e.g. 'random=3..5'. You may combine these, e.g. 'random=100,1..9', in which case there would be 1/10th chance of getting 100, just like for each of 1 to 9. Dollars signs are only normally interpreted here, so it is harder to have a dynamically determined range. You would need to create the random-string with ''format''.
** '''rand''': does the same as random, but has better MP support. See [[BuildingMultiplayerExamples]] for more info on the MP case. '''It is highly recommended that you use this feature for randomization.'''
** '''time=stamp''': Retrieves a timestamp in milliseconds since wesnoth was started, can be used as timing aid. Don't try to use this as random value in MP since it will cause an OOS.
** {{DevFeature}} '''string_length''': Retrieves the length in characters of the string passed as this attribute's value; such string is parsed and variable substitution applied automatically (see [[VariablesWML]] for details).
** {{DevFeature}} '''[join]''' joins an array of strings to a textual list
***variable: name of the array
***key: array[$i].key to look for the strings
***separator: separator to connect the elements
***remove_empty: wether to ignore empty elements

* {{DevFeature}} '''[set_variables]''': manipulates a WML array
** '''name''': the name of the container to manipulate
** '''mode''': one of the following values:
***replace: will clean the array '''name''' and replace it with given data
***append: will append given data to the current array
***merge: will merge in the given data into '''name'''
** '''to_variable''': data will be set to the given array
** '''[value]''': the WML inside the [value] tags will be stored in data, variables will be interpolated directly, use $| in order to escape the $ sign, you can store arrays of WML by supplying multiple [value] tags, example:
[set_variables]
name=arr
mode=replace
[value]
foo=bar
[/value]
[value]
foo=more
[/value]
[/set_variables]
{DEBUG_MSG $arr[0].foo}
{DEBUG_MSG $arr[1].foo}
=>bar; more
** '''[literal]''': same as '''[value]''', but variables will not be substituted, '''[literal]''' and '''[value]''' can not be used in the same [set_variables] tag, i.e. you can not create arrays by piling a mix of '''[value]''' and '''[literal]''' tags
**'''[split]''' splits a textual list into an array which will then be set to data
***list: textual list to split
***key: array[$i].key to put the elements in
***separator: separator to separate the elements
***remove_empty: wether to ignore empty elements

* {{DevFeature}} '''[fire_event]''': trigger a WML event
** '''name''': the name of event to trigger
** '''[primary_unit]''': primary unit for the event (usually the attacker) (optional)
** '''[secondary_unit]''': secondary unit for the event (usually the defender) (optional)
** both tags have some keys which are optional :
*** '''x,y''': location of this unit
*** '''weapon''': weapon that this unit was supposed to use for this event

* '''[store_unit]''': stores details about units into game variables. Common usage is to manipulate a unit by using [store_unit] to store it into a variable, followed by manipulation of the variable, and then [unstore_unit] to re-create the unit with the modified variables. Note: stored units also exist on the field, and modifying the stored variable will not automatically change the stats of the units. You need to use [unstore_unit]. See also [unstore_unit], [[DirectActionsWML]], and '''FOREACH''', [[UtilWML]]
** '''[filter]''': [[StandardUnitFilter]] all units matching this filter will be stored. If there are multiple units, they will be stored into an array of variables.
** '''variable''': the name of the variable into which to store the unit(s)
** '''mode''': defaults to ''always_clear'', which clears the variable, whether or not a match is found. If mode is set to ''replace'', the variable will only be cleared if a match is found. If mode is set to ''append'', the variable will not be cleared.
** '''kill''': if 'yes' the units that are stored will be removed from play. This is useful for instance to remove access to a player's recall list, with the intent to restore the recall list later.
:When a unit is stored, the following values may be manipulated with '''[set_variable]'''
:* description
:* experience
:* facing
:* gender
:* canrecruit
:* overlays
:* goto_x
:* goto_y
:* hitpoints
:* moves
:* resting
:* side
:* type
:* unrenamable
:* upkeep
:* user_description
:* x
:* y
:* [variables]
:* [status]
:* [modifications]
Variables, status, and modifications are children of the stored unit variable. Example:
[set_variable]
name=unit_store.status.poisoned
value=yes
[/set_variable]

:All keys and tags in the unit definition may be manipulated, including some others. Here is a sample list. If you have a doubt about what keys are valid or what the valid value range is for each key, code a [store_unit] event, save the game, and examine what keys are in the file.
:* advanceto
:* alignment
:* alpha
:* attacks_left
:* canrecruit
:* controller
:* cost
:* description
:* experience
:* facing
:* flying
:* fog
:* gender
:* get_hit_sound
:* gold
:* goto_x
:* goto_y
:* hitpoints
:* id
:* image
:* image_defensive
:* income
:* language_name (same as the name key in the unit config)
:* level
:* max_attacks
:* max_experience
:* max_hitpoints
:* max_moves
:* movement
:* movement_type
:* moves
:* race
:* resting
:* shroud
:* side
:* team_name
:* type
:* unit_description
:* unrenamable
:* usage
:* value
:* x
:* y
:* zoc
:* [advancement]
:* [/advancement]
:* [movement_costs]
:* [/movement_costs]
:* [defense]
:* [/defense]
:* [resistance]
:* [/resistance]
:* [variables]
:* [/variables]
:* [status]
:* [/status]
:* [attack]
:* [/attack]
:* [modifications_description]
:* [/modifications_description]
:* [modifications]
:* [/modifications]

* '''[store_starting_location]''': Stores the starting location of a side's leader in a variable. The variable is a composite type which will have members 'x', 'y', and 'terrain' (the terrain type for a starting location is always 'K' unless it has been changed)
** '''side''': the side whose starting location is to be stored
** '''variable''': (default='location'): the name of the variable to store the location in
* '''[store_locations]''': Stores a series of locations that pass certain criteria into an array. Each member of the array has members 'x' and 'y' (the position) and 'terrain' (the terrain type).
** [[StandardLocationFilter]]: a location or location range which specifies the locations to store. You must specify this or no locations will be stored.
** '''variable''': the name of the variable (array) into which to store the locations
** '''terrain''': a comma-sperated list of terrain codes. (See [[TerrainCodesWML]] for possible values.) If present, locations will only be chosen if the code for the terrain type of that location is listed.
** '''radius''': if present, any locations which are within '''radius''' hexes of the location filter will also be stored
** '''[filter]''': [[StandardUnitFilter]] only locations with units on them that match the filter will be stored. Use a blank filter to only store locations with units.
* '''[store_villages]''': Stores a series of locations of villages that pass certain criteria into an array. Each member of the array has members 'x' and 'y' (the position) and 'terrain' (the terrain type).
** '''owner_side''': a side number. If present, only villages owned by this side will be choosen. If owner_side=0, store the unowned villages.
** '''variable''': the name of the variable (array) into which to store the locations
** '''terrain''': a series of terrain characters. (See [[TerrainLettersWML]] for possible values.) If present, villages will only be chosen if the terrain code of the terrain type of that location is listed. You may give a comma separated list of terrains.
** '''side''': (default=1) the side for which the gold should be stored
** '''variable''': (default='gold') the name of the variable to store the gold in
* '''[store_side]''': stores information about a certain side in a variable. The variable will contain the member variables 'name', 'team_name', 'gold' and 'income', 'fog', 'shroud', 'user_team_name', 'colour', 'controller', 'village_gold' and 'recruit'.)
** '''side''': the side whose information should be stored
** '''variable''': the name of the variable to store the information in
* '''[clear_variable]''': This will delete the given variable or array. This is good to use to clean up the set of variables -- e.g. a well-behaved scenario will delete any variables that shouldn't be kept for the next scenario before the end of the scenario. Tags and variables of stored units can also be cleared, meaning that [trait]s and [object]s, for example, can be removed.
** '''name''': the name of the variable to clear.
* '''[role]''': tries to find a unit to assign a role to. This is useful if you want to choose a non-major character to say some things during the game. Once a role is assigned, you can use '''role=''' in a unit filter to identify the unit with that role (See [[FilterWML]]). However, there is no guarantee that roles will ever be assigned. You can use '''[have_unit]''' (see [if]) to see whether a role was assigned. This tag uses a [[StandardUnitFilter]] with the modification to order the search by type, mark only the first unit found with the role, and the role attribute is not used in the search. If for some reason you want to search for units that have or don't have existing roles, you can use one or more [not] filters. The will check recall lists in addition to units on the map. In normal use, you will probably want to include a ''side'' attribute to force the unit to be on a particular side.
** '''role''': the value to store as the unit's role. This role is not used in the [[StandardUnitFilter]] when doing the search for the unit to assign this role to.
** '''type''': a comma-separated list of possible types the unit can be. If any types are given, then units will be searched by type in the order listed. If no type is given, then no particular order with respect to type is guaranteed.
* {{DevFeature}} '''[store_map_dimensions]''': Stores the map dimensions in a variable.
** '''variable''': the name of the variable where the values will be saved into. If it is skipped, a variable 'map_size' is used, and its contents overridden, if they existed already. The result is a container variable, with members ''width'' and ''height''.

== See Also ==
* [[VariablesWML]]
* [[DirectActionsWML]]
* [[InterfaceActionsWML]]
* [[EventWML]]
* [[ReferenceWML]]

[[Category: WML Reference]]

FrenchTranslation

2008-03-26T19:35:39Z

Noyga: Undo revision 22919 by Esr (Talk)

Battle for Wesnoth - Traduction française
== Le mot d'introduction ==

Cette page sert à mieux coordonner l'effort de tous et à donner les informations souvent demandées avant de se lancer dans la traduction française.

== Règles de traduction ==
=== Respect des termes de l'univers de Wesnoth ===
Pour améliorer la cohérence de l'ensemble des traductions, plusieurs Wikis servent de dictionnaires pour décrire l'univers de Wesnoth :
# unités : [[FrenchUnits]] ;
# noms communs : [[NomsCommuns]] ;
# noms propres : [[NomsPropres]].

=== Respect du contexte ===
Il est important de correctement traduire les différents textes. Il ne suffit pas de traduire mot à mot les différentes phrases, il faut aussi faire très attention au contexte.

=== Respect des règles de typographie ===

==== Titres ====
Les titres des campagnes, des scénarios et des chapitres doivent suivre les règles de la langue française. Ces règles se trouvent sur http://fr.wikipedia.org/wiki/Wikip%C3%A9dia:Conventions_typographiques.

==== Ponctuation ====
Les traductions doivent aussi suivre les règles de ponctuation de la langue française, essentielles à un bon affichage du texte ; par exemple, l'utilisation d'une espace fine avant le signe « : » évitera que ce signe ne se trouve en début de ligne d'un texte. Ces règles se trouvent sur http://www.reveenjoie-poesie.com/outils-linguistiques/Typographie_francaise.html.

Il est préférable de ne pas mettre de virgule ni avant le « et », ni avant le « ou » (contrairement à l'anglais).

Remarque : sous Windows, la combinaison Alt+(0160) permet d'écrire une espace fine (les parenthèses indiquent qu'il faut maintenir la touche Alt appuyée).
Voici d'autres raccourcis : http://www.crdp-montpellier.fr/cd48/tice/trucs/majuscules.htm#win

==== Majuscules ====
Les majuscules doivent être accentuées dans les textes traduits : À, Â, Æ, Ç, É, Ê, È, Î, Ô, Œ, Ù, Û...

Voici également quelques rappels sur des confusions fréquentes :
# pas de majuscules aux noms des races (« nains », « elfes », « orcs », etc.) ;
# majuscules aux noms de clans ou de factions (les humains de « l'Ordre de la Serre Pourpre ») ;
# majuscules aux points cardinaux quand on parle d'une partie d'un tout (« les forêts de l'Ouest » peuvent se trouver à l'est), et minuscule quand on parle de la direction (« aller vers le nord »).

=== Respect des règles de l'orthographe ===
Il est préférable de soigner son orthographe : le CNRS et l'ATILF fournissent un dictionnaire en ligne performant et complet : http://atilf.atilf.fr/

Les rectifications d'orthographes préconisées par l'Académie Française peuvent s'appliquer (http://www.academie-francaise.fr/langue/orthographe/regles.html).

== Principes de traduction pour Wesnoth ==
Le principe est de mettre à jour les fichiers .po, fichiers servant à gérer les traductions dans Wesnoth. Les échanges se font via la mailing list.

=== S'inscrire à la mailing list ===
La mailing list francophone de Wesnoth est l'outil privilégié pour
# d'abord avertir les traducteurs que vous allez commencer une traduction (et éviter de travailler sur le même fichier),
# envoyer ses traductions pour validation ou relecture,
# poser des questions.

Pour s'inscrire à la mailing list, envoyez un mail vide ayant comme sujet « subscribe » (il sera traité par un robot) ; ou cliquez directement ici mailto:wesnoth-request@ml.free.fr?subject=subscribe et envoyez...

Les responsables des différentes mailing list sont ici : [[WesnothTranslations]].

Les archives de la mailing list sont ici : http://news.gmane.org/gmane.games.wesnoth-fr ; vous pouvez vous abonner au serveur de news news.gmane.org (gmane.games.wesnoth-fr).

Il est également possible de discuter sur le canal IRC #wesnothfr (sur irc.freenode.net) ou sur le forum, mais l'équipe de traduction française ne s'y promène que rarement.

=== Récupérer les fichiers .po nécessaires ===
Les fichiers à traduire sont accessibles :
# soit par cette page : http://gettext.wesnoth.org/ (le plus simple),
# soit par le CVS : http://savannah.nongnu.org/cvs/?group=wesnoth (si on aime CVS).

=== Modifier les fichiers .po et vérifier le statut des lignes traduites ===
Plusieurs logiciels permettent de modifier ces fichiers :
# les éditeurs de texte
#* notepad++ (http://notepad-plus.sourceforge.net/fr/site.htm) ;
#* textpad (http://www.textpad.com/);
#* ou, pour Mac, Textwrangler (http://www.barebones.com/products/textwrangler/index.shtml) ;
#* et puis bien d'autres encore...
# ou des éditeurs spécifiques aux fichiers .po
#* poEdit, pour Mac et PC (http://www.poedit.net/) ;
#* KBabel (http://i18n.kde.org/tools/kbabel/) ;
#* gtranslator (http://gtranslator.sourceforge.net/).

Chaque champ de traduction possède un statut :
# si vous traduisez pour la première fois un champ, mettez-le en traduction approximative ("fuzzy" en anglais), et ce même si c'est une traduction très basique ; toute traduction doit être relue au moins une fois avant d'être approuvée ;
# si vous relisez un champ, libre à vous de décider de son statut après votre relecture ;
#* sortez-le de son état approximatif si vous le considérez incontestablement bien traduit ;
#* laissez-le à l'état approximatif et demandez une deuxième relecture si vous n'êtes pas sûr de la traduction.

=== Tester sa traduction ===
Si vous le désirez, vous pouvez immédiatement tester votre traduction :
# enlevez l'option fuzzy de la ligne (ou des lignes) que vous voulez vérifier ;
# générez un fichier compilé « .mo » à partir du fichier texte « .po » ;
#*En ligne de commande : la commande « msgfmt » peut être utilisée avec le nom du fichier « .po » (exemple : « msgfmt mon_fichier.po -o mon_fichier.mo » générera « mon_fichier.mo »).
#*Avec l'éditeur « poedit » : « Fichier -> Préférence », onglet « Editeur, cochez la case « Compiler automatiquement les fichiers .mo lors de la sauvegarde » ; sauvez le fichier.
# copiez votre fichier dans le répertoire contenant les traductions et renommez-le ;
#*Sous Windows, <Répertoire d'installation de Wesnoth>\fr\LC_MESSAGES\<Nom du fichier à tester> (Exemple : C:\Wesnoth\po\fr\LC_MESSAGES\wesnoth-utbs.mo) ;
#*Sous Linux, répertoire en fonction de la distribution (Exemple Mandriva : /usr/share/locale/fr/LC_MESSAGES).
# jouez.... jusqu'au moment où le texte traduit est censé apparaître ; il n'est pas nécessaire de tout reprendre depuis le début, une sauvegarde fonctionne. Un texte traduit sans erreur apparaît... traduit.

Remarque : pour accélérer les tests, vous pouvez utiliser le mode debug de Wesnoth :
#Pour passer en mode débug :
#*taper : (pour ouvrir le mode de commande), puis : debug<entrée>
#*ou taper "wesnoth.exe --debug",
#*ou taper "wesnoth.exe -d"
# pour utiliser le mode débug :
#*":debug" entre en mode debug
#*":n" termine le scénario immédiatement

=== Envoyer sa traduction ===
Une traduction terminée est compressée, puis envoyée à la ML.

Il est préférable, en cas de relecture, de signaler les modifications dans le corps du mail, par exemple en faisant comme ci-dessous :
#Exemple 1 (refonte d'une phrase) : N° ligne Anciene version => Nouvelle version.
#Exemple 2 (correction d'une faute, indiquée par des *) : N°Ligne Ancien*n*e version

Il est également possible de générer un fichier différentiel entre l'ancienne et la nouvelle version ; mais l'expérience semble montrer que cela est peu relu.
Cette techique est surtout à utiliser qu'en cas de modifications massives (cas où le suivi ligne à ligne serait complexe et lourd).

=== Attention ===
Il y a un bug récurent dans les fichiers po : lorsque la phrase traduite commence par "$", rien ne s'affiche

dans le jeu. Pour corriger le problème, il suffit de mettre un simple espace devant le signe (seulement quand la phrase commence par $)

== Aujourd'hui, qui fait quoi ? ==
Ce chapitre vous permet de savoir qui fait quoi...

Date de dernière mise à jour : 22/03/2008
* Traductions
** wesnoth-httt (Heir To The Throne / L'Héritier du trône) : La_vie_en_Wose
** wesnoth-thot (The Hammer of Thursagan) : Dylann/gotrek860
** wesnoth-utbs (Under the burning suns) : Damien
** wesnoth-did (Descent in the Darkness) : Jean-joseph
* Relectures / À relire

[[Category:Translations]]

ThemeWML

2008-03-16T17:57:24Z

Noyga: /* [status] */

{{WML Tags}}
== The toplevel [theme] tag ==

Themes are used both for the wesnoth game and the wesnoth editor.
Themes allow flexible configuration of how everything is laid out on-screen.

The only key in '''[theme]''' is '''name'''. This is the name of the theme.

The only tag in '''[theme]''' is '''[resolution]''', but each theme can have multiple [resolution] tags.
The [resolution] tags are scanned until the first one which is of the same or lower resolution than is currently being used is found, and this is used as our theme.
This allows us to define themes to work differently on different resolutions,
and will allow us to support both high and low resolutions elegantly.

The following keys and tags are recognized for [resolution]:

* '''width''', '''height''': dimensions in pixels

All subtags of [resolution] use the following keys:
* '''rect''': defines the rectangle to display on. Parts of a ''rect=a,b,c,d'' clause may be:
** number : absolute positions
** ''='' : same value as the same field in reference rect (alignment with reference)
** +number or -number : for a and b, add this value to reference's c and d respectively (spacing from reference)
; for c and d, add this value to self's a and b (specify by width and height)
** =+number or =-number : add this value to same field in reference rect (eg. consider reference as a container box)
* '''xanchor''', '''yanchor''': control the behavior of how this rectangle changes as the resolution changes.
** '''left'''': its distance from the left side of the screen always remain the same, while changes in the resolution will change its size by the same amount (top for the y axis).
** '''right''': its size always remain the same, as well as its distance to the right side of the screen (bottom for the y axis).
** '''fixed''': its co-ordinates in that axis remain constant
** '''proportional''': its co-ordinates multiplied by the ratio of the resolution being used to the canonical resolution.

== [main_map] ==

defines where the main game display (i.e. all the hexagons and units) is displayed.

== [main_map_border] ==
Defines the border of the main map area. It has the following keys.

* '''border_size''': the size of the border, the value should be between 0.0 and 0.5. The images which are used by default are sized for 0.5. If the border gets smaller the images still need the same size. They're simply cut off at the right spot.
* '''background_image''': the filename of the image to use as background.
* '''tile_image''': the filename of the image to use for the _off^_usr tile. The image in the minimal can't be controlled only the image in the main map. This image must be in the terrain directory and a png image. When specifying the image the 'terrain/' prefix and '.png' suffix _must_ be ommitted.
* '''corner_image_top_left''': filename for the image in the top left corner.
* '''corner_image_bottom_left''': filename for the image in the top left corner.
* '''corner_image_top_right_odd''': filename for the image in the top right corner, if the x value of the corner is odd. This x value is the value seen in game (and thus not in the source).
* '''corner_image_top_right_even''': filename for the image in the top right corner, if the x value of the corner is even. This x value is the value seen in game (and thus not in the source).
* '''corner_image_bottom_right_odd''': filename for the image in the bottom right corner, if the x value of the corner is odd. This x value is the value seen in game (and thus not in the source).
* '''corner_image_bottom_right_even''': filename for the image in the bottom right corner, if the x value of the corner is even. This x value is the value seen in game (and thus not in the source).
* '''border_image_left''': filename for the image at the left border.
* '''border_image_right''': filename for the image at the right border.
* '''border_image_top_odd''': filename for the image at the top border, if the x value of the tile is odd. This x value is the value seen in game (and thus not in the source).
* '''border_image_top_even''': filename for the image at the top border, if the x value of the tile is even. This x value is the value seen in game (and thus not in the source).
* '''border_image_bottom_odd''': filename for the image at the bottom border, if the x value of the tile is odd. This x value is the value seen in game (and thus not in the source).
* '''border_image_bottom_even''': filename for the image at the bottom border, if the x value of the tile is even. This x value is the value seen in game (and thus not in the source).

== [mini_map] ==

Determines where the mini map is displayed

== [panel] ==

Displays an image as a panel on-screen.
* '''image''': the image used for the panel

== [label] ==

Displays a text label on screen.
* '''prefix''': a string that will be printed before the text in all languages
* '''text''': a text string id to be displayed
* '''postfix''': a string that will be printed after the text in all languages
* '''icon''': an image that will be displayed instead of the text if it is available
* '''font_size''': the size of font to use for the label

== [menu] ==

* '''title''': the id of the string to write on the button
* '''title_literal''': a string that will be displayed "as is" in all language after the title
* '''image''': the image to use if available
* '''is_context_menu''': if set to true this menu will not be placed, but displayed on a right click
* '''items''': comma separated list of actions to put in the menu. if there is only one action, it will be executed immediately and no menu will be displayed
** '''cycle''': move to next movable unit
** '''endunitturn''': consume this unit's move and cycle to the next one
** '''leader''': center on the leader
** '''undo''': undo last action
** '''redo''': redo undone action
** '''zoomin''': zoom the map in
** '''zoomout''': zoom the map out
** '''zoomdefault''': return to default zoom
** '''fullscreen''': switch fulscreen mode
** '''accelerated''': switch turbo mode
** '''resistance''': show resistance table of current unit
** '''terraintable''': show terrain table of current unit
** '''describeunit''': show unit description
** '''renameunit''': change unit name
** '''save''': save the game
** '''recruit''': recruit a unit
** '''repeatrecruit''': repeat last recruitement
** '''recall''': recall a unit from previous scenarion
** '''endturn''': end current turn
** '''togglegrid''': toggle grid display
** '''statustable''': show status table
** '''mute''': mute all sounds
** '''speak''': send message to other players
** '''createunit''': debug create a unit on the map
** '''preferences''': open preference dialog
** '''objectives''': show objective window
** '''unitlist''': list units
** '''statistics''': show game statistics
** '''quit''': quit the game
** '''labelterrain''': label current location
** '''clearlabels''': clear all labels on map
** '''showenemymoves''': show grids reachable by the enemy
** '''bestenemymoves''': show grids reachable by the enemy with no zone of control
** '''editnewmap''': editor only start a new map
** '''editloadmap''': editor only loads an existing map
** '''editsavemap''': editor only saves the current map
** '''editsaveas''': editor only saves the current map, let you choose a filename
** '''editsetstartpos''': editor only set a starting position for a team
** '''editfloodfill''': editor only flood the map with a terrain
** '''toggleshroud''': toggle the "moving removes shroud" behaviour
** '''updateshroud'': removes all possible shroud
** '''AUTOSAVES'': expands to a list of all Auto-Save games prior to this one

== [status] ==

This tag describes the Status Table.
This tag contains many other tags, which determine where other game statistics, such as the current turn, and a description of selected units go.
For instance, the [time_of_day] tag will determine where the time of day image goes.
Each subtag of [status] can contain the following attributes

** '''font_size''': the size of font to use for the status
** '''rect''': the rectangle as for the main_map attribute
** '''xanchor''': the x-wise anchoring as for the main_map attribute
** '''yanchor''': the y-wise anchoring as for the main_map attribute
** '''prefix''': the string to display before the actual status, this is the string id for internationalisation
** '''prefix_literal''': a string to put after the prefix, but before the label for all languages.
** '''postfix_literal''': a string to put after the status
** '''postfix''': the string to display after the postfix_literal, this is the string id for internationalisation

the following tags are recognized for [status]:
* '''[unit_description]''': the user description of the current unit. Note {{DevFeature}}: this tag is now obsolete
* {{DevFeature}} '''[unit_name]''': the user description of the current unit
* '''[unit_type]''': the type of the current unit
* '''[unit_race]''': the race of the current unit
* '''[unit_level]''': the level of the current unit
* {{DevFeature}} '''[unit_side]''': the side of the current unit (flag)
* '''[unit_traits]''': the traits of the current unit
* '''[unit_status]''': the status of the current unit
* '''[unit_alignment]''': the alignment of the current unit
* '''[unit_abilities]''': the abilities of the current unit
* '''[unit_hp]''': the HP of the current unit
* '''[unit_xp]''': the XP of the current unit
* '''[unit_moves]''': the moves remaining for the current unit
* '''[unit_weapons]''': the attacks of the current unit
* '''[unit_image]''': the icon for the current unit
* '''[unit_profile]''': the portait for the current unit
* '''[time_of_day]''': the time of day on the current location
* '''[turn]''': the turn number and turn remaining
* '''[gold]''': the gold remaining
* '''[villages]''': the number of villages owned
* '''[num_units]''': the number of units owned
* '''[upkeep]''': the money needed to keep your units every turn
* '''[expenses]''': the money lost each turn when you don't have enough income
* '''[income]''': the income per turn (can be positive)
* '''[terrain]''': the text description of the current terrain
* '''[position]''': the current terrain's position
* '''[side_playing]''': the current playing side (flag)
* '''[observers]''': the current observers

== See Also ==

* [[ThemeSystem]]
* [[Using custom themes in campaigns]]
* [[ReferenceWML]]

[[Category: WML Reference]]

ThemeWML

2008-03-16T17:55:46Z

Noyga: /* [status] */

{{WML Tags}}
== The toplevel [theme] tag ==

Themes are used both for the wesnoth game and the wesnoth editor.
Themes allow flexible configuration of how everything is laid out on-screen.

The only key in '''[theme]''' is '''name'''. This is the name of the theme.

The only tag in '''[theme]''' is '''[resolution]''', but each theme can have multiple [resolution] tags.
The [resolution] tags are scanned until the first one which is of the same or lower resolution than is currently being used is found, and this is used as our theme.
This allows us to define themes to work differently on different resolutions,
and will allow us to support both high and low resolutions elegantly.

The following keys and tags are recognized for [resolution]:

* '''width''', '''height''': dimensions in pixels

All subtags of [resolution] use the following keys:
* '''rect''': defines the rectangle to display on. Parts of a ''rect=a,b,c,d'' clause may be:
** number : absolute positions
** ''='' : same value as the same field in reference rect (alignment with reference)
** +number or -number : for a and b, add this value to reference's c and d respectively (spacing from reference)
; for c and d, add this value to self's a and b (specify by width and height)
** =+number or =-number : add this value to same field in reference rect (eg. consider reference as a container box)
* '''xanchor''', '''yanchor''': control the behavior of how this rectangle changes as the resolution changes.
** '''left'''': its distance from the left side of the screen always remain the same, while changes in the resolution will change its size by the same amount (top for the y axis).
** '''right''': its size always remain the same, as well as its distance to the right side of the screen (bottom for the y axis).
** '''fixed''': its co-ordinates in that axis remain constant
** '''proportional''': its co-ordinates multiplied by the ratio of the resolution being used to the canonical resolution.

== [main_map] ==

defines where the main game display (i.e. all the hexagons and units) is displayed.

== [main_map_border] ==
Defines the border of the main map area. It has the following keys.

* '''border_size''': the size of the border, the value should be between 0.0 and 0.5. The images which are used by default are sized for 0.5. If the border gets smaller the images still need the same size. They're simply cut off at the right spot.
* '''background_image''': the filename of the image to use as background.
* '''tile_image''': the filename of the image to use for the _off^_usr tile. The image in the minimal can't be controlled only the image in the main map. This image must be in the terrain directory and a png image. When specifying the image the 'terrain/' prefix and '.png' suffix _must_ be ommitted.
* '''corner_image_top_left''': filename for the image in the top left corner.
* '''corner_image_bottom_left''': filename for the image in the top left corner.
* '''corner_image_top_right_odd''': filename for the image in the top right corner, if the x value of the corner is odd. This x value is the value seen in game (and thus not in the source).
* '''corner_image_top_right_even''': filename for the image in the top right corner, if the x value of the corner is even. This x value is the value seen in game (and thus not in the source).
* '''corner_image_bottom_right_odd''': filename for the image in the bottom right corner, if the x value of the corner is odd. This x value is the value seen in game (and thus not in the source).
* '''corner_image_bottom_right_even''': filename for the image in the bottom right corner, if the x value of the corner is even. This x value is the value seen in game (and thus not in the source).
* '''border_image_left''': filename for the image at the left border.
* '''border_image_right''': filename for the image at the right border.
* '''border_image_top_odd''': filename for the image at the top border, if the x value of the tile is odd. This x value is the value seen in game (and thus not in the source).
* '''border_image_top_even''': filename for the image at the top border, if the x value of the tile is even. This x value is the value seen in game (and thus not in the source).
* '''border_image_bottom_odd''': filename for the image at the bottom border, if the x value of the tile is odd. This x value is the value seen in game (and thus not in the source).
* '''border_image_bottom_even''': filename for the image at the bottom border, if the x value of the tile is even. This x value is the value seen in game (and thus not in the source).

== [mini_map] ==

Determines where the mini map is displayed

== [panel] ==

Displays an image as a panel on-screen.
* '''image''': the image used for the panel

== [label] ==

Displays a text label on screen.
* '''prefix''': a string that will be printed before the text in all languages
* '''text''': a text string id to be displayed
* '''postfix''': a string that will be printed after the text in all languages
* '''icon''': an image that will be displayed instead of the text if it is available
* '''font_size''': the size of font to use for the label

== [menu] ==

* '''title''': the id of the string to write on the button
* '''title_literal''': a string that will be displayed "as is" in all language after the title
* '''image''': the image to use if available
* '''is_context_menu''': if set to true this menu will not be placed, but displayed on a right click
* '''items''': comma separated list of actions to put in the menu. if there is only one action, it will be executed immediately and no menu will be displayed
** '''cycle''': move to next movable unit
** '''endunitturn''': consume this unit's move and cycle to the next one
** '''leader''': center on the leader
** '''undo''': undo last action
** '''redo''': redo undone action
** '''zoomin''': zoom the map in
** '''zoomout''': zoom the map out
** '''zoomdefault''': return to default zoom
** '''fullscreen''': switch fulscreen mode
** '''accelerated''': switch turbo mode
** '''resistance''': show resistance table of current unit
** '''terraintable''': show terrain table of current unit
** '''describeunit''': show unit description
** '''renameunit''': change unit name
** '''save''': save the game
** '''recruit''': recruit a unit
** '''repeatrecruit''': repeat last recruitement
** '''recall''': recall a unit from previous scenarion
** '''endturn''': end current turn
** '''togglegrid''': toggle grid display
** '''statustable''': show status table
** '''mute''': mute all sounds
** '''speak''': send message to other players
** '''createunit''': debug create a unit on the map
** '''preferences''': open preference dialog
** '''objectives''': show objective window
** '''unitlist''': list units
** '''statistics''': show game statistics
** '''quit''': quit the game
** '''labelterrain''': label current location
** '''clearlabels''': clear all labels on map
** '''showenemymoves''': show grids reachable by the enemy
** '''bestenemymoves''': show grids reachable by the enemy with no zone of control
** '''editnewmap''': editor only start a new map
** '''editloadmap''': editor only loads an existing map
** '''editsavemap''': editor only saves the current map
** '''editsaveas''': editor only saves the current map, let you choose a filename
** '''editsetstartpos''': editor only set a starting position for a team
** '''editfloodfill''': editor only flood the map with a terrain
** '''toggleshroud''': toggle the "moving removes shroud" behaviour
** '''updateshroud'': removes all possible shroud
** '''AUTOSAVES'': expands to a list of all Auto-Save games prior to this one

== [status] ==

This tag describes the Status Table.
This tag contains many other tags, which determine where other game statistics, such as the current turn, and a description of selected units go.
For instance, the [time_of_day] tag will determine where the time of day image goes.
Each subtag of [status] can contain the following attributes

** '''font_size''': the size of font to use for the status
** '''rect''': the rectangle as for the main_map attribute
** '''xanchor''': the x-wise anchoring as for the main_map attribute
** '''yanchor''': the y-wise anchoring as for the main_map attribute
** '''prefix''': the string to display before the actual status, this is the string id for internationalisation
** '''prefix_literal''': a string to put after the prefix, but before the label for all languages.
** '''postfix_literal''': a string to put after the status
** '''postfix''': the string to display after the postfix_literal, this is the string id for internationalisation

the following tags are recognized for [status]:
* '''[unit_description]''': the user description of the current unit. Note
* {{DevFeature}} '''[unit_name]''': the user description of the current unit
* '''[unit_type]''': the type of the current unit
* '''[unit_race]''': the race of the current unit
* '''[unit_level]''': the level of the current unit
* {{DevFeature}} '''[unit_side]''': the side of the current unit (flag)
* '''[unit_traits]''': the traits of the current unit
* '''[unit_status]''': the status of the current unit
* '''[unit_alignment]''': the alignment of the current unit
* '''[unit_abilities]''': the abilities of the current unit
* '''[unit_hp]''': the HP of the current unit
* '''[unit_xp]''': the XP of the current unit
* '''[unit_moves]''': the moves remaining for the current unit
* '''[unit_weapons]''': the attacks of the current unit
* '''[unit_image]''': the icon for the current unit
* '''[unit_profile]''': the portait for the current unit
* '''[time_of_day]''': the time of day on the current location
* '''[turn]''': the turn number and turn remaining
* '''[gold]''': the gold remaining
* '''[villages]''': the number of villages owned
* '''[num_units]''': the number of units owned
* '''[upkeep]''': the money needed to keep your units every turn
* '''[expenses]''': the money lost each turn when you don't have enough income
* '''[income]''': the income per turn (can be positive)
* '''[terrain]''': the text description of the current terrain
* '''[position]''': the current terrain's position
* '''[side_playing]''': the current playing side (flag)
* '''[observers]''': the current observers

== See Also ==

* [[ThemeSystem]]
* [[Using custom themes in campaigns]]
* [[ReferenceWML]]

[[Category: WML Reference]]

ThemeWML

2008-03-16T17:38:19Z

Noyga: /* [status] */

{{WML Tags}}
== The toplevel [theme] tag ==

Themes are used both for the wesnoth game and the wesnoth editor.
Themes allow flexible configuration of how everything is laid out on-screen.

The only key in '''[theme]''' is '''name'''. This is the name of the theme.

The only tag in '''[theme]''' is '''[resolution]''', but each theme can have multiple [resolution] tags.
The [resolution] tags are scanned until the first one which is of the same or lower resolution than is currently being used is found, and this is used as our theme.
This allows us to define themes to work differently on different resolutions,
and will allow us to support both high and low resolutions elegantly.

The following keys and tags are recognized for [resolution]:

* '''width''', '''height''': dimensions in pixels

All subtags of [resolution] use the following keys:
* '''rect''': defines the rectangle to display on. Parts of a ''rect=a,b,c,d'' clause may be:
** number : absolute positions
** ''='' : same value as the same field in reference rect (alignment with reference)
** +number or -number : for a and b, add this value to reference's c and d respectively (spacing from reference)
; for c and d, add this value to self's a and b (specify by width and height)
** =+number or =-number : add this value to same field in reference rect (eg. consider reference as a container box)
* '''xanchor''', '''yanchor''': control the behavior of how this rectangle changes as the resolution changes.
** '''left'''': its distance from the left side of the screen always remain the same, while changes in the resolution will change its size by the same amount (top for the y axis).
** '''right''': its size always remain the same, as well as its distance to the right side of the screen (bottom for the y axis).
** '''fixed''': its co-ordinates in that axis remain constant
** '''proportional''': its co-ordinates multiplied by the ratio of the resolution being used to the canonical resolution.

== [main_map] ==

defines where the main game display (i.e. all the hexagons and units) is displayed.

== [main_map_border] ==
Defines the border of the main map area. It has the following keys.

* '''border_size''': the size of the border, the value should be between 0.0 and 0.5. The images which are used by default are sized for 0.5. If the border gets smaller the images still need the same size. They're simply cut off at the right spot.
* '''background_image''': the filename of the image to use as background.
* '''tile_image''': the filename of the image to use for the _off^_usr tile. The image in the minimal can't be controlled only the image in the main map. This image must be in the terrain directory and a png image. When specifying the image the 'terrain/' prefix and '.png' suffix _must_ be ommitted.
* '''corner_image_top_left''': filename for the image in the top left corner.
* '''corner_image_bottom_left''': filename for the image in the top left corner.
* '''corner_image_top_right_odd''': filename for the image in the top right corner, if the x value of the corner is odd. This x value is the value seen in game (and thus not in the source).
* '''corner_image_top_right_even''': filename for the image in the top right corner, if the x value of the corner is even. This x value is the value seen in game (and thus not in the source).
* '''corner_image_bottom_right_odd''': filename for the image in the bottom right corner, if the x value of the corner is odd. This x value is the value seen in game (and thus not in the source).
* '''corner_image_bottom_right_even''': filename for the image in the bottom right corner, if the x value of the corner is even. This x value is the value seen in game (and thus not in the source).
* '''border_image_left''': filename for the image at the left border.
* '''border_image_right''': filename for the image at the right border.
* '''border_image_top_odd''': filename for the image at the top border, if the x value of the tile is odd. This x value is the value seen in game (and thus not in the source).
* '''border_image_top_even''': filename for the image at the top border, if the x value of the tile is even. This x value is the value seen in game (and thus not in the source).
* '''border_image_bottom_odd''': filename for the image at the bottom border, if the x value of the tile is odd. This x value is the value seen in game (and thus not in the source).
* '''border_image_bottom_even''': filename for the image at the bottom border, if the x value of the tile is even. This x value is the value seen in game (and thus not in the source).

== [mini_map] ==

Determines where the mini map is displayed

== [panel] ==

Displays an image as a panel on-screen.
* '''image''': the image used for the panel

== [label] ==

Displays a text label on screen.
* '''prefix''': a string that will be printed before the text in all languages
* '''text''': a text string id to be displayed
* '''postfix''': a string that will be printed after the text in all languages
* '''icon''': an image that will be displayed instead of the text if it is available
* '''font_size''': the size of font to use for the label

== [menu] ==

* '''title''': the id of the string to write on the button
* '''title_literal''': a string that will be displayed "as is" in all language after the title
* '''image''': the image to use if available
* '''is_context_menu''': if set to true this menu will not be placed, but displayed on a right click
* '''items''': comma separated list of actions to put in the menu. if there is only one action, it will be executed immediately and no menu will be displayed
** '''cycle''': move to next movable unit
** '''endunitturn''': consume this unit's move and cycle to the next one
** '''leader''': center on the leader
** '''undo''': undo last action
** '''redo''': redo undone action
** '''zoomin''': zoom the map in
** '''zoomout''': zoom the map out
** '''zoomdefault''': return to default zoom
** '''fullscreen''': switch fulscreen mode
** '''accelerated''': switch turbo mode
** '''resistance''': show resistance table of current unit
** '''terraintable''': show terrain table of current unit
** '''describeunit''': show unit description
** '''renameunit''': change unit name
** '''save''': save the game
** '''recruit''': recruit a unit
** '''repeatrecruit''': repeat last recruitement
** '''recall''': recall a unit from previous scenarion
** '''endturn''': end current turn
** '''togglegrid''': toggle grid display
** '''statustable''': show status table
** '''mute''': mute all sounds
** '''speak''': send message to other players
** '''createunit''': debug create a unit on the map
** '''preferences''': open preference dialog
** '''objectives''': show objective window
** '''unitlist''': list units
** '''statistics''': show game statistics
** '''quit''': quit the game
** '''labelterrain''': label current location
** '''clearlabels''': clear all labels on map
** '''showenemymoves''': show grids reachable by the enemy
** '''bestenemymoves''': show grids reachable by the enemy with no zone of control
** '''editnewmap''': editor only start a new map
** '''editloadmap''': editor only loads an existing map
** '''editsavemap''': editor only saves the current map
** '''editsaveas''': editor only saves the current map, let you choose a filename
** '''editsetstartpos''': editor only set a starting position for a team
** '''editfloodfill''': editor only flood the map with a terrain
** '''toggleshroud''': toggle the "moving removes shroud" behaviour
** '''updateshroud'': removes all possible shroud
** '''AUTOSAVES'': expands to a list of all Auto-Save games prior to this one

== [status] ==

This tag describes the Status Table.
This tag contains many other tags, which determine where other game statistics, such as the current turn, and a description of selected units go.
For instance, the [time_of_day] tag will determine where the time of day image goes.
Each subtag of [status] can contain the following attributes

** '''font_size''': the size of font to use for the status
** '''rect''': the rectangle as for the main_map attribute
** '''xanchor''': the x-wise anchoring as for the main_map attribute
** '''yanchor''': the y-wise anchoring as for the main_map attribute
** '''prefix''': the string to display before the actual status, this is the string id for internationalisation
** '''prefix_literal''': a string to put after the prefix, but before the label for all languages.
** '''postfix_literal''': a string to put after the status
** '''postfix''': the string to display after the postfix_literal, this is the string id for internationalisation

the following tags are recognized for [status]:
* '''[unit_description]''': the user description of the current unit
* '''[unit_type]''': the type of the current unit
* '''[unit_race]''': the race of the current unit
* '''[unit_level]''': the level of the current unit
* {{DevFeature}} '''[unit_side]''': the side of the current unit (flag)
* '''[unit_traits]''': the traits of the current unit
* '''[unit_status]''': the status of the current unit
* '''[unit_alignment]''': the alignment of the current unit
* '''[unit_abilities]''': the abilities of the current unit
* '''[unit_hp]''': the HP of the current unit
* '''[unit_xp]''': the XP of the current unit
* '''[unit_moves]''': the moves remaining for the current unit
* '''[unit_weapons]''': the attacks of the current unit
* '''[unit_image]''': the icon for the current unit
* '''[unit_profile]''': the portait for the current unit
* '''[time_of_day]''': the time of day on the current location
* '''[turn]''': the turn number and turn remaining
* '''[gold]''': the gold remaining
* '''[villages]''': the number of villages owned
* '''[num_units]''': the number of units owned
* '''[upkeep]''': the money needed to keep your units every turn
* '''[expenses]''': the money lost each turn when you don't have enough income
* '''[income]''': the income per turn (can be positive)
* '''[terrain]''': the text description of the current terrain
* '''[position]''': the current terrain's position
* '''[side_playing]''': the current playing side (flag)
* '''[observers]''': the current observers

== See Also ==

* [[ThemeSystem]]
* [[Using custom themes in campaigns]]
* [[ReferenceWML]]

[[Category: WML Reference]]

InternalActionsWML

2008-03-16T11:01:06Z

Noyga: /* [switch] {{DevFeature}} */

{{WML Tags}}
== Internal actions ==

Internal actions are actions that WML uses internally that do not directly affect gameplay, for example storing a variable.

The internal actions '''[if]''', '''[while]''', and '''[event]''' describe when/whether sets of actions should be executed.

== [if] ==

Executes different sets of actions based on whether the conditions described in the condition tags are true or not.

Condition tags:
* '''[have_unit]''': a unit passing this filter with >0 HP exists
** [[StandardUnitFilter]] (almost... '''Note:''' does not check for matching units in the recall list)

* '''[have_location]''': a location passing this filter exists
** [[StandardLocationFilter]]

* '''[and]''': If an [and] is present, all must evaluate to true in order for the [if] to evaluate true. Useful as a bracket for complex conditions, but not strictly necessary.
** condition tags as in [if]: if these evaluate to true, [and] evaluates to true.

* '''[or]''': If an [or] is present, one must evaluate to true in order for the [if] to evaluate true. ([[AdvancedConditionalWML|Example]])
** condition tags as in [if]: if these evaluate to true, '''[or]''' evaluates to true.

* '''[not]''': If a [not] is present, none must evaluate to true in order for the [if] to evaluate true.
** condition tags as in [if]: if these evaluate to true, [not] evaluates to false.

* '''[and],[or],[not]''': all top-level filters will support in-order conditional handling of and, or, and not. One important thing to remember is, if you have multiple [or]s, you should not wrap your first conditional statement into an [or] block.

* '''[variable]''': tests something about the value of a WML variable (see [[VariablesWML]])
** '''name''': the name of the variable to test the value of Only one of the following keys should be used for comparing the value of the variable to another value:
** '''equals''': $name is equal (string wise) to this
** '''not_equals''': $name is not equal to this
** '''greater_than''': $name is numerically greater than this
** '''less_than''': $name is less than this
** '''greater_than_equal_to''': $name is not less than this
** '''less_than_equal_to''': $name is not greater than this
** '''numerical_not_equals''': $name is greater than or less than this
** '''numerical_equals''': $name is not greater than or less than this
** '''boolean_equals''': $name has the same boolean value (e.g. off, false, 0, no)
** '''contains''': $name contains this string
** {{DevFeature}} '''boolean_not_equals''': $name has not the same boolean value. Strictly a syntactic shortcut for the following syntax that served its absence in 1.4:
[not]
[variable]
name=...
boolean_equals=...
[/variable]
[/not]

After condition tags:
* '''[then]''': contains a set of action tags which should be executed if all conditions are true, or all conditions in any single [or] are true
* '''[else]''': contains a set of action tags which should be executed if any condition is false, and all [or] tags are false

== [switch] {{DevFeature}} ==

Executes different sets of action based on the value of a variable.
[switch]
variable=foo
[case]
value="A"
... WML if foo=A ...
[/case]
[case]
value="B"
... WML if foo=B ...
[/case]
[else]
... WML if not foo=A nor foo=B ...
[/else]
[/switch]

* '''variable''': name of the variable to check.
* '''[case]''': Case block. Contains:
** '''value''': value to test the variable against.
** the action WML to execute if the variable matches the value (rest of the block).
* '''[else]''': Block of action WML to execute if no '''[case]''' block matches.

== [while] ==

Executes commands if all conditions are true.
Continues to execute them until a condition is not true.

Executes a maximum of 1024 iterations per invocation.
Condition tags are the same as for [if]

After condition tags:
* '''[do]''': contains actions that should be executed repeatedly until some condition is false.

The '''[while]''' tag is useful for iterating over an array.
An array is a list of values.
The ''number''th value in the array '''array''' is stored in the WML variable '''''array''[number]'''.
Note that if '''number''' is the value of the variable '''variable''',
the expression '''$''array''[$variable]''' will return the ''number''th value in ''array''.
The macros 'FOREACH' and 'NEXT' ([[UtilWML]]) can be used to iterate over an array;
i.e. run a set of actions once per element of the array.

=== {FOREACH} ===
If you wish to use a "for-each" iteration format (useful for example when you want to do an iteration for each row in a table) you can use the [http://www.wesnoth.org/misc/macro-reference.xhtml FOREACH] and [http://www.wesnoth.org/misc/macro-reference.xhtml NEXT] prededined macros.

=== {REPEAT} ===
You can use the REPEAT macro to perform a quick iteration for a number of times you specify.

== [event] ==

This adds a new event to the scenario.
The event is in the normal format for an '''[event]''' tag (See [[EventWML]]).
This is useful if you want an event that can only be triggered when a prior event is fulfilled

These tags describe actions that affect the values of WML variables
(see [[VariablesWML]] for information on WML variables,
and [[UtilWML]] for convenient macro shortcuts for some of these):
* '''[set_variable]''': manipulates a WML variable. {{Note:Predefined Macro|VARIABLE}}
** '''name''': the name of the variable to manipulate
** '''value''': set the variable to the given value (can be numeric or string). This only interprets dollars signs if it is the very first character, and then the entire value must be a simple variable name. (in 1.3.2, has the same effect as format. Use literal for no substitution)
** '''literal''': set the variable to the given value (can be numeric or string). This does not interpret any dollars signs.
** '''format''': set the variable to the given value. Interprets the dollar sign to a higher degree than most actions. (see [[VariablesWML]])
** '''to_variable''': Fully processes its value as in ''format'', and then gets the variable with that name.
** '''add''': add the given amount to the variable. To subtract, add a negative number.
** '''multiply''': multiply the variable by the given number. To divide, multiply by the inverse eg: 4/2 = 4 * 1/2 = 4 * 0.5. To negate, multiply by -1. The result is an integer.
** '''divide''': divide the variable by the given number. The result is an integer.
** '''modulo''': returns the remainder of an integer division. Both variables need to be an integer, the result is also an integer. eg 5 % 2 = 1.
** '''random''': the variable will be randomly set. You may provide a comma separated list of possibilities, e.g. 'random=Bob,Bill,Bella'. You may provide a range of numbers (integers), e.g. 'random=3..5'. You may combine these, e.g. 'random=100,1..9', in which case there would be 1/10th chance of getting 100, just like for each of 1 to 9. Dollars signs are only normally interpreted here, so it is harder to have a dynamically determined range. You would need to create the random-string with ''format''.
** '''rand''': does the same as random, but has better MP support. See [[BuildingMultiplayerExamples]] for more info on the MP case. '''It is highly recommended that you use this feature for randomization.'''
** '''time=stamp''': Retrieves a timestamp in milliseconds since wesnoth was started, can be used as timing aid. Don't try to use this as random value in MP since it will cause an OOS.
** {{DevFeature}} '''string_length''': Retrieves the length in characters of the string passed as this attribute's value; such string is parsed and variable substitution applied automatically (see [[VariablesWML]] for details).
** {{DevFeature}} '''[join]''' joins an array of strings to a textual list
***variable: name of the array
***key: array[$i].key to look for the strings
***separator: separator to connect the elements
***remove_empty: wether to ignore empty elements

* {{DevFeature}} '''[set_variables]''': manipulates a WML array
** '''name''': the name of the container to manipulate
** '''mode''': one of the following values:
***replace: will clean the array '''name''' and replace it with given data
***append: will append given data to the current array
***merge: will merge in the given data into '''name'''
** '''to_variable''': data will be set to the given array
** '''[value]''': the WML inside the [value] tags will be stored in data, variables will be interpolated directly, use $| in order to escape the $ sign, you can store arrays of WML by supplying multiple [value] tags
** '''[literal]''': same as '''[value]''', but variables will not be substituted, '''[literal]''' and '''[value]''' can not be used in the same [set_variables] tag, i.e. you can not create arrays by piling a mix of '''[value]''' and '''[literal]''' tags
**'''[split]''' splits a textual list into an array which will then be set to data
***list: textual list to split
***key: array[$i].key to put the elements in
***separator: separator to separate the elements
***remove_empty: wether to ignore empty elements

* '''[store_unit]''': stores details about units into game variables. Common usage is to manipulate a unit by using [store_unit] to store it into a variable, followed by manipulation of the variable, and then [unstore_unit] to re-create the unit with the modified variables. Note: stored units also exist on the field, and modifying the stored variable will not automatically change the stats of the units. You need to use [unstore_unit]. See also [unstore_unit], [[DirectActionsWML]], and '''FOREACH''', [[UtilWML]]
** '''[filter]''': [[StandardUnitFilter]] all units matching this filter will be stored. If there are multiple units, they will be stored into an array of variables.
** '''variable''': the name of the variable into which to store the unit(s)
** '''mode''': defaults to ''always_clear'', which clears the variable, whether or not a match is found. If mode is set to ''replace'', the variable will only be cleared if a match is found. If mode is set to ''append'', the variable will not be cleared.
** '''kill''': if 'yes' the units that are stored will be removed from play. This is useful for instance to remove access to a player's recall list, with the intent to restore the recall list later.
:When a unit is stored, the following values may be manipulated with '''[set_variable]'''
:* description
:* experience
:* facing
:* gender
:* canrecruit
:* overlays
:* goto_x
:* goto_y
:* hitpoints
:* moves
:* resting
:* side
:* type
:* unrenamable
:* upkeep
:* user_description
:* x
:* y
:* [variables]
:* [status]
:* [modifications]
Variables, status, and modifications are children of the stored unit variable. Example:
[set_variable]
name=unit_store.status.poisoned
value=yes
[/set_variable]

:All keys and tags in the unit definition may be manipulated, including some others. Here is a sample list. If you have a doubt about what keys are valid or what the valid value range is for each key, code a [store_unit] event, save the game, and examine what keys are in the file.
:* advanceto
:* alignment
:* alpha
:* attacks_left
:* canrecruit
:* controller
:* cost
:* description
:* experience
:* facing
:* flying
:* fog
:* gender
:* get_hit_sound
:* gold
:* goto_x
:* goto_y
:* hitpoints
:* id
:* image
:* image_defensive
:* income
:* language_name (same as the name key in the unit config)
:* level
:* max_attacks
:* max_experience
:* max_hitpoints
:* max_moves
:* movement
:* movement_type
:* moves
:* race
:* resting
:* shroud
:* side
:* team_name
:* type
:* unit_description
:* unrenamable
:* usage
:* value
:* x
:* y
:* zoc
:* [advancement]
:* [/advancement]
:* [movement_costs]
:* [/movement_costs]
:* [defense]
:* [/defense]
:* [resistance]
:* [/resistance]
:* [variables]
:* [/variables]
:* [status]
:* [/status]
:* [attack]
:* [/attack]
:* [modifications_description]
:* [/modifications_description]
:* [modifications]
:* [/modifications]

* '''[store_starting_location]''': Stores the starting location of a side's leader in a variable. The variable is a composite type which will have members 'x', 'y', and 'terrain' (the terrain type for a starting location is always 'K' unless it has been changed)
** '''side''': the side whose starting location is to be stored
** '''variable''': (default='location'): the name of the variable to store the location in
* '''[store_locations]''': Stores a series of locations that pass certain criteria into an array. Each member of the array has members 'x' and 'y' (the position) and 'terrain' (the terrain type).
** [[StandardLocationFilter]]: a location or location range which specifies the locations to store. You must specify this or no locations will be stored.
** '''variable''': the name of the variable (array) into which to store the locations
** '''terrain''': a comma-sperated list of terrain codes. (See [[TerrainCodesWML]] for possible values.) If present, locations will only be chosen if the code for the terrain type of that location is listed.
** '''radius''': if present, any locations which are within '''radius''' hexes of the location filter will also be stored
** '''[filter]''': [[StandardUnitFilter]] only locations with units on them that match the filter will be stored. Use a blank filter to only store locations with units.
* '''[store_villages]''': Stores a series of locations of villages that pass certain criteria into an array. Each member of the array has members 'x' and 'y' (the position) and 'terrain' (the terrain type).
** '''owner_side''': a side number. If present, only villages owned by this side will be choosen. If owner_side=0, store the unowned villages.
** '''variable''': the name of the variable (array) into which to store the locations
** '''terrain''': a series of terrain characters. (See [[TerrainLettersWML]] for possible values.) If present, villages will only be chosen if the terrain code of the terrain type of that location is listed. You may give a comma separated list of terrains.
** '''side''': (default=1) the side for which the gold should be stored
** '''variable''': (default='gold') the name of the variable to store the gold in
* '''[store_side]''': stores information about a certain side in a variable. The variable will contain the member variables 'name', 'team_name', 'gold' and 'income', 'fog', 'shroud', 'user_team_name', 'colour', 'controller', 'village_gold' and 'recruit'.)
** '''side''': the side whose information should be stored
** '''variable''': the name of the variable to store the information in
* '''[clear_variable]''': This will delete the given variable or array. This is good to use to clean up the set of variables -- e.g. a well-behaved scenario will delete any variables that shouldn't be kept for the next scenario before the end of the scenario. Tags and variables of stored units can also be cleared, meaning that [trait]s and [object]s, for example, can be removed.
** '''name''': the name of the variable to clear.
* '''[role]''': tries to find a unit to assign a role to. This is useful if you want to choose a non-major character to say some things during the game. Once a role is assigned, you can use '''role=''' in a unit filter to identify the unit with that role (See [[FilterWML]]). However, there is no guarantee that roles will ever be assigned. You can use '''[have_unit]''' (see [if]) to see whether a role was assigned. This tag uses a [[StandardUnitFilter]] with the modification to order the search by type, mark only the first unit found with the role, and the role attribute is not used in the search. If for some reason you want to search for units that have or don't have existing roles, you can use one or more [not] filters. The will check recall lists in addition to units on the map. In normal use, you will probably want to include a ''side'' attribute to force the unit to be on a particular side.
** '''role''': the value to store as the unit's role. This role is not used in the [[StandardUnitFilter]] when doing the search for the unit to assign this role to.
** '''type''': a comma-separated list of possible types the unit can be. If any types are given, then units will be searched by type in the order listed. If no type is given, then no particular order with respect to type is guaranteed.
* {{DevFeature}} '''[store_map_dimensions]''': Stores the map dimensions in a variable.
** '''variable''': the name of the variable where the values will be saved into. If it is skipped, a variable 'map_size' is used, and its contents overridden, if they existed already. The result is a container variable, with members ''width'' and ''height''.

== See Also ==
* [[VariablesWML]]
* [[DirectActionsWML]]
* [[InterfaceActionsWML]]
* [[EventWML]]
* [[ReferenceWML]]

[[Category: WML Reference]]

InternalActionsWML

2008-03-16T10:57:30Z

Noyga: /* [switch] {{DevFeature}} */

{{WML Tags}}
== Internal actions ==

Internal actions are actions that WML uses internally that do not directly affect gameplay, for example storing a variable.

The internal actions '''[if]''', '''[while]''', and '''[event]''' describe when/whether sets of actions should be executed.

== [if] ==

Executes different sets of actions based on whether the conditions described in the condition tags are true or not.

Condition tags:
* '''[have_unit]''': a unit passing this filter with >0 HP exists
** [[StandardUnitFilter]] (almost... '''Note:''' does not check for matching units in the recall list)

* '''[have_location]''': a location passing this filter exists
** [[StandardLocationFilter]]

* '''[and]''': If an [and] is present, all must evaluate to true in order for the [if] to evaluate true. Useful as a bracket for complex conditions, but not strictly necessary.
** condition tags as in [if]: if these evaluate to true, [and] evaluates to true.

* '''[or]''': If an [or] is present, one must evaluate to true in order for the [if] to evaluate true. ([[AdvancedConditionalWML|Example]])
** condition tags as in [if]: if these evaluate to true, '''[or]''' evaluates to true.

* '''[not]''': If a [not] is present, none must evaluate to true in order for the [if] to evaluate true.
** condition tags as in [if]: if these evaluate to true, [not] evaluates to false.

* '''[and],[or],[not]''': all top-level filters will support in-order conditional handling of and, or, and not. One important thing to remember is, if you have multiple [or]s, you should not wrap your first conditional statement into an [or] block.

* '''[variable]''': tests something about the value of a WML variable (see [[VariablesWML]])
** '''name''': the name of the variable to test the value of Only one of the following keys should be used for comparing the value of the variable to another value:
** '''equals''': $name is equal (string wise) to this
** '''not_equals''': $name is not equal to this
** '''greater_than''': $name is numerically greater than this
** '''less_than''': $name is less than this
** '''greater_than_equal_to''': $name is not less than this
** '''less_than_equal_to''': $name is not greater than this
** '''numerical_not_equals''': $name is greater than or less than this
** '''numerical_equals''': $name is not greater than or less than this
** '''boolean_equals''': $name has the same boolean value (e.g. off, false, 0, no)
** '''contains''': $name contains this string
** {{DevFeature}} '''boolean_not_equals''': $name has not the same boolean value. Strictly a syntactic shortcut for the following syntax that served its absence in 1.4:
[not]
[variable]
name=...
boolean_equals=...
[/variable]
[/not]

After condition tags:
* '''[then]''': contains a set of action tags which should be executed if all conditions are true, or all conditions in any single [or] are true
* '''[else]''': contains a set of action tags which should be executed if any condition is false, and all [or] tags are false

== [switch] {{DevFeature}} ==

Executes different sets of action based on the value of a variable.
[switch]
variable=foo
[case]
value="A"
... WML if foo=A ...
[/case]
[case]
value="B"
... WML if foo=B ...
[/case]
[else]
... WML if not foo=A nor foo=B ...
[/else]
[/switch]

* '''variable''': variable to check.
* '''[case]''': Case block. Contains:
** '''value''': the value to test the variable against.
** the action WML to execute if the variable matches the value (rest of the block).
* '''[else]''': Block of action WML to execute if no '''[case]''' block matches.

== [while] ==

Executes commands if all conditions are true.
Continues to execute them until a condition is not true.

Executes a maximum of 1024 iterations per invocation.
Condition tags are the same as for [if]

After condition tags:
* '''[do]''': contains actions that should be executed repeatedly until some condition is false.

The '''[while]''' tag is useful for iterating over an array.
An array is a list of values.
The ''number''th value in the array '''array''' is stored in the WML variable '''''array''[number]'''.
Note that if '''number''' is the value of the variable '''variable''',
the expression '''$''array''[$variable]''' will return the ''number''th value in ''array''.
The macros 'FOREACH' and 'NEXT' ([[UtilWML]]) can be used to iterate over an array;
i.e. run a set of actions once per element of the array.

=== {FOREACH} ===
If you wish to use a "for-each" iteration format (useful for example when you want to do an iteration for each row in a table) you can use the [http://www.wesnoth.org/misc/macro-reference.xhtml FOREACH] and [http://www.wesnoth.org/misc/macro-reference.xhtml NEXT] prededined macros.

=== {REPEAT} ===
You can use the REPEAT macro to perform a quick iteration for a number of times you specify.

== [event] ==

This adds a new event to the scenario.
The event is in the normal format for an '''[event]''' tag (See [[EventWML]]).
This is useful if you want an event that can only be triggered when a prior event is fulfilled

These tags describe actions that affect the values of WML variables
(see [[VariablesWML]] for information on WML variables,
and [[UtilWML]] for convenient macro shortcuts for some of these):
* '''[set_variable]''': manipulates a WML variable. {{Note:Predefined Macro|VARIABLE}}
** '''name''': the name of the variable to manipulate
** '''value''': set the variable to the given value (can be numeric or string). This only interprets dollars signs if it is the very first character, and then the entire value must be a simple variable name. (in 1.3.2, has the same effect as format. Use literal for no substitution)
** '''literal''': set the variable to the given value (can be numeric or string). This does not interpret any dollars signs.
** '''format''': set the variable to the given value. Interprets the dollar sign to a higher degree than most actions. (see [[VariablesWML]])
** '''to_variable''': Fully processes its value as in ''format'', and then gets the variable with that name.
** '''add''': add the given amount to the variable. To subtract, add a negative number.
** '''multiply''': multiply the variable by the given number. To divide, multiply by the inverse eg: 4/2 = 4 * 1/2 = 4 * 0.5. To negate, multiply by -1. The result is an integer.
** '''divide''': divide the variable by the given number. The result is an integer.
** '''modulo''': returns the remainder of an integer division. Both variables need to be an integer, the result is also an integer. eg 5 % 2 = 1.
** '''random''': the variable will be randomly set. You may provide a comma separated list of possibilities, e.g. 'random=Bob,Bill,Bella'. You may provide a range of numbers (integers), e.g. 'random=3..5'. You may combine these, e.g. 'random=100,1..9', in which case there would be 1/10th chance of getting 100, just like for each of 1 to 9. Dollars signs are only normally interpreted here, so it is harder to have a dynamically determined range. You would need to create the random-string with ''format''.
** '''rand''': does the same as random, but has better MP support. See [[BuildingMultiplayerExamples]] for more info on the MP case. '''It is highly recommended that you use this feature for randomization.'''
** '''time=stamp''': Retrieves a timestamp in milliseconds since wesnoth was started, can be used as timing aid. Don't try to use this as random value in MP since it will cause an OOS.
** {{DevFeature}} '''string_length''': Retrieves the length in characters of the string passed as this attribute's value; such string is parsed and variable substitution applied automatically (see [[VariablesWML]] for details).
** {{DevFeature}} '''[join]''' joins an array of strings to a textual list
***variable: name of the array
***key: array[$i].key to look for the strings
***separator: separator to connect the elements
***remove_empty: wether to ignore empty elements

* {{DevFeature}} '''[set_variables]''': manipulates a WML array
** '''name''': the name of the container to manipulate
** '''mode''': one of the following values:
***replace: will clean the array '''name''' and replace it with given data
***append: will append given data to the current array
***merge: will merge in the given data into '''name'''
** '''to_variable''': data will be set to the given array
** '''[value]''': the WML inside the [value] tags will be stored in data, variables will be interpolated directly, use $| in order to escape the $ sign, you can store arrays of WML by supplying multiple [value] tags
** '''[literal]''': same as '''[value]''', but variables will not be substituted, '''[literal]''' and '''[value]''' can not be used in the same [set_variables] tag, i.e. you can not create arrays by piling a mix of '''[value]''' and '''[literal]''' tags
**'''[split]''' splits a textual list into an array which will then be set to data
***list: textual list to split
***key: array[$i].key to put the elements in
***separator: separator to separate the elements
***remove_empty: wether to ignore empty elements

* '''[store_unit]''': stores details about units into game variables. Common usage is to manipulate a unit by using [store_unit] to store it into a variable, followed by manipulation of the variable, and then [unstore_unit] to re-create the unit with the modified variables. Note: stored units also exist on the field, and modifying the stored variable will not automatically change the stats of the units. You need to use [unstore_unit]. See also [unstore_unit], [[DirectActionsWML]], and '''FOREACH''', [[UtilWML]]
** '''[filter]''': [[StandardUnitFilter]] all units matching this filter will be stored. If there are multiple units, they will be stored into an array of variables.
** '''variable''': the name of the variable into which to store the unit(s)
** '''mode''': defaults to ''always_clear'', which clears the variable, whether or not a match is found. If mode is set to ''replace'', the variable will only be cleared if a match is found. If mode is set to ''append'', the variable will not be cleared.
** '''kill''': if 'yes' the units that are stored will be removed from play. This is useful for instance to remove access to a player's recall list, with the intent to restore the recall list later.
:When a unit is stored, the following values may be manipulated with '''[set_variable]'''
:* description
:* experience
:* facing
:* gender
:* canrecruit
:* overlays
:* goto_x
:* goto_y
:* hitpoints
:* moves
:* resting
:* side
:* type
:* unrenamable
:* upkeep
:* user_description
:* x
:* y
:* [variables]
:* [status]
:* [modifications]
Variables, status, and modifications are children of the stored unit variable. Example:
[set_variable]
name=unit_store.status.poisoned
value=yes
[/set_variable]

:All keys and tags in the unit definition may be manipulated, including some others. Here is a sample list. If you have a doubt about what keys are valid or what the valid value range is for each key, code a [store_unit] event, save the game, and examine what keys are in the file.
:* advanceto
:* alignment
:* alpha
:* attacks_left
:* canrecruit
:* controller
:* cost
:* description
:* experience
:* facing
:* flying
:* fog
:* gender
:* get_hit_sound
:* gold
:* goto_x
:* goto_y
:* hitpoints
:* id
:* image
:* image_defensive
:* income
:* language_name (same as the name key in the unit config)
:* level
:* max_attacks
:* max_experience
:* max_hitpoints
:* max_moves
:* movement
:* movement_type
:* moves
:* race
:* resting
:* shroud
:* side
:* team_name
:* type
:* unit_description
:* unrenamable
:* usage
:* value
:* x
:* y
:* zoc
:* [advancement]
:* [/advancement]
:* [movement_costs]
:* [/movement_costs]
:* [defense]
:* [/defense]
:* [resistance]
:* [/resistance]
:* [variables]
:* [/variables]
:* [status]
:* [/status]
:* [attack]
:* [/attack]
:* [modifications_description]
:* [/modifications_description]
:* [modifications]
:* [/modifications]

* '''[store_starting_location]''': Stores the starting location of a side's leader in a variable. The variable is a composite type which will have members 'x', 'y', and 'terrain' (the terrain type for a starting location is always 'K' unless it has been changed)
** '''side''': the side whose starting location is to be stored
** '''variable''': (default='location'): the name of the variable to store the location in
* '''[store_locations]''': Stores a series of locations that pass certain criteria into an array. Each member of the array has members 'x' and 'y' (the position) and 'terrain' (the terrain type).
** [[StandardLocationFilter]]: a location or location range which specifies the locations to store. You must specify this or no locations will be stored.
** '''variable''': the name of the variable (array) into which to store the locations
** '''terrain''': a comma-sperated list of terrain codes. (See [[TerrainCodesWML]] for possible values.) If present, locations will only be chosen if the code for the terrain type of that location is listed.
** '''radius''': if present, any locations which are within '''radius''' hexes of the location filter will also be stored
** '''[filter]''': [[StandardUnitFilter]] only locations with units on them that match the filter will be stored. Use a blank filter to only store locations with units.
* '''[store_villages]''': Stores a series of locations of villages that pass certain criteria into an array. Each member of the array has members 'x' and 'y' (the position) and 'terrain' (the terrain type).
** '''owner_side''': a side number. If present, only villages owned by this side will be choosen. If owner_side=0, store the unowned villages.
** '''variable''': the name of the variable (array) into which to store the locations
** '''terrain''': a series of terrain characters. (See [[TerrainLettersWML]] for possible values.) If present, villages will only be chosen if the terrain code of the terrain type of that location is listed. You may give a comma separated list of terrains.
** '''side''': (default=1) the side for which the gold should be stored
** '''variable''': (default='gold') the name of the variable to store the gold in
* '''[store_side]''': stores information about a certain side in a variable. The variable will contain the member variables 'name', 'team_name', 'gold' and 'income', 'fog', 'shroud', 'user_team_name', 'colour', 'controller', 'village_gold' and 'recruit'.)
** '''side''': the side whose information should be stored
** '''variable''': the name of the variable to store the information in
* '''[clear_variable]''': This will delete the given variable or array. This is good to use to clean up the set of variables -- e.g. a well-behaved scenario will delete any variables that shouldn't be kept for the next scenario before the end of the scenario. Tags and variables of stored units can also be cleared, meaning that [trait]s and [object]s, for example, can be removed.
** '''name''': the name of the variable to clear.
* '''[role]''': tries to find a unit to assign a role to. This is useful if you want to choose a non-major character to say some things during the game. Once a role is assigned, you can use '''role=''' in a unit filter to identify the unit with that role (See [[FilterWML]]). However, there is no guarantee that roles will ever be assigned. You can use '''[have_unit]''' (see [if]) to see whether a role was assigned. This tag uses a [[StandardUnitFilter]] with the modification to order the search by type, mark only the first unit found with the role, and the role attribute is not used in the search. If for some reason you want to search for units that have or don't have existing roles, you can use one or more [not] filters. The will check recall lists in addition to units on the map. In normal use, you will probably want to include a ''side'' attribute to force the unit to be on a particular side.
** '''role''': the value to store as the unit's role. This role is not used in the [[StandardUnitFilter]] when doing the search for the unit to assign this role to.
** '''type''': a comma-separated list of possible types the unit can be. If any types are given, then units will be searched by type in the order listed. If no type is given, then no particular order with respect to type is guaranteed.
* {{DevFeature}} '''[store_map_dimensions]''': Stores the map dimensions in a variable.
** '''variable''': the name of the variable where the values will be saved into. If it is skipped, a variable 'map_size' is used, and its contents overridden, if they existed already. The result is a container variable, with members ''width'' and ''height''.

== See Also ==
* [[VariablesWML]]
* [[DirectActionsWML]]
* [[InterfaceActionsWML]]
* [[EventWML]]
* [[ReferenceWML]]

[[Category: WML Reference]]

InternalActionsWML

2008-03-16T00:13:53Z

Noyga: /* [switch] {{DevFeature}} */

{{WML Tags}}
== Internal actions ==

Internal actions are actions that WML uses internally that do not directly affect gameplay, for example storing a variable.

The internal actions '''[if]''', '''[while]''', and '''[event]''' describe when/whether sets of actions should be executed.

== [if] ==

Executes different sets of actions based on whether the conditions described in the condition tags are true or not.

Condition tags:
* '''[have_unit]''': a unit passing this filter with >0 HP exists
** [[StandardUnitFilter]] (almost... '''Note:''' does not check for matching units in the recall list)

* '''[have_location]''': a location passing this filter exists
** [[StandardLocationFilter]]

* '''[and]''': If an [and] is present, all must evaluate to true in order for the [if] to evaluate true. Useful as a bracket for complex conditions, but not strictly necessary.
** condition tags as in [if]: if these evaluate to true, [and] evaluates to true.

* '''[or]''': If an [or] is present, one must evaluate to true in order for the [if] to evaluate true. ([[AdvancedConditionalWML|Example]])
** condition tags as in [if]: if these evaluate to true, '''[or]''' evaluates to true.

* '''[not]''': If a [not] is present, none must evaluate to true in order for the [if] to evaluate true.
** condition tags as in [if]: if these evaluate to true, [not] evaluates to false.

* '''[and],[or],[not]''': all top-level filters will support in-order conditional handling of and, or, and not. One important thing to remember is, if you have multiple [or]s, you should not wrap your first conditional statement into an [or] block.

* '''[variable]''': tests something about the value of a WML variable (see [[VariablesWML]])
** '''name''': the name of the variable to test the value of Only one of the following keys should be used for comparing the value of the variable to another value:
** '''equals''': $name is equal (string wise) to this
** '''not_equals''': $name is not equal to this
** '''greater_than''': $name is numerically greater than this
** '''less_than''': $name is less than this
** '''greater_than_equal_to''': $name is not less than this
** '''less_than_equal_to''': $name is not greater than this
** '''numerical_not_equals''': $name is greater than or less than this
** '''numerical_equals''': $name is not greater than or less than this
** '''boolean_equals''': $name has the same boolean value (e.g. off, false, 0, no)
** '''contains''': $name contains this string
** {{DevFeature}} '''boolean_not_equals''': $name has not the same boolean value. Strictly a syntactic shortcut for the following syntax that served its absence in 1.4:
[not]
[variable]
name=...
boolean_equals=...
[/variable]
[/not]

After condition tags:
* '''[then]''': contains a set of action tags which should be executed if all conditions are true, or all conditions in any single [or] are true
* '''[else]''': contains a set of action tags which should be executed if any condition is false, and all [or] tags are false

== [switch] {{DevFeature}} ==

Executes different sets of action based ont the value of a variable.
[switch]
variable=foo
[case]
value="A"
... WML if foo=A ...
[/case]
[case]
value="B"
... WML if foo=B ...
[/case]
[else]
... WML if not foo=A nor foo=B ...
[/else]
[/switch]

* '''variable''': variable to check.
* '''[case]''': Case block. Contains:
** '''value''': the value to test the variable against.
** the action WML to execute if the variable matches the value (rest of the block).
* '''[else]''': Block of action WML to execute if no '''[case]''' block matches.

== [while] ==

Executes commands if all conditions are true.
Continues to execute them until a condition is not true.

Executes a maximum of 1024 iterations per invocation.
Condition tags are the same as for [if]

After condition tags:
* '''[do]''': contains actions that should be executed repeatedly until some condition is false.

The '''[while]''' tag is useful for iterating over an array.
An array is a list of values.
The ''number''th value in the array '''array''' is stored in the WML variable '''''array''[number]'''.
Note that if '''number''' is the value of the variable '''variable''',
the expression '''$''array''[$variable]''' will return the ''number''th value in ''array''.
The macros 'FOREACH' and 'NEXT' ([[UtilWML]]) can be used to iterate over an array;
i.e. run a set of actions once per element of the array.

=== {FOREACH} ===
If you wish to use a "for-each" iteration format (useful for example when you want to do an iteration for each row in a table) you can use the [http://www.wesnoth.org/misc/macro-reference.xhtml FOREACH] and [http://www.wesnoth.org/misc/macro-reference.xhtml NEXT] prededined macros.

=== {REPEAT} ===
You can use the REPEAT macro to perform a quick iteration for a number of times you specify.

== [event] ==

This adds a new event to the scenario.
The event is in the normal format for an '''[event]''' tag (See [[EventWML]]).
This is useful if you want an event that can only be triggered when a prior event is fulfilled

These tags describe actions that affect the values of WML variables
(see [[VariablesWML]] for information on WML variables,
and [[UtilWML]] for convenient macro shortcuts for some of these):
* '''[set_variable]''': manipulates a WML variable. {{Note:Predefined Macro|VARIABLE}}
** '''name''': the name of the variable to manipulate
** '''value''': set the variable to the given value (can be numeric or string). This only interprets dollars signs if it is the very first character, and then the entire value must be a simple variable name. (in 1.3.2, has the same effect as format. Use literal for no substitution)
** '''literal''': set the variable to the given value (can be numeric or string). This does not interpret any dollars signs.
** '''format''': set the variable to the given value. Interprets the dollar sign to a higher degree than most actions. (see [[VariablesWML]])
** '''to_variable''': Fully processes its value as in ''format'', and then gets the variable with that name.
** '''add''': add the given amount to the variable. To subtract, add a negative number.
** '''multiply''': multiply the variable by the given number. To divide, multiply by the inverse eg: 4/2 = 4 * 1/2 = 4 * 0.5. To negate, multiply by -1. The result is an integer.
** '''divide''': divide the variable by the given number. The result is an integer.
** '''modulo''': returns the remainder of an integer division. Both variables need to be an integer, the result is also an integer. eg 5 % 2 = 1.
** '''random''': the variable will be randomly set. You may provide a comma separated list of possibilities, e.g. 'random=Bob,Bill,Bella'. You may provide a range of numbers (integers), e.g. 'random=3..5'. You may combine these, e.g. 'random=100,1..9', in which case there would be 1/10th chance of getting 100, just like for each of 1 to 9. Dollars signs are only normally interpreted here, so it is harder to have a dynamically determined range. You would need to create the random-string with ''format''.
** '''rand''': does the same as random, but has better MP support. See [[BuildingMultiplayerExamples]] for more info on the MP case. '''It is highly recommended that you use this feature for randomization.'''
** '''time=stamp''': Retrieves a timestamp in milliseconds since wesnoth was started, can be used as timing aid. Don't try to use this as random value in MP since it will cause an OOS.
** {{DevFeature}} '''string_length''': Retrieves the length in characters of the string passed as this attribute's value; such string is parsed and variable substitution applied automatically (see [[VariablesWML]] for details).

* '''[store_unit]''': stores details about units into game variables. Common usage is to manipulate a unit by using [store_unit] to store it into a variable, followed by manipulation of the variable, and then [unstore_unit] to re-create the unit with the modified variables. Note: stored units also exist on the field, and modifying the stored variable will not automatically change the stats of the units. You need to use [unstore_unit]. See also [unstore_unit], [[DirectActionsWML]], and '''FOREACH''', [[UtilWML]]
** '''[filter]''': [[StandardUnitFilter]] all units matching this filter will be stored. If there are multiple units, they will be stored into an array of variables.
** '''variable''': the name of the variable into which to store the unit(s)
** '''mode''': defaults to ''always_clear'', which clears the variable, whether or not a match is found. If mode is set to ''replace'', the variable will only be cleared if a match is found. If mode is set to ''append'', the variable will not be cleared.
** '''kill''': if 'yes' the units that are stored will be removed from play. This is useful for instance to remove access to a player's recall list, with the intent to restore the recall list later.
:When a unit is stored, the following values may be manipulated with '''[set_variable]'''
:* description
:* experience
:* facing
:* gender
:* canrecruit
:* overlays
:* goto_x
:* goto_y
:* hitpoints
:* moves
:* resting
:* side
:* type
:* unrenamable
:* upkeep
:* user_description
:* x
:* y
:* [variables]
:* [status]
:* [modifications]
Variables, status, and modifications are children of the stored unit variable. Example:
[set_variable]
name=unit_store.status.poisoned
value=yes
[/set_variable]

:All keys and tags in the unit definition may be manipulated, including some others. Here is a sample list. If you have a doubt about what keys are valid or what the valid value range is for each key, code a [store_unit] event, save the game, and examine what keys are in the file.
:* advanceto
:* alignment
:* alpha
:* attacks_left
:* canrecruit
:* controller
:* cost
:* description
:* experience
:* facing
:* flying
:* fog
:* gender
:* get_hit_sound
:* gold
:* goto_x
:* goto_y
:* hitpoints
:* id
:* image
:* image_defensive
:* income
:* language_name (same as the name key in the unit config)
:* level
:* max_attacks
:* max_experience
:* max_hitpoints
:* max_moves
:* movement
:* movement_type
:* moves
:* race
:* resting
:* shroud
:* side
:* team_name
:* type
:* unit_description
:* unrenamable
:* usage
:* value
:* x
:* y
:* zoc
:* [advancement]
:* [/advancement]
:* [movement_costs]
:* [/movement_costs]
:* [defense]
:* [/defense]
:* [resistance]
:* [/resistance]
:* [variables]
:* [/variables]
:* [status]
:* [/status]
:* [attack]
:* [/attack]
:* [modifications_description]
:* [/modifications_description]
:* [modifications]
:* [/modifications]

* '''[store_starting_location]''': Stores the starting location of a side's leader in a variable. The variable is a composite type which will have members 'x', 'y', and 'terrain' (the terrain type for a starting location is always 'K' unless it has been changed)
** '''side''': the side whose starting location is to be stored
** '''variable''': (default='location'): the name of the variable to store the location in
* '''[store_locations]''': Stores a series of locations that pass certain criteria into an array. Each member of the array has members 'x' and 'y' (the position) and 'terrain' (the terrain type).
** [[StandardLocationFilter]]: a location or location range which specifies the locations to store. You must specify this or no locations will be stored.
** '''variable''': the name of the variable (array) into which to store the locations
** '''terrain''': a comma-sperated list of terrain codes. (See [[TerrainCodesWML]] for possible values.) If present, locations will only be chosen if the code for the terrain type of that location is listed.
** '''radius''': if present, any locations which are within '''radius''' hexes of the location filter will also be stored
** '''[filter]''': [[StandardUnitFilter]] only locations with units on them that match the filter will be stored. Use a blank filter to only store locations with units.
* '''[store_villages]''': Stores a series of locations of villages that pass certain criteria into an array. Each member of the array has members 'x' and 'y' (the position) and 'terrain' (the terrain type).
** '''owner_side''': a side number. If present, only villages owned by this side will be choosen. If owner_side=0, store the unowned villages.
** '''variable''': the name of the variable (array) into which to store the locations
** '''terrain''': a series of terrain characters. (See [[TerrainLettersWML]] for possible values.) If present, villages will only be chosen if the terrain code of the terrain type of that location is listed. You may give a comma separated list of terrains.
** '''side''': (default=1) the side for which the gold should be stored
** '''variable''': (default='gold') the name of the variable to store the gold in
* '''[store_side]''': stores information about a certain side in a variable. The variable will contain the member variables 'name', 'team_name', 'gold' and 'income', 'fog', 'shroud', 'user_team_name', 'colour', 'controller', 'village_gold' and 'recruit'.)
** '''side''': the side whose information should be stored
** '''variable''': the name of the variable to store the information in
* '''[clear_variable]''': This will delete the given variable or array. This is good to use to clean up the set of variables -- e.g. a well-behaved scenario will delete any variables that shouldn't be kept for the next scenario before the end of the scenario. Tags and variables of stored units can also be cleared, meaning that [trait]s and [object]s, for example, can be removed.
** '''name''': the name of the variable to clear.
* '''[role]''': tries to find a unit to assign a role to. This is useful if you want to choose a non-major character to say some things during the game. Once a role is assigned, you can use '''role=''' in a unit filter to identify the unit with that role (See [[FilterWML]]). However, there is no guarantee that roles will ever be assigned. You can use '''[have_unit]''' (see [if]) to see whether a role was assigned. This tag uses a [[StandardUnitFilter]] with the modification to order the search by type, mark only the first unit found with the role, and the role attribute is not used in the search. If for some reason you want to search for units that have or don't have existing roles, you can use one or more [not] filters. The will check recall lists in addition to units on the map. In normal use, you will probably want to include a ''side'' attribute to force the unit to be on a particular side.
** '''role''': the value to store as the unit's role. This role is not used in the [[StandardUnitFilter]] when doing the search for the unit to assign this role to.
** '''type''': a comma-separated list of possible types the unit can be. If any types are given, then units will be searched by type in the order listed. If no type is given, then no particular order with respect to type is guaranteed.
* {{DevFeature}} '''[store_map_dimensions]''': Stores the map dimensions in a variable.
** '''variable''': the name of the variable where the values will be saved into. If it is skipped, a variable 'map_size' is used, and its contents overridden, if they existed already. The result is a container variable, with members ''width'' and ''height''.

== See Also ==
* [[VariablesWML]]
* [[DirectActionsWML]]
* [[InterfaceActionsWML]]
* [[EventWML]]
* [[ReferenceWML]]

[[Category: WML Reference]]

InternalActionsWML

2008-03-16T00:11:47Z

Noyga:

{{WML Tags}}
== Internal actions ==

Internal actions are actions that WML uses internally that do not directly affect gameplay, for example storing a variable.

The internal actions '''[if]''', '''[while]''', and '''[event]''' describe when/whether sets of actions should be executed.

== [if] ==

Executes different sets of actions based on whether the conditions described in the condition tags are true or not.

Condition tags:
* '''[have_unit]''': a unit passing this filter with >0 HP exists
** [[StandardUnitFilter]] (almost... '''Note:''' does not check for matching units in the recall list)

* '''[have_location]''': a location passing this filter exists
** [[StandardLocationFilter]]

* '''[and]''': If an [and] is present, all must evaluate to true in order for the [if] to evaluate true. Useful as a bracket for complex conditions, but not strictly necessary.
** condition tags as in [if]: if these evaluate to true, [and] evaluates to true.

* '''[or]''': If an [or] is present, one must evaluate to true in order for the [if] to evaluate true. ([[AdvancedConditionalWML|Example]])
** condition tags as in [if]: if these evaluate to true, '''[or]''' evaluates to true.

* '''[not]''': If a [not] is present, none must evaluate to true in order for the [if] to evaluate true.
** condition tags as in [if]: if these evaluate to true, [not] evaluates to false.

* '''[and],[or],[not]''': all top-level filters will support in-order conditional handling of and, or, and not. One important thing to remember is, if you have multiple [or]s, you should not wrap your first conditional statement into an [or] block.

* '''[variable]''': tests something about the value of a WML variable (see [[VariablesWML]])
** '''name''': the name of the variable to test the value of Only one of the following keys should be used for comparing the value of the variable to another value:
** '''equals''': $name is equal (string wise) to this
** '''not_equals''': $name is not equal to this
** '''greater_than''': $name is numerically greater than this
** '''less_than''': $name is less than this
** '''greater_than_equal_to''': $name is not less than this
** '''less_than_equal_to''': $name is not greater than this
** '''numerical_not_equals''': $name is greater than or less than this
** '''numerical_equals''': $name is not greater than or less than this
** '''boolean_equals''': $name has the same boolean value (e.g. off, false, 0, no)
** '''contains''': $name contains this string
** {{DevFeature}} '''boolean_not_equals''': $name has not the same boolean value. Strictly a syntactic shortcut for the following syntax that served its absence in 1.4:
[not]
[variable]
name=...
boolean_equals=...
[/variable]
[/not]

After condition tags:
* '''[then]''': contains a set of action tags which should be executed if all conditions are true, or all conditions in any single [or] are true
* '''[else]''': contains a set of action tags which should be executed if any condition is false, and all [or] tags are false

== [switch] {{DevFeature}} ==

Executes different sets of action based ont the value of a variable.
[switch]
variable=foo
[case]
value="A"
... WML if A ...
[/case]
[case]
value="B"
... WML if B ...
[/case]
[else]
... WML if not A nor B ...
[/else]
[/switch]

* '''variable''': variable to check.
* '''[case]''': Case block. Contains:
** '''value''': the value to test the variable against.
** the action WML to execute if the variable matches the value (rest of the block).
* '''[else]''': Block of action WML to execute if no '''[case]''' block matches.

== [while] ==

Executes commands if all conditions are true.
Continues to execute them until a condition is not true.

Executes a maximum of 1024 iterations per invocation.
Condition tags are the same as for [if]

After condition tags:
* '''[do]''': contains actions that should be executed repeatedly until some condition is false.

The '''[while]''' tag is useful for iterating over an array.
An array is a list of values.
The ''number''th value in the array '''array''' is stored in the WML variable '''''array''[number]'''.
Note that if '''number''' is the value of the variable '''variable''',
the expression '''$''array''[$variable]''' will return the ''number''th value in ''array''.
The macros 'FOREACH' and 'NEXT' ([[UtilWML]]) can be used to iterate over an array;
i.e. run a set of actions once per element of the array.

=== {FOREACH} ===
If you wish to use a "for-each" iteration format (useful for example when you want to do an iteration for each row in a table) you can use the [http://www.wesnoth.org/misc/macro-reference.xhtml FOREACH] and [http://www.wesnoth.org/misc/macro-reference.xhtml NEXT] prededined macros.

=== {REPEAT} ===
You can use the REPEAT macro to perform a quick iteration for a number of times you specify.

== [event] ==

This adds a new event to the scenario.
The event is in the normal format for an '''[event]''' tag (See [[EventWML]]).
This is useful if you want an event that can only be triggered when a prior event is fulfilled

These tags describe actions that affect the values of WML variables
(see [[VariablesWML]] for information on WML variables,
and [[UtilWML]] for convenient macro shortcuts for some of these):
* '''[set_variable]''': manipulates a WML variable. {{Note:Predefined Macro|VARIABLE}}
** '''name''': the name of the variable to manipulate
** '''value''': set the variable to the given value (can be numeric or string). This only interprets dollars signs if it is the very first character, and then the entire value must be a simple variable name. (in 1.3.2, has the same effect as format. Use literal for no substitution)
** '''literal''': set the variable to the given value (can be numeric or string). This does not interpret any dollars signs.
** '''format''': set the variable to the given value. Interprets the dollar sign to a higher degree than most actions. (see [[VariablesWML]])
** '''to_variable''': Fully processes its value as in ''format'', and then gets the variable with that name.
** '''add''': add the given amount to the variable. To subtract, add a negative number.
** '''multiply''': multiply the variable by the given number. To divide, multiply by the inverse eg: 4/2 = 4 * 1/2 = 4 * 0.5. To negate, multiply by -1. The result is an integer.
** '''divide''': divide the variable by the given number. The result is an integer.
** '''modulo''': returns the remainder of an integer division. Both variables need to be an integer, the result is also an integer. eg 5 % 2 = 1.
** '''random''': the variable will be randomly set. You may provide a comma separated list of possibilities, e.g. 'random=Bob,Bill,Bella'. You may provide a range of numbers (integers), e.g. 'random=3..5'. You may combine these, e.g. 'random=100,1..9', in which case there would be 1/10th chance of getting 100, just like for each of 1 to 9. Dollars signs are only normally interpreted here, so it is harder to have a dynamically determined range. You would need to create the random-string with ''format''.
** '''rand''': does the same as random, but has better MP support. See [[BuildingMultiplayerExamples]] for more info on the MP case. '''It is highly recommended that you use this feature for randomization.'''
** '''time=stamp''': Retrieves a timestamp in milliseconds since wesnoth was started, can be used as timing aid. Don't try to use this as random value in MP since it will cause an OOS.
** {{DevFeature}} '''string_length''': Retrieves the length in characters of the string passed as this attribute's value; such string is parsed and variable substitution applied automatically (see [[VariablesWML]] for details).

* '''[store_unit]''': stores details about units into game variables. Common usage is to manipulate a unit by using [store_unit] to store it into a variable, followed by manipulation of the variable, and then [unstore_unit] to re-create the unit with the modified variables. Note: stored units also exist on the field, and modifying the stored variable will not automatically change the stats of the units. You need to use [unstore_unit]. See also [unstore_unit], [[DirectActionsWML]], and '''FOREACH''', [[UtilWML]]
** '''[filter]''': [[StandardUnitFilter]] all units matching this filter will be stored. If there are multiple units, they will be stored into an array of variables.
** '''variable''': the name of the variable into which to store the unit(s)
** '''mode''': defaults to ''always_clear'', which clears the variable, whether or not a match is found. If mode is set to ''replace'', the variable will only be cleared if a match is found. If mode is set to ''append'', the variable will not be cleared.
** '''kill''': if 'yes' the units that are stored will be removed from play. This is useful for instance to remove access to a player's recall list, with the intent to restore the recall list later.
:When a unit is stored, the following values may be manipulated with '''[set_variable]'''
:* description
:* experience
:* facing
:* gender
:* canrecruit
:* overlays
:* goto_x
:* goto_y
:* hitpoints
:* moves
:* resting
:* side
:* type
:* unrenamable
:* upkeep
:* user_description
:* x
:* y
:* [variables]
:* [status]
:* [modifications]
Variables, status, and modifications are children of the stored unit variable. Example:
[set_variable]
name=unit_store.status.poisoned
value=yes
[/set_variable]

:All keys and tags in the unit definition may be manipulated, including some others. Here is a sample list. If you have a doubt about what keys are valid or what the valid value range is for each key, code a [store_unit] event, save the game, and examine what keys are in the file.
:* advanceto
:* alignment
:* alpha
:* attacks_left
:* canrecruit
:* controller
:* cost
:* description
:* experience
:* facing
:* flying
:* fog
:* gender
:* get_hit_sound
:* gold
:* goto_x
:* goto_y
:* hitpoints
:* id
:* image
:* image_defensive
:* income
:* language_name (same as the name key in the unit config)
:* level
:* max_attacks
:* max_experience
:* max_hitpoints
:* max_moves
:* movement
:* movement_type
:* moves
:* race
:* resting
:* shroud
:* side
:* team_name
:* type
:* unit_description
:* unrenamable
:* usage
:* value
:* x
:* y
:* zoc
:* [advancement]
:* [/advancement]
:* [movement_costs]
:* [/movement_costs]
:* [defense]
:* [/defense]
:* [resistance]
:* [/resistance]
:* [variables]
:* [/variables]
:* [status]
:* [/status]
:* [attack]
:* [/attack]
:* [modifications_description]
:* [/modifications_description]
:* [modifications]
:* [/modifications]

* '''[store_starting_location]''': Stores the starting location of a side's leader in a variable. The variable is a composite type which will have members 'x', 'y', and 'terrain' (the terrain type for a starting location is always 'K' unless it has been changed)
** '''side''': the side whose starting location is to be stored
** '''variable''': (default='location'): the name of the variable to store the location in
* '''[store_locations]''': Stores a series of locations that pass certain criteria into an array. Each member of the array has members 'x' and 'y' (the position) and 'terrain' (the terrain type).
** [[StandardLocationFilter]]: a location or location range which specifies the locations to store. You must specify this or no locations will be stored.
** '''variable''': the name of the variable (array) into which to store the locations
** '''terrain''': a comma-sperated list of terrain codes. (See [[TerrainCodesWML]] for possible values.) If present, locations will only be chosen if the code for the terrain type of that location is listed.
** '''radius''': if present, any locations which are within '''radius''' hexes of the location filter will also be stored
** '''[filter]''': [[StandardUnitFilter]] only locations with units on them that match the filter will be stored. Use a blank filter to only store locations with units.
* '''[store_villages]''': Stores a series of locations of villages that pass certain criteria into an array. Each member of the array has members 'x' and 'y' (the position) and 'terrain' (the terrain type).
** '''owner_side''': a side number. If present, only villages owned by this side will be choosen. If owner_side=0, store the unowned villages.
** '''variable''': the name of the variable (array) into which to store the locations
** '''terrain''': a series of terrain characters. (See [[TerrainLettersWML]] for possible values.) If present, villages will only be chosen if the terrain code of the terrain type of that location is listed. You may give a comma separated list of terrains.
** '''side''': (default=1) the side for which the gold should be stored
** '''variable''': (default='gold') the name of the variable to store the gold in
* '''[store_side]''': stores information about a certain side in a variable. The variable will contain the member variables 'name', 'team_name', 'gold' and 'income', 'fog', 'shroud', 'user_team_name', 'colour', 'controller', 'village_gold' and 'recruit'.)
** '''side''': the side whose information should be stored
** '''variable''': the name of the variable to store the information in
* '''[clear_variable]''': This will delete the given variable or array. This is good to use to clean up the set of variables -- e.g. a well-behaved scenario will delete any variables that shouldn't be kept for the next scenario before the end of the scenario. Tags and variables of stored units can also be cleared, meaning that [trait]s and [object]s, for example, can be removed.
** '''name''': the name of the variable to clear.
* '''[role]''': tries to find a unit to assign a role to. This is useful if you want to choose a non-major character to say some things during the game. Once a role is assigned, you can use '''role=''' in a unit filter to identify the unit with that role (See [[FilterWML]]). However, there is no guarantee that roles will ever be assigned. You can use '''[have_unit]''' (see [if]) to see whether a role was assigned. This tag uses a [[StandardUnitFilter]] with the modification to order the search by type, mark only the first unit found with the role, and the role attribute is not used in the search. If for some reason you want to search for units that have or don't have existing roles, you can use one or more [not] filters. The will check recall lists in addition to units on the map. In normal use, you will probably want to include a ''side'' attribute to force the unit to be on a particular side.
** '''role''': the value to store as the unit's role. This role is not used in the [[StandardUnitFilter]] when doing the search for the unit to assign this role to.
** '''type''': a comma-separated list of possible types the unit can be. If any types are given, then units will be searched by type in the order listed. If no type is given, then no particular order with respect to type is guaranteed.
* {{DevFeature}} '''[store_map_dimensions]''': Stores the map dimensions in a variable.
** '''variable''': the name of the variable where the values will be saved into. If it is skipped, a variable 'map_size' is used, and its contents overridden, if they existed already. The result is a container variable, with members ''width'' and ''height''.

== See Also ==
* [[VariablesWML]]
* [[DirectActionsWML]]
* [[InterfaceActionsWML]]
* [[EventWML]]
* [[ReferenceWML]]

[[Category: WML Reference]]

FrenchTranslation

2008-03-10T20:05:08Z

Noyga: /* Aujourd'hui, qui fait quoi ? */

Battle for Wesnoth - Traduction française
== Le mot d'introduction ==

Cette page sert à mieux coordonner l'effort de tous et à donner les informations souvent demandées avant de se lancer dans la traduction française.

== Règles de traduction ==
=== Respect des termes de l'univers de Wesnoth ===
Pour améliorer la cohérence de l'ensemble des traductions, plusieurs Wikis servent de dictionnaires pour décrire l'univers de Wesnoth :
# noms communs : [[NomsCommuns]] ;
# noms propres : [[NomsPropres]].

=== Respect du contexte ===
Il est important de correctement traduire les différents textes. Il ne suffit pas de traduire mot à mot les différentes phrases, il faut aussi faire très attention au contexte.

=== Respect des règles de typographie ===

==== Titres ====
Les titres des campagnes, des scénarios et des chapitres doivent suivre les règles de la langue française. Ces règles se trouvent sur http://fr.wikipedia.org/wiki/Wikip%C3%A9dia:Conventions_typographiques.

==== Ponctuation ====
Les traductions doivent aussi suivre les règles de ponctuation de la langue française, essentielles à un bon affichage du texte ; par exemple, l'utilisation d'une espace fine avant le signe « : » évitera que ce signe ne se trouve en début de ligne d'un texte. Ces règles se trouvent sur http://www.reveenjoie-poesie.com/outils-linguistiques/Typographie_francaise.html.

Il est préférable de ne pas mettre de virgule ni avant le « et », ni avant le « ou » (contrairement à l'anglais).

Remarque : sous Windows, la combinaison Alt+(0160) permet d'écrire une espace fine (les parenthèses indiquent qu'il faut maintenir la touche Alt appuyée).
Voici d'autres raccourcis : http://www.crdp-montpellier.fr/cd48/tice/trucs/majuscules.htm#win

==== Majuscules ====
Les majuscules doivent être accentuées dans les textes traduits : À, Â, Æ, Ç, É, Ê, È, Î, Ô, Œ, Ù, Û...

Voici également quelques rappels sur des confusions fréquentes :
# pas de majuscules aux noms des races (« nains », « elfes », « orcs », etc.) ;
# majuscules aux noms de clans ou de factions (les humains de « l'Ordre de la Serre Pourpre ») ;
# majuscules aux points cardinaux quand on parle d'une partie d'un tout (« les forêts de l'Ouest » peuvent se trouver à l'est), et minuscule quand on parle de la direction (« aller vers le nord »).

=== Respect des règles de l'orthographe ===
Il est préférable de soigner son orthographe : le CNRS et l'ATILF fournissent un dictionnaire en ligne performant et complet : http://atilf.atilf.fr/

Les rectifications d'orthographes préconisées par l'Académie Française peuvent s'appliquer (http://www.academie-francaise.fr/langue/orthographe/regles.html).

== Principes de traduction pour Wesnoth ==
Le principe est de mettre à jour les fichiers .po, fichiers servant à gérer les traductions dans Wesnoth. Les échanges se font via la mailing list.

=== S'inscrire à la mailing list ===
La mailing list francophone de Wesnoth est l'outil privilégié pour
# d'abord avertir les traducteurs que vous allez commencer une traduction (et éviter de travailler sur le même fichier),
# envoyer ses traductions pour validation ou relecture,
# poser des questions.

Pour s'inscrire à la mailing list, envoyez un mail vide ayant comme sujet « subscribe » (il sera traité par un robot) ; ou cliquez directement ici mailto:wesnoth-request@ml.free.fr?subject=subscribe et envoyez...

Les responsables des différentes mailing list sont ici : [[WesnothTranslations]].

Les archives de la mailing list sont ici : http://news.gmane.org/gmane.games.wesnoth-fr ; vous pouvez vous abonner au serveur de news news.gmane.org (gmane.games.wesnoth-fr).

Il est également possible de discuter sur le canal IRC #wesnothfr (sur irc.freenode.net) ou sur le forum, mais l'équipe de traduction française ne s'y promène que rarement.

=== Récupérer les fichiers .po nécessaires ===
Les fichiers à traduire sont accessibles :
# soit par cette page : http://gettext.wesnoth.org/ (le plus simple),
# soit par le CVS : http://savannah.nongnu.org/cvs/?group=wesnoth (si on aime CVS).

=== Modifier les fichiers .po et vérifier le statut des lignes traduites ===
Plusieurs logiciels permettent de modifier ces fichiers :
# les éditeurs de texte
#* notepad++ (http://notepad-plus.sourceforge.net/fr/site.htm) ;
#* textpad (http://www.textpad.com/);
#* ou, pour Mac, Textwrangler (http://www.barebones.com/products/textwrangler/index.shtml) ;
#* et puis bien d'autres encore...
# ou des éditeurs spécifiques aux fichiers .po
#* poEdit, pour Mac et PC (http://www.poedit.net/) ;
#* KBabel (http://i18n.kde.org/tools/kbabel/) ;
#* gtranslator (http://gtranslator.sourceforge.net/).

Chaque champ de traduction possède un statut :
# si vous traduisez pour la première fois un champ, mettez-le en traduction approximative ("fuzzy" en anglais), et ce même si c'est une traduction très basique ; toute traduction doit être relue au moins une fois avant d'être approuvée ;
# si vous relisez un champ, libre à vous de décider de son statut après votre relecture ;
#* sortez-le de son état approximatif si vous le considérez incontestablement bien traduit ;
#* laissez-le à l'état approximatif et demandez une deuxième relecture si vous n'êtes pas sûr de la traduction.

=== Tester sa traduction ===
Si vous le désirez, vous pouvez immédiatement tester votre traduction :
# enlevez l'option fuzzy de la ligne (ou des lignes) que vous voulez vérifier ;
# générez un fichier compilé « .mo » à partir du fichier texte « .po » ;
#*En ligne de commande : la commande « msgfmt » peut être utilisée avec le nom du fichier « .po » (exemple : « msgfmt mon_fichier.po -o mon_fichier.mo » générera « mon_fichier.mo »).
#*Avec l'éditeur « poedit » : « Fichier -> Préférence », onglet « Editeur, cochez la case « Compiler automatiquement les fichiers .mo lors de la sauvegarde » ; sauvez le fichier.
# copiez votre fichier dans le répertoire contenant les traductions et renommez-le ;
#*Sous Windows, <Répertoire d'installation de Wesnoth>\fr\LC_MESSAGES\<Nom du fichier à tester> (Exemple : C:\Wesnoth\po\fr\LC_MESSAGES\wesnoth-utbs.mo) ;
#*Sous Linux, répertoire en fonction de la distribution (Exemple Mandriva : /usr/share/locale/fr/LC_MESSAGES).
# jouez.... jusqu'au moment où le texte traduit est censé apparaître ; il n'est pas nécessaire de tout reprendre depuis le début, une sauvegarde fonctionne. Un texte traduit sans erreur apparaît... traduit.

Remarque : pour accélérer les tests, vous pouvez utiliser le mode debug de Wesnoth :
#Pour passer en mode débug :
#*taper : (pour ouvrir le mode de commande), puis : debug<entrée>
#*ou taper "wesnoth.exe --debug",
#*ou taper "wesnoth.exe -d"
# pour utiliser le mode débug :
#*":debug" entre en mode debug
#*":n" termine le scénario immédiatement

=== Envoyer sa traduction ===
Une traduction terminée est compressée, puis envoyée à la ML.

Il est préférable, en cas de relecture, de signaler les modifications dans le corps du mail, par exemple en faisant comme ci-dessous :
#Exemple 1 (refonte d'une phrase) : N° ligne Anciene version => Nouvelle version.
#Exemple 2 (correction d'une faute, indiquée par des *) : N°Ligne Ancien*n*e version

Il est également possible de générer un fichier différentiel entre l'ancienne et la nouvelle version ; mais l'expérience semble montrer que cela est peu relu.
Cette techique est surtout à utiliser qu'en cas de modifications massives (cas où le suivi ligne à ligne serait complexe et lourd).

=== Attention ===
Il y a un bug récurent dans les fichiers po : lorsque la phrase traduite commence par "$", rien ne s'affiche

dans le jeu. Pour corriger le problème, il suffit de mettre un simple espace devant le signe (seulement quand la phrase commence par $)

== Aujourd'hui, qui fait quoi ? ==
Ce chapitre vous permet de savoir qui fait quoi...

Date de dernière mise à jour : 10/03/2008
* Traductions
** wesnoth-httt (Heir To The Throne / L'Héritier du trône) : La_vie_en_Wose
** wesnoth-thot (The Hammer of Thursagan) : Dylann/gotrek860
** wesnoth-nr (Northern Rebirth) : Damien
** wesnoth-l (Liberty) : Pierre
** wesnoth-did (Descent in the Darkness) : Jean-joseph
* Relectures / À relire

[[Category:Translations]]

SpellingMistakes

2008-03-02T21:50:38Z

Noyga: /* 1.4 Annuncement */

This page is meant to be a list for mistakes in campaigns and other texts in the en_US version of the game.

==An Orcish Incursion==

==Descent into Darkness==

==Eastern Invasion==

==Heir to the Throne==

==Northern Rebirth==

==Sceptre of Fire==

==Son of the Black Eye==

==The Hammer of Thursagan==

==The Rise of Wesnoth==

==The South Guard==

==Two Brothers==

==Under the Burning Suns==

==Editor==

==Tutorial==

==Manual==

==1.4 Annuncement==
#: ../template.html:111
"New maps and multiplayer campaigns: <cite> Auction-X, Dark Forecast Hamlets, "
"Mokena Prairie, The Manzivan Traps, Xanthe Chaos, </cite>. Revised maps: "
"<cite>Alirok Marsh</cite> (formerly <cite>Triple Blitz</cite>),<cite> "
"Amohsad Caldera, Blue Water Province, Castle Hopping Isle, Caves of the "
"Basilisk</cite> (formerly <cite>Blitz</cite>), <cite> Crossing, Crusaders "
"Fields, Cynsaun Battlefield, Den of Onis, Fallenstar Lake</cite> (formerly "
"<cite>Meteor Lake</cite>), <cite> Forest of Fear, Freelands</cite> (formerly "
"<cite>Charge</cite>),<cite> Hexcake, Hornshark Island, Island of the "
"Horatii, King of the Hill, Lagoon, Loris River, Merkwuerdigliebe, Morituri, "
"Paths of Daggers, Sablestone Delta, Siege Castles, Silverhead, Sulla's "
"Ruins, Waterloo Sunset, Wesbowl</cite>."
#Extra useless spaces in many places
#Missing comma before Hamlets
#Should be no comma and space after Xanthe Chaos
#Missing "Weldyn Channel" before </cite> (formerly <cite>Blitz</cite>)
#Missing "Siverhead" before Crossing

==Other (ingame help, ...)==

==Translation code bugs==

[[Category:Troubleshooting and Bugs]]

SpellingMistakes

2008-03-02T21:49:09Z

Noyga: /* 1.4 Annuncement */

This page is meant to be a list for mistakes in campaigns and other texts in the en_US version of the game.

==An Orcish Incursion==

==Descent into Darkness==

==Eastern Invasion==

==Heir to the Throne==

==Northern Rebirth==

==Sceptre of Fire==

==Son of the Black Eye==

==The Hammer of Thursagan==

==The Rise of Wesnoth==

==The South Guard==

==Two Brothers==

==Under the Burning Suns==

==Editor==

==Tutorial==

==Manual==

==1.4 Annuncement==
#: ../template.html:111
"New maps and multiplayer campaigns: <cite> Auction-X, Dark Forecast Hamlets, "
"Mokena Prairie, The Manzivan Traps, Xanthe Chaos, </cite>. Revised maps: "
"<cite>Alirok Marsh</cite> (formerly <cite>Triple Blitz</cite>),<cite> "
"Amohsad Caldera, Blue Water Province, Castle Hopping Isle, Caves of the "
"Basilisk</cite> (formerly <cite>Blitz</cite>), <cite> Crossing, Crusaders "
"Fields, Cynsaun Battlefield, Den of Onis, Fallenstar Lake</cite> (formerly "
"<cite>Meteor Lake</cite>), <cite> Forest of Fear, Freelands</cite> (formerly "
"<cite>Charge</cite>),<cite> Hexcake, Hornshark Island, Island of the "
"Horatii, King of the Hill, Lagoon, Loris River, Merkwuerdigliebe, Morituri, "
"Paths of Daggers, Sablestone Delta, Siege Castles, Silverhead, Sulla's "
"Ruins, Waterloo Sunset, Wesbowl</cite>."
#Extra useless spaces in many places
#Missing comma before Hamlets
#Should be no comma and space after Xanthe Chaos
#Missing "Weldyn Channel" before </cite> (formerly <cite>Blitz</cite>)

==Other (ingame help, ...)==

==Translation code bugs==

[[Category:Troubleshooting and Bugs]]

SpellingMistakes

2008-03-02T21:34:26Z

Noyga: /* 1.4 Annuncement */

This page is meant to be a list for mistakes in campaigns and other texts in the en_US version of the game.

==An Orcish Incursion==

==Descent into Darkness==

==Eastern Invasion==

==Heir to the Throne==

==Northern Rebirth==

==Sceptre of Fire==

==Son of the Black Eye==

==The Hammer of Thursagan==

==The Rise of Wesnoth==

==The South Guard==

==Two Brothers==

==Under the Burning Suns==

==Editor==

==Tutorial==

==Manual==

==1.4 Annuncement==
# type: Content of: <html><body><div><div><div><dl><dd>
#: ../template.html:111
"New maps and multiplayer campaigns: <cite> Auction-X, Dark Forecast Hamlets, "
"Mokena Prairie, The Manzivan Traps, Xanthe Chaos, </cite>. Revised maps: "
"<cite>Alirok Marsh</cite> (formerly <cite>Triple Blitz</cite>),<cite> "
"Amohsad Caldera, Blue Water Province, Castle Hopping Isle, Caves of the "
"Basilisk</cite> (formerly <cite>Blitz</cite>), <cite> Crossing, Crusaders "
"Fields, Cynsaun Battlefield, Den of Onis, Fallenstar Lake</cite> (formerly "
"<cite>Meteor Lake</cite>), <cite> Forest of Fear, Freelands</cite> (formerly "
"<cite>Charge</cite>),<cite> Hexcake, Hornshark Island, Island of the "
"Horatii, King of the Hill, Lagoon, Loris River, Merkwuerdigliebe, Morituri, "
"Paths of Daggers, Sablestone Delta, Siege Castles, Silverhead, Sulla's "
"Ruins, Waterloo Sunset, Wesbowl</cite>."
#Extra useless spaces in many places
#Missing comma before Hamlets
#Should be no comma and space after Xanthe Chaos

==Other (ingame help, ...)==

==Translation code bugs==

[[Category:Troubleshooting and Bugs]]

SpellingMistakes

2008-03-02T21:31:43Z

Noyga: /* 1.4 Annuncement */

This page is meant to be a list for mistakes in campaigns and other texts in the en_US version of the game.

==An Orcish Incursion==

==Descent into Darkness==

==Eastern Invasion==

==Heir to the Throne==

==Northern Rebirth==

==Sceptre of Fire==

==Son of the Black Eye==

==The Hammer of Thursagan==

==The Rise of Wesnoth==

==The South Guard==

==Two Brothers==

==Under the Burning Suns==

==Editor==

==Tutorial==

==Manual==

==1.4 Annuncement==
# type: Content of: <html><body><div><div><div><dl><dd>
#: ../template.html:111
"New maps and multiplayer campaigns: <cite> Auction-X, Dark Forecast Hamlets, "
"Mokena Prairie, The Manzivan Traps, Xanthe Chaos, </cite>. Revised maps: "
"<cite>Alirok Marsh</cite> (formerly <cite>Triple Blitz</cite>),<cite> "
"Amohsad Caldera, Blue Water Province, Castle Hopping Isle, Caves of the "
"Basilisk</cite> (formerly <cite>Blitz</cite>), <cite> Crossing, Crusaders "
"Fields, Cynsaun Battlefield, Den of Onis, Fallenstar Lake</cite> (formerly "
"<cite>Meteor Lake</cite>), <cite> Forest of Fear, Freelands</cite> (formerly "
"<cite>Charge</cite>),<cite> Hexcake, Hornshark Island, Island of the "
"Horatii, King of the Hill, Lagoon, Loris River, Merkwuerdigliebe, Morituri, "
"Paths of Daggers, Sablestone Delta, Siege Castles, Silverhead, Sulla's "
"Ruins, Waterloo Sunset, Wesbowl</cite>."
#Missing comma before Hamlets
#Should be no comma and space after Xanthe Chaos

==Other (ingame help, ...)==

==Translation code bugs==

[[Category:Troubleshooting and Bugs]]

SpellingMistakes

2008-03-02T21:29:46Z

Noyga: /* 1.4 Annoncement */

This page is meant to be a list for mistakes in campaigns and other texts in the en_US version of the game.

==An Orcish Incursion==

==Descent into Darkness==

==Eastern Invasion==

==Heir to the Throne==

==Northern Rebirth==

==Sceptre of Fire==

==Son of the Black Eye==

==The Hammer of Thursagan==

==The Rise of Wesnoth==

==The South Guard==

==Two Brothers==

==Under the Burning Suns==

==Editor==

==Tutorial==

==Manual==

==1.4 Annuncement==
# type: Content of: <html><body><div><div><div><dl><dd>
#: ../template.html:111
"New maps and multiplayer campaigns: <cite> Auction-X, Dark Forecast Hamlets, "
"Mokena Prairie, The Manzivan Traps, Xanthe Chaos, </cite>. Revised maps: "
"<cite>Alirok Marsh</cite> (formerly <cite>Triple Blitz</cite>),<cite> "
"Amohsad Caldera, Blue Water Province, Castle Hopping Isle, Caves of the "
"Basilisk</cite> (formerly <cite>Blitz</cite>), <cite> Crossing, Crusaders "
"Fields, Cynsaun Battlefield, Den of Onis, Fallenstar Lake</cite> (formerly "
"<cite>Meteor Lake</cite>), <cite> Forest of Fear, Freelands</cite> (formerly "
"<cite>Charge</cite>),<cite> Hexcake, Hornshark Island, Island of the "
"Horatii, King of the Hill, Lagoon, Loris River, Merkwuerdigliebe, Morituri, "
"Paths of Daggers, Sablestone Delta, Siege Castles, Silverhead, Sulla's "
"Ruins, Waterloo Sunset, Wesbowl</cite>."
Missing comma before Hamlets
Should be no comma and space after Xanthe Chaos

==Other (ingame help, ...)==

==Translation code bugs==

[[Category:Troubleshooting and Bugs]]

SpellingMistakes

2008-03-02T21:26:55Z

Noyga: /* Other (ingame help, ...) */

SummerOfCodeIdeas

2008-03-02T13:25:38Z

Noyga: /* Noyga */

== Ideas for Google Summer of Code projects ==

This is a compilation of ideas from ML. Needs to be refined (more detailed description, deliverables, workload estimation?):

== List of Ideas for the Project ==

=== Writing an AI based on the formula AI ===

Wesnoth has always had a simple C++ based AI. David (our lead developer) has been working on a simple language to write AI in Wesnoth ''link to formula AI page here''

The Wesnoth AI is used as an opponent in most campaigns, and as such is an important piece of code for the Wesnoth project. Unfortunately it is also one of the most neglected piece of code and a place where a lot of research and work could be done

==== General description ====

The aim of this project is to develop a new AI that would replace the original C++ AI. The main criterias we would want for this new AI are

* ''Plugability :'' It should be trivial for any content maker to change the behavior of the AI in specific case. The exact cases are still to be defined but should typically include
** hardwiring the first few turns of the AI
** changing the recruitment pattern
** completely controlling a given unit (scenario unit)
** taking control then giving back control of a given unit
* ''tunability :'' It should be easy for a scenario author to specify the general behaviour of the enemy on a given scenario (aggressiveness, intrepidity...)
* ''specific behaviours :'' there are some typical behaviours that are not smart to win the scenario but are needed, such as guarding a given unit, a given position, wandering aimlessly, attacking randomly, always fleeing. The AI should implement such behaviours, and allow easy addition of new behaviours

==== Required knowledge and talent ====

* ''A minimal knowledge of C++ is required, a good knowledge of C++ is desired :'' The formula AI framework is a work in progress and chances are high that some changes in the wesnoth code base will be needed. The wesnoth developer community is used to handle people that are familiar with coding but not C++, however the Formula AI framework uses advanced C++ features and a good knowledge of the language would avoid a major hurdle when plugging in new entries or functionalities for the AI
* ''Good social interaction with a large player community :'' A preliminary phase to coding any AI is to know the strategies and game pattern used by human players. This requires huge interaction with the player community. Our Gameplay Developers are open and can give some good starting points, but a big game experience and good interaction with the player community will greatly help in the study of the design

==== Milestones and deliverables ====

It is hard to give milestones at this point, but here are some ideas of what could be done

* ''AI design description, and basic function library :'' This first deliverable aims to conclude the '''study and analysis''' part of the project : becoming familiar with the formula language, study of multiplayer strategies and of the need of scenario writers with regard to AI. We would like to have a description of the code structure of the AI, some basis of the play strategies it would use and how external scenario writers could configure it for the particular behaviour they need
* ''Main AI delivery :'' This milestone's aim is to deliver a working AI implementing the strategies described in the first phase. It would not have to systematically beat the standard C++ AI at this point, but should be able to play the game correctly (recruit, early deployment on villages, grouping units to attack, holding its ground, protecting weak/important units). Moreover most plug-in entries should be available and a test-case for these entries should be provided.
* ''Fine tunning and behaviour library :'' The third phase would validate the actual strategy of the AI. The AI should consistently beat the default C++ AI, and do fairly well against an average human player. At that stage a library of scenario behaviours should also be delivered. The AI does not need to be as efficient with all scenario tweaking, but should act correctly with regard to the particular behaviour desired.

=== Extending the Multiplayer server ===

When the development team met at FOSDEM, we had our multiplayer community, though it is strong and healthy, had its growth restrained by the interface of the multiplayer lobby.

==== General Description ====
The general idea of this project would be
* To study the current lobby,
* To present some ideas of evolutions both in interface and functionalities of our multiplayer interface to allow it to scale to a much larger community
* To present some well constructed thought on our MP community and how that interface would develop it
* Of course to implement those changes :)

Some ideas that we had (but that are in no way mandatory)
* Having a simple way to register and authenticate nicknames, similar to what IRC offers. The point is not to have cryptographically safe logins, but to have something simple that gets the job done
* Having a simple room system? again inspired on IRC
* Having some way to find the type of games you are interested in.
** game type
** number of free slots/players
** any other criteria you might find interesting

Other ideas we are not convinced are good, but that are certainly worth studying (especially how the communities based around these concepts are different from ours)
* ranking players
* guilds
* official tournaments
* titles for players
* metaservers
* game matching when players are ranked (poker, bridge...)

The scalability of the project, both in term of number of players, and in term of the possibility for players and developers to extend the concept will be a valued criteria

Administration/moderation problems and techniques should also be studied

interaction with the Add-On server/forum might be an interesting field to expand to

==== Required knowledge and talent ====

* A fair amount of experience on C++ is required. Wesnoth uses some advanced C++ features and is heavily based on BOOST and STL. We can train you in some of the libraries used, but learning all of them would be a big hurdle
* Various experience with multiplayer games, in order to have a good idea of what multiplayer lobbies of other game look like, and (more importantly) a good idea of the social behaviours of multiple MP communities, how teams are formed in games and things like that

==== Milestones and deliverables ====

* A first milestone would be a presentation summarizing the different studies, and the proposed interface. preliminary informal stages would probably be desirable, to make sure the proposed idea is already a consensus within devs
** Study of other MP game-matching interfaces and functionalities
** Study of other MP communities
** Study of other MP moderation practices
** Study of the Wesnoth MP community, including needs, various opinons from different developers and players
* A second milestone would be the main code delivery. Code should be functional for it will be delivered in the next Wesnoth development release

=== Scenario/Campaign editor ===

Currently, in order to create campaign or multiplayer scenarios, it is necessary to manually edit WML files - XML-like configuration files. The goal of this project would be to create a graphical editor allowing the same.

==== General description ====

A scenario editor for Wesnoth supporting everything possible by Wesnoth's engine would be a huge project, so the scope of the actual project would of course be limited - what exactly should be implemented would be decided by initial discussion. Implementation details and choice of language/tools would also be up to the student to choose. The main ideas would be for the scenario editor to be:
* cross-platform (at least Linux, OSX, Windows)
* easy to use (someone who tries reasonably hard should be able to create a simple scenario/campaign with it, even if not knowing WML)
* powerful (there already is a map editor coming with Wesnoth - the scenario editor will provide more/different things)
* extensible (also after the SoC project, it should be easy to add additional features)

There exist at least two attempts at a scenario editor, an OSX-only one which shipped with early Wesnoth versions, and CampGen, an external tool written in WxPython. The student could look at them for ideas or even use one of them as base, but that should be discussed first. The below assumes a new application is developed from scratch (which likely will be much more motivating for the student than reviving an existing attempt). The actual things to be done would be:

* Decide on a cross-platform GUI which would be best suited (Qt4, Wx, GTK, Wesnoth's builtin GUI (in that case, could maybe integrate with the existing map editor, but would have serious other problems), or others...).
* Decide on a platform/language to use (C++, Python, or others...). Wesnoth is written in C++, so it's what most developers would prefer, but as long as it can be expected to work on Linux, OSX and Windows, this is completely open.
* GUI design. This is the main part of the project. The editor should make it easy to create scenarios, so the GUI must not be confusing/hard to use.
* Decide on base features. [[ReferenceWML]] lists everything currently supported by WML. Theoretically, the scenario editor could support everything, but for the timeframe of the SoC project, it will be necessary to decide on the most important features and implement those.
** WML-centric or not? Two opposite views for such an editor would be to either strictly follow WML, as extreme case have one dialog for each WML element. Or on the other hand make a scenario creation tool which completely hides WML and then simply can export to WML, translating features as necessary. The final design likely would be somewhere in between.
** Ability to read existing WML? The editor will export to WML, but need to decide if it also should be able to read it.
** Built-in map editor? Wesnoth comes with a map editor, but it can only be used to define the terrain. The scenario editor has to allow placing events and units and other things, so it will need a way to display maps as well. Would be worth investigating if the existing C++ map-drawing code of Wesnoth can be re-used.
** Ability to enter custom WML code? For advanced users this might be nice, if it can integrate well.
** Story screen editor for campaigns?
** How powerful should the events editor be? WML basically is a turing complete language, so must decide what should be supported and how to present to the user.
** Custom unit animations?
** Custom multi-hex terrains?
* Extensibility (leave the possibility to extend the application with plugins for some of the above things, either with a plugin architecture or by making the source code modular enough)
* WML-export. The second major part besides designing and implementing all the GUI will be exporting the result to WML, and depending on some design choices this could prove more or less hard to do.

==== Required knowledge and talent ====
* Knowledge of C++. Even in case the editor is not written in C++, it will be necessary to look at some parts of Wesnoth's source code (WML-parser, editor, ...) and understand them, possibly even integrate/re-use them.
* Ability/interest in GUI/application design. A not negligible part of the project likely will be spent designing various GUI dialogs.
* Prior use of level creation tools/modding tools. Knowing existing tools for other games will help a lot in the design phase, as many good ideas can be seen there. Not required though.
* Having played Wesnoth and knowing what scenarios look like would help. Someone who never played Wesnoth before would risk losing a lot of precious time playing the game instead of working :) But it's not required of course.
* Knowledge of WML. A candidate who already knows Wesnoth's WML could save the initial time studying it. (On the other hand, not knowing WML might mean less technical bias and might lead to an application which is easer to use for non-technical users.)
* Ability to interact with developers/users. Presenting GUI mockups and test versions and incorporating early user feedback likely will improve the end result a lot. The Wesnoth community is big enough that there should be quite some willing testers.

==== Milestones and deliverables ====
The initial design will decide on many later things, and likely a lot of talking to developers and users will be necessary. But some general milestones I'd expect:
* Create a base test application in the chosen language/platform. This will not do much yet, maybe load some WML and display it as text. Try to package it for Linux, OSX and Windows (there will be help from the Wesnoth community, so no need to have access to all of them), and see if it can be expected to work. If a standard GUI like C++/Qt4 is used, this will be rather trivial. Something like Python/Wx or C#/.NET might take more time.
* Add ability to edit some very simple, maybe only textual properties of a scenario, and export to WML. It should already have base features like Save/Load/Undo, copy/paste, multiple documents, and so on. Depending on the chosen GUI this may be easy or already require some work.
* Finish design. Should list the intended features and demonstrate how the GUI will work.
* Start implementation, a natural milestone would be to make it possible to create and export a very simple, but playable scenario.
* Add more of the features (which ones and in which order depends on the design above, a detailed roadmap will be part of it).

=== Addon server ===
Wesnoth has an addon server which offers users to upload user
made content (UMC). This allows all other users of Wesnoth
to easily download and install this content. The server was
originally written for user made campaigns but contains a lot
more types of addons nowadays. Both the server side and the
client side need to be improved.

==== General description ====
Both the server and client side of the addon server haven't
been improved over the years and can use quite some improvements.
The client side GUI needs quite some improvements. For the
server side it's wanted to allow better integration with
various tools, which improve the quality of the addons.

===== Server side =====
The server code either needs to be updated or rewritten, the
student is free to make this decision him or herself. The
student is free to choose the language for the server.

* The server only needs to run on Linux systems, crossplatform would be nice but isn't required.
* At the moment there's a rudimentary integration with our translation project Wescamp. This needs to be improved. Upon uploading the new content needs to be send to Wescamp (via a svn commit). And the translations need to be fetched on a regular basis.
* We have various tools to check the WML code and also upgrade it to newer version. The addon server needs to be able to run those tools on the content.

===== Client side =====
The client side needs improvements, there are two main clients
the ingame version and a standalone version in Python.

* Upgrade the GUI, Mordante is working on a new GUI library which is intended to make it possible to make the wanted changes.
* Make it easier to see what kind of addon it is, at the moment a lot of new users download something and have no clue what kind of addon it is.
* Make it easier to see whether a newer version of the addon is on the server and update the addon.
* Make it easy to select which translations you want to download and also look for newer versions of the translations.

==== Required knowledge and talent ====
* Knowledge of C++, the game is written in C++ and modifications need to be made there.
* Knowlegde of Python, various tools have been written in Python which need to be intergrated with the new server.

==== Milestones and deliverables ====
* The first step is to determine what exactly needs to be done and determine in which language the server will be rewritten. This includes, but isn't limited to:
** Determine the exact feature set.
** Protocol changes needed.
** Methods to integrate with both the WML tools and Wescamp with the new server.
** Determine the GUI for the client side.
* This needs to be presented and discussed with the mentor(s).
* The next thing in to implement the feature set. The code needs to be fully functional and committed in trunk.

=== Map editor ===

=== Make your own ideas ===
If you have your own idea the best thing is to join
IRC wesnoth-dev at irc.freenode.net and discuss the
idea with the developers there. If the developers
think your idea is interesting and like the feature
you can start to turn it into a full proposal. Once
done discuss it again on IRC so the developers can
accept your idea.

=== Other ideas to be fleshed out ===
* A MapGenerator rewrite - better scalable for outdoor maps, plus the possibility to define areas (similar to the caverns in the ave generator) etc.

== Other info to provide for GSoC ==
==== Describe your organization. ====

==== Why is your organization applying to participate in GSoC 2008? What do you hope to gain by participating?====

Most of our developers have particular areas of interest in which they work. Though they are efficient in their areas, there are other, presently uncovered, areas of the code with a need for improvements but a high barrier to entry.

If a student were dedicated to any of these uncovered areas, we believe that person could be brought up to speed relatively quickly and function as a peer of the existing developers.

By bringing new people in and allowing them to be actively responsible for an area of code, we hope to kickstart some areas of the project that have lagged behind

==== Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.====
This is the first time the Wesnoth project has applied to Google SoC

==== If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?====

This is the first time the Wesnoth project has applied to Google SoC

==== Who will your organization administrator be? Please include Google Account information.====
Nils Kneuper aka Ivanovic

crazy.ivanovic |ATTT| googlemail.com

==== What license(s) does your project use?====
Our project is entirely GPL.

All code is GPL.

All art is GPL, 99% was made for the project, everything was taken from content that was checked to be GPL.

==== What is the URL for your ideas page?====
Our main summer of code page is located at http://www.wesnoth.org/wiki/SummerOfCodeIdeas

This page contains various coding ideas and the thought the development team has already given them.

It also contains a list of the developers that are the most active on IRC and their domains of interest.

==== What is the main development mailing list or forum for your organization?====
Most development work takes place on "wesnoth-dev |ATTT| gna.org". Beside this some work happens at http://www.wesnoth.org/forum/.

in particular, all art developement takes place on the forum.

==== What is the main IRC channel for your organization?====

All our IRC channels are on the ''freenode'' network

* ''#wesnoth-dev'' is the main development channel, where most discussion takes place
* ''#wesnoth'' is a generic channel for the community
* ''#wesnoth-mp'' is a separate channel for multiplayer games and balancing

==== Does your organization have an application template you would like to see students use? If so, please provide it now.====
We plan mainly to meet potential students through our IRC channel, but the following questions are wesnoth-specific and are worth pondering for any student, even if we don't need a formal answer

* What type of gamer are you? What type of games? What type of opponent? Are you more interested in story or gameplay?
* Are you good at interacting with other players? Our developer community is friendly, but the player community can be a bit rough.
* Do you give constructive advices? Do you receive advice well? Are you good at sorting useful criticism from useless ones?
* Have you played Wesnoth? How long? Single player or multiplayer? We do not plan to favor Wesnoth players as such, but some projects require a good feeling of the game which is hard to get without having played intensively.
* What nickname do you plan to use on IRC and the forum?

''''to be completed''''

==== Who will be your backup organization administrator? Please include Google Account information.====

==== Who will your mentors be? Please include Google Account information.====

David White (davewx7@gmail.com)

Jeremy Rosen alias Boucman (boucman2|ATTT|gmail.com)

Mark de Wever aka Mordante (gmail.com account mordante.wesnoth)

==== What criteria did you use to select these individuals as mentors? Please be as specific as possible.====

Dave is the project leader and one of the most knowledgeable in C++. He has also written the Formula AI code which we plan to develop via the SoC

He is well known in our community for formulating simple but effective explanations for complicated topics, and has good design intuition.

The growth of Wesnoth demonstrates his capacity to get other developers to work together and keep them involved in a thriving community.

==== What is your plan for dealing with disappearing students?====

==== What is your plan for dealing with disappearing mentors?====

==== What steps will you take to encourage students to interact with your project's community before, during and after the program?====

Wesnoth has a particularly healthy community, both for developers and for players.

Our general policy regarding new coders has always been "two patch... you're in" In other word, anybody that is able to get two non-trivial patches applied is offered commit right.

We have a developer responsible for applying patches and guiding new developers into our community. This is a well known and effective process we plan to apply to students, directing them to our [[EasyCoding]] pages (these project are usually a couple of hours long and has been chosen to provide easy access to code)

Usually, patches go back and forth a couple of time, to make sure that all secondary things are in place (indenting, coding style, modified makefiles etc.) The idea is that coder education should take place before the coder gets commit rights, but that getting new coder in is one of the most important things to maintain our project alive.

If the student is a little proactive and ready to join IRC, all the developers are usually very welcoming, and good at directing newcomers to quickly give useful results.

We also plan to give a special forum title to any students. This will allow all forum members to tell them appart from normal users and give them read/write access to the developper only forums.

This will also allow usto quickly spot any problem they might have interacting with the player community. We have a very mature developper community, but our player community is made of all sort of people of all age and education, and it can be rough at time.

==== What will you do to ensure that your accepted students stick with the project after GSoC concludes?====

Since our community has a history of having developpers easily and quickly join, we expect the student to be full-fledge developpers quite faset (probably a little after the end of the bonding period).

Thus there will be no "end of GSoC" transition. At the end of the Summer of code we expect the student to be responsible for the part he developped, and to continue taking care of it, like other developpers are responsible for their part.

''''TO BE COMPLETED''''

=== People to bug on IRC, possible mentors ===
Everybody feel free to edit/correct his entry!

==== Dave alias Sirp ====

Sirp started Wesnoth and is our lead developper. He is currently our C++ expert and is also the one that is working on the new Formula AI. Any questions regarding the formula AI should be directed to him.

==== Mordante ====
Many of the possible projects involve the code for which he is an area expert. Also, many of the possible projects currently listed on the ideas page require GUI parts to work. Given that Mordante wants to tackle a rewrite of large parts of this, he will be our expert there as well as already being our area expert for the terrain engine.

==== Elias Pscherning (elias) ====
He wrote the original version of campgen and as such will know a lot about what is needed to to make such an editor work correctly. The work on a scenario editor might be based upon campgen and as such his knowledge will be really helpful.

==== Karol Nowak (grzywacz) ====
Last year he participated at GSoC as a student, so he will understand the situation of GSoC students. Beside this he is our top expert on embedded devices, and is actively working on the gp2x support.

==== boucman ====
As our "patch monkey" he accustomed to critiquing patches of every kind. Beside this, he knows many areas of the game due to working on applying patches. He is particularly used to answering question from new coders, and doesn't mind explaining trivial stuff.

He was the one who started the "two patches, you're in" policy and the ReferenceWML part of the project

==== Soliton ====
He knows our MP server setup best. Beside this he has already done a lot of work on the MP server himself. So he probably has most knowledge about it and, being one of our MP-developers, might provide important help from the perspective of the MP player community and what is needed there.

==== zookeeper or Mythological or Rhuvaen ====
As our leading WML expert it would be good to have him in the list when it comes to WML specific problems. That is for work on the scenario editor he probably knows best what should be implemented in it and what is a usable way for things.

==== YogiHH or Piotr Cychowski (cycholka) ====
Since they are the two developers who know most about building under Windows, they will probably be really helpful. Either if the student comes from the Windows side, or to help test resulting work to make sure that it does work on Windows and, for the case that it does not, to show them where problems are.

==== Eric S. Raymond (ESR) ====
ESR is our project toolsmith; he has written several tools that semi-automate various aspects of WML maintenance. While most of our developers/designers concentrate on either the C++ core or WML but not both, he has a balanced understanding of both levels and may be helpful in helping students develop a grasp of the overall architecture. Finally, he did the last overhaul of the Wesnoth UI and understands UI design principles; he is well-equipped to guide students working in that area.

==== Noyga ====
Another versatile developer, on the C++ side he doesn't concentrate on a particular area, did some tweaks to improve translations in some languages (like enabling the female forms for names in various place) but know quite well the C++ side of units, abilities and WML. On the WML side he's an expert.

SummerOfCodeIdeas

2008-03-02T13:23:05Z

Noyga: /* People to bug on IRC, possible mentors */

== Ideas for Google Summer of Code projects ==

This is a compilation of ideas from ML. Needs to be refined (more detailed description, deliverables, workload estimation?):

== List of Ideas for the Project ==

=== Writing an AI based on the formula AI ===

Wesnoth has always had a simple C++ based AI. David (our lead developer) has been working on a simple language to write AI in Wesnoth ''link to formula AI page here''

The Wesnoth AI is used as an opponent in most campaigns, and as such is an important piece of code for the Wesnoth project. Unfortunately it is also one of the most neglected piece of code and a place where a lot of research and work could be done

==== General description ====

The aim of this project is to develop a new AI that would replace the original C++ AI. The main criterias we would want for this new AI are

* ''Plugability :'' It should be trivial for any content maker to change the behavior of the AI in specific case. The exact cases are still to be defined but should typically include
** hardwiring the first few turns of the AI
** changing the recruitment pattern
** completely controlling a given unit (scenario unit)
** taking control then giving back control of a given unit
* ''tunability :'' It should be easy for a scenario author to specify the general behaviour of the enemy on a given scenario (aggressiveness, intrepidity...)
* ''specific behaviours :'' there are some typical behaviours that are not smart to win the scenario but are needed, such as guarding a given unit, a given position, wandering aimlessly, attacking randomly, always fleeing. The AI should implement such behaviours, and allow easy addition of new behaviours

==== Required knowledge and talent ====

* ''A minimal knowledge of C++ is required, a good knowledge of C++ is desired :'' The formula AI framework is a work in progress and chances are high that some changes in the wesnoth code base will be needed. The wesnoth developer community is used to handle people that are familiar with coding but not C++, however the Formula AI framework uses advanced C++ features and a good knowledge of the language would avoid a major hurdle when plugging in new entries or functionalities for the AI
* ''Good social interaction with a large player community :'' A preliminary phase to coding any AI is to know the strategies and game pattern used by human players. This requires huge interaction with the player community. Our Gameplay Developers are open and can give some good starting points, but a big game experience and good interaction with the player community will greatly help in the study of the design

==== Milestones and deliverables ====

It is hard to give milestones at this point, but here are some ideas of what could be done

* ''AI design description, and basic function library :'' This first deliverable aims to conclude the '''study and analysis''' part of the project : becoming familiar with the formula language, study of multiplayer strategies and of the need of scenario writers with regard to AI. We would like to have a description of the code structure of the AI, some basis of the play strategies it would use and how external scenario writers could configure it for the particular behaviour they need
* ''Main AI delivery :'' This milestone's aim is to deliver a working AI implementing the strategies described in the first phase. It would not have to systematically beat the standard C++ AI at this point, but should be able to play the game correctly (recruit, early deployment on villages, grouping units to attack, holding its ground, protecting weak/important units). Moreover most plug-in entries should be available and a test-case for these entries should be provided.
* ''Fine tunning and behaviour library :'' The third phase would validate the actual strategy of the AI. The AI should consistently beat the default C++ AI, and do fairly well against an average human player. At that stage a library of scenario behaviours should also be delivered. The AI does not need to be as efficient with all scenario tweaking, but should act correctly with regard to the particular behaviour desired.

=== Extending the Multiplayer server ===

When the development team met at FOSDEM, we had our multiplayer community, though it is strong and healthy, had its growth restrained by the interface of the multiplayer lobby.

==== General Description ====
The general idea of this project would be
* To study the current lobby,
* To present some ideas of evolutions both in interface and functionalities of our multiplayer interface to allow it to scale to a much larger community
* To present some well constructed thought on our MP community and how that interface would develop it
* Of course to implement those changes :)

Some ideas that we had (but that are in no way mandatory)
* Having a simple way to register and authenticate nicknames, similar to what IRC offers. The point is not to have cryptographically safe logins, but to have something simple that gets the job done
* Having a simple room system? again inspired on IRC
* Having some way to find the type of games you are interested in.
** game type
** number of free slots/players
** any other criteria you might find interesting

Other ideas we are not convinced are good, but that are certainly worth studying (especially how the communities based around these concepts are different from ours)
* ranking players
* guilds
* official tournaments
* titles for players
* metaservers
* game matching when players are ranked (poker, bridge...)

The scalability of the project, both in term of number of players, and in term of the possibility for players and developers to extend the concept will be a valued criteria

Administration/moderation problems and techniques should also be studied

interaction with the Add-On server/forum might be an interesting field to expand to

==== Required knowledge and talent ====

* A fair amount of experience on C++ is required. Wesnoth uses some advanced C++ features and is heavily based on BOOST and STL. We can train you in some of the libraries used, but learning all of them would be a big hurdle
* Various experience with multiplayer games, in order to have a good idea of what multiplayer lobbies of other game look like, and (more importantly) a good idea of the social behaviours of multiple MP communities, how teams are formed in games and things like that

==== Milestones and deliverables ====

* A first milestone would be a presentation summarizing the different studies, and the proposed interface. preliminary informal stages would probably be desirable, to make sure the proposed idea is already a consensus within devs
** Study of other MP game-matching interfaces and functionalities
** Study of other MP communities
** Study of other MP moderation practices
** Study of the Wesnoth MP community, including needs, various opinons from different developers and players
* A second milestone would be the main code delivery. Code should be functional for it will be delivered in the next Wesnoth development release

=== Scenario/Campaign editor ===

Currently, in order to create campaign or multiplayer scenarios, it is necessary to manually edit WML files - XML-like configuration files. The goal of this project would be to create a graphical editor allowing the same.

==== General description ====

A scenario editor for Wesnoth supporting everything possible by Wesnoth's engine would be a huge project, so the scope of the actual project would of course be limited - what exactly should be implemented would be decided by initial discussion. Implementation details and choice of language/tools would also be up to the student to choose. The main ideas would be for the scenario editor to be:
* cross-platform (at least Linux, OSX, Windows)
* easy to use (someone who tries reasonably hard should be able to create a simple scenario/campaign with it, even if not knowing WML)
* powerful (there already is a map editor coming with Wesnoth - the scenario editor will provide more/different things)
* extensible (also after the SoC project, it should be easy to add additional features)

There exist at least two attempts at a scenario editor, an OSX-only one which shipped with early Wesnoth versions, and CampGen, an external tool written in WxPython. The student could look at them for ideas or even use one of them as base, but that should be discussed first. The below assumes a new application is developed from scratch (which likely will be much more motivating for the student than reviving an existing attempt). The actual things to be done would be:

* Decide on a cross-platform GUI which would be best suited (Qt4, Wx, GTK, Wesnoth's builtin GUI (in that case, could maybe integrate with the existing map editor, but would have serious other problems), or others...).
* Decide on a platform/language to use (C++, Python, or others...). Wesnoth is written in C++, so it's what most developers would prefer, but as long as it can be expected to work on Linux, OSX and Windows, this is completely open.
* GUI design. This is the main part of the project. The editor should make it easy to create scenarios, so the GUI must not be confusing/hard to use.
* Decide on base features. [[ReferenceWML]] lists everything currently supported by WML. Theoretically, the scenario editor could support everything, but for the timeframe of the SoC project, it will be necessary to decide on the most important features and implement those.
** WML-centric or not? Two opposite views for such an editor would be to either strictly follow WML, as extreme case have one dialog for each WML element. Or on the other hand make a scenario creation tool which completely hides WML and then simply can export to WML, translating features as necessary. The final design likely would be somewhere in between.
** Ability to read existing WML? The editor will export to WML, but need to decide if it also should be able to read it.
** Built-in map editor? Wesnoth comes with a map editor, but it can only be used to define the terrain. The scenario editor has to allow placing events and units and other things, so it will need a way to display maps as well. Would be worth investigating if the existing C++ map-drawing code of Wesnoth can be re-used.
** Ability to enter custom WML code? For advanced users this might be nice, if it can integrate well.
** Story screen editor for campaigns?
** How powerful should the events editor be? WML basically is a turing complete language, so must decide what should be supported and how to present to the user.
** Custom unit animations?
** Custom multi-hex terrains?
* Extensibility (leave the possibility to extend the application with plugins for some of the above things, either with a plugin architecture or by making the source code modular enough)
* WML-export. The second major part besides designing and implementing all the GUI will be exporting the result to WML, and depending on some design choices this could prove more or less hard to do.

==== Required knowledge and talent ====
* Knowledge of C++. Even in case the editor is not written in C++, it will be necessary to look at some parts of Wesnoth's source code (WML-parser, editor, ...) and understand them, possibly even integrate/re-use them.
* Ability/interest in GUI/application design. A not negligible part of the project likely will be spent designing various GUI dialogs.
* Prior use of level creation tools/modding tools. Knowing existing tools for other games will help a lot in the design phase, as many good ideas can be seen there. Not required though.
* Having played Wesnoth and knowing what scenarios look like would help. Someone who never played Wesnoth before would risk losing a lot of precious time playing the game instead of working :) But it's not required of course.
* Knowledge of WML. A candidate who already knows Wesnoth's WML could save the initial time studying it. (On the other hand, not knowing WML might mean less technical bias and might lead to an application which is easer to use for non-technical users.)
* Ability to interact with developers/users. Presenting GUI mockups and test versions and incorporating early user feedback likely will improve the end result a lot. The Wesnoth community is big enough that there should be quite some willing testers.

==== Milestones and deliverables ====
The initial design will decide on many later things, and likely a lot of talking to developers and users will be necessary. But some general milestones I'd expect:
* Create a base test application in the chosen language/platform. This will not do much yet, maybe load some WML and display it as text. Try to package it for Linux, OSX and Windows (there will be help from the Wesnoth community, so no need to have access to all of them), and see if it can be expected to work. If a standard GUI like C++/Qt4 is used, this will be rather trivial. Something like Python/Wx or C#/.NET might take more time.
* Add ability to edit some very simple, maybe only textual properties of a scenario, and export to WML. It should already have base features like Save/Load/Undo, copy/paste, multiple documents, and so on. Depending on the chosen GUI this may be easy or already require some work.
* Finish design. Should list the intended features and demonstrate how the GUI will work.
* Start implementation, a natural milestone would be to make it possible to create and export a very simple, but playable scenario.
* Add more of the features (which ones and in which order depends on the design above, a detailed roadmap will be part of it).

=== Addon server ===
Wesnoth has an addon server which offers users to upload user
made content (UMC). This allows all other users of Wesnoth
to easily download and install this content. The server was
originally written for user made campaigns but contains a lot
more types of addons nowadays. Both the server side and the
client side need to be improved.

==== General description ====
Both the server and client side of the addon server haven't
been improved over the years and can use quite some improvements.
The client side GUI needs quite some improvements. For the
server side it's wanted to allow better integration with
various tools, which improve the quality of the addons.

===== Server side =====
The server code either needs to be updated or rewritten, the
student is free to make this decision him or herself. The
student is free to choose the language for the server.

* The server only needs to run on Linux systems, crossplatform would be nice but isn't required.
* At the moment there's a rudimentary integration with our translation project Wescamp. This needs to be improved. Upon uploading the new content needs to be send to Wescamp (via a svn commit). And the translations need to be fetched on a regular basis.
* We have various tools to check the WML code and also upgrade it to newer version. The addon server needs to be able to run those tools on the content.

===== Client side =====
The client side needs improvements, there are two main clients
the ingame version and a standalone version in Python.

* Upgrade the GUI, Mordante is working on a new GUI library which is intended to make it possible to make the wanted changes.
* Make it easier to see what kind of addon it is, at the moment a lot of new users download something and have no clue what kind of addon it is.
* Make it easier to see whether a newer version of the addon is on the server and update the addon.
* Make it easy to select which translations you want to download and also look for newer versions of the translations.

==== Required knowledge and talent ====
* Knowledge of C++, the game is written in C++ and modifications need to be made there.
* Knowlegde of Python, various tools have been written in Python which need to be intergrated with the new server.

==== Milestones and deliverables ====
* The first step is to determine what exactly needs to be done and determine in which language the server will be rewritten. This includes, but isn't limited to:
** Determine the exact feature set.
** Protocol changes needed.
** Methods to integrate with both the WML tools and Wescamp with the new server.
** Determine the GUI for the client side.
* This needs to be presented and discussed with the mentor(s).
* The next thing in to implement the feature set. The code needs to be fully functional and committed in trunk.

=== Map editor ===

=== Make your own ideas ===
If you have your own idea the best thing is to join
IRC wesnoth-dev at irc.freenode.net and discuss the
idea with the developers there. If the developers
think your idea is interesting and like the feature
you can start to turn it into a full proposal. Once
done discuss it again on IRC so the developers can
accept your idea.

=== Other ideas to be fleshed out ===
* A MapGenerator rewrite - better scalable for outdoor maps, plus the possibility to define areas (similar to the caverns in the ave generator) etc.

== Other info to provide for GSoC ==
==== Describe your organization. ====

==== Why is your organization applying to participate in GSoC 2008? What do you hope to gain by participating?====

Most of our developers have particular areas of interest in which they work. Though they are efficient in their areas, there are other, presently uncovered, areas of the code with a need for improvements but a high barrier to entry.

If a student were dedicated to any of these uncovered areas, we believe that person could be brought up to speed relatively quickly and function as a peer of the existing developers.

By bringing new people in and allowing them to be actively responsible for an area of code, we hope to kickstart some areas of the project that have lagged behind

==== Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.====
This is the first time the Wesnoth project has applied to Google SoC

==== If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?====

This is the first time the Wesnoth project has applied to Google SoC

==== Who will your organization administrator be? Please include Google Account information.====
Nils Kneuper aka Ivanovic

crazy.ivanovic |ATTT| googlemail.com

==== What license(s) does your project use?====
Our project is entirely GPL.

All code is GPL.

All art is GPL, 99% was made for the project, everything was taken from content that was checked to be GPL.

==== What is the URL for your ideas page?====
Our main summer of code page is located at http://www.wesnoth.org/wiki/SummerOfCodeIdeas

This page contains various coding ideas and the thought the development team has already given them.

It also contains a list of the developers that are the most active on IRC and their domains of interest.

==== What is the main development mailing list or forum for your organization?====
Most development work takes place on "wesnoth-dev |ATTT| gna.org". Beside this some work happens at http://www.wesnoth.org/forum/.

in particular, all art developement takes place on the forum.

==== What is the main IRC channel for your organization?====

All our IRC channels are on the ''freenode'' network

* ''#wesnoth-dev'' is the main development channel, where most discussion takes place
* ''#wesnoth'' is a generic channel for the community
* ''#wesnoth-mp'' is a separate channel for multiplayer games and balancing

==== Does your organization have an application template you would like to see students use? If so, please provide it now.====
We plan mainly to meet potential students through our IRC channel, but the following questions are wesnoth-specific and are worth pondering for any student, even if we don't need a formal answer

* What type of gamer are you? What type of games? What type of opponent? Are you more interested in story or gameplay?
* Are you good at interacting with other players? Our developer community is friendly, but the player community can be a bit rough.
* Do you give constructive advices? Do you receive advice well? Are you good at sorting useful criticism from useless ones?
* Have you played Wesnoth? How long? Single player or multiplayer? We do not plan to favor Wesnoth players as such, but some projects require a good feeling of the game which is hard to get without having played intensively.
* What nickname do you plan to use on IRC and the forum?

''''to be completed''''

==== Who will be your backup organization administrator? Please include Google Account information.====

==== Who will your mentors be? Please include Google Account information.====

David White (davewx7@gmail.com)

Jeremy Rosen alias Boucman (boucman2|ATTT|gmail.com)

Mark de Wever aka Mordante (gmail.com account mordante.wesnoth)

==== What criteria did you use to select these individuals as mentors? Please be as specific as possible.====

Dave is the project leader and one of the most knowledgeable in C++. He has also written the Formula AI code which we plan to develop via the SoC

He is well known in our community for formulating simple but effective explanations for complicated topics, and has good design intuition.

The growth of Wesnoth demonstrates his capacity to get other developers to work together and keep them involved in a thriving community.

==== What is your plan for dealing with disappearing students?====

==== What is your plan for dealing with disappearing mentors?====

==== What steps will you take to encourage students to interact with your project's community before, during and after the program?====

Wesnoth has a particularly healthy community, both for developers and for players.

Our general policy regarding new coders has always been "two patch... you're in" In other word, anybody that is able to get two non-trivial patches applied is offered commit right.

We have a developer responsible for applying patches and guiding new developers into our community. This is a well known and effective process we plan to apply to students, directing them to our [[EasyCoding]] pages (these project are usually a couple of hours long and has been chosen to provide easy access to code)

Usually, patches go back and forth a couple of time, to make sure that all secondary things are in place (indenting, coding style, modified makefiles etc.) The idea is that coder education should take place before the coder gets commit rights, but that getting new coder in is one of the most important things to maintain our project alive.

If the student is a little proactive and ready to join IRC, all the developers are usually very welcoming, and good at directing newcomers to quickly give useful results.

We also plan to give a special forum title to any students. This will allow all forum members to tell them appart from normal users and give them read/write access to the developper only forums.

This will also allow usto quickly spot any problem they might have interacting with the player community. We have a very mature developper community, but our player community is made of all sort of people of all age and education, and it can be rough at time.

==== What will you do to ensure that your accepted students stick with the project after GSoC concludes?====

Since our community has a history of having developpers easily and quickly join, we expect the student to be full-fledge developpers quite faset (probably a little after the end of the bonding period).

Thus there will be no "end of GSoC" transition. At the end of the Summer of code we expect the student to be responsible for the part he developped, and to continue taking care of it, like other developpers are responsible for their part.

''''TO BE COMPLETED''''

=== People to bug on IRC, possible mentors ===
Everybody feel free to edit/correct his entry!

==== Dave alias Sirp ====

Sirp started Wesnoth and is our lead developper. He is currently our C++ expert and is also the one that is working on the new Formula AI. Any questions regarding the formula AI should be directed to him.

==== Mordante ====
Many of the possible projects involve the code for which he is an area expert. Also, many of the possible projects currently listed on the ideas page require GUI parts to work. Given that Mordante wants to tackle a rewrite of large parts of this, he will be our expert there as well as already being our area expert for the terrain engine.

==== Elias Pscherning (elias) ====
He wrote the original version of campgen and as such will know a lot about what is needed to to make such an editor work correctly. The work on a scenario editor might be based upon campgen and as such his knowledge will be really helpful.

==== Karol Nowak (grzywacz) ====
Last year he participated at GSoC as a student, so he will understand the situation of GSoC students. Beside this he is our top expert on embedded devices, and is actively working on the gp2x support.

==== boucman ====
As our "patch monkey" he accustomed to critiquing patches of every kind. Beside this, he knows many areas of the game due to working on applying patches. He is particularly used to answering question from new coders, and doesn't mind explaining trivial stuff.

He was the one who started the "two patches, you're in" policy and the ReferenceWML part of the project

==== Soliton ====
He knows our MP server setup best. Beside this he has already done a lot of work on the MP server himself. So he probably has most knowledge about it and, being one of our MP-developers, might provide important help from the perspective of the MP player community and what is needed there.

==== zookeeper or Mythological or Rhuvaen ====
As our leading WML expert it would be good to have him in the list when it comes to WML specific problems. That is for work on the scenario editor he probably knows best what should be implemented in it and what is a usable way for things.

==== YogiHH or Piotr Cychowski (cycholka) ====
Since they are the two developers who know most about building under Windows, they will probably be really helpful. Either if the student comes from the Windows side, or to help test resulting work to make sure that it does work on Windows and, for the case that it does not, to show them where problems are.

==== Eric S. Raymond (ESR) ====
ESR is our project toolsmith; he has written several tools that semi-automate various aspects of WML maintenance. While most of our developers/designers concentrate on either the C++ core or WML but not both, he has a balanced understanding of both levels and may be helpful in helping students develop a grasp of the overall architecture. Finally, he did the last overhaul of the Wesnoth UI and understands UI design principles; he is well-equipped to guide students working in that area.

==== Noyga ====
Another versatile developer, on the C++ side he doesn't concentrate on a particular area, but know quite well the C++ side of units, abilities and WML. On the WML side he's an expert.

Fosdem2008

2008-02-19T21:05:12Z

Noyga: /* Schedule/Plans */

== General information ==
* Fosdem - http://fosdem.org/2008/
* Dave's talk (Chavanne, Saturday, 15:00-15:45) - http://fosdem.org/2008/schedule/events/240

== Schedule/Plans ==

{| border="1" width="100%"
|-
!
! Arrival
! Departure
! Accomodation
|-
| Boucman
| 22, 22:10 (train: Bruxelles-Midi)
| 24, 18:40 (train: Bruxelles-Midi)
| Hotel Du Congres
|-
| David & Lisa
| 18, morning
| 25, morning
| Novotel Grand Place
|-
| ettin
| 22, 9:15 (BRU)
| 24, 15:25 (BRU)
| Bruegel YH
|-
| grzywacz
| 22, 20:35 (CHA)
| 24, 20:50 (CHA)
| Bruegel YH
|-
| Ivanovic
| 22, lunchtime
| 25, lunchtime
| Bruegel YH
|-
| Mist (aka cycholka)
| 22, 19:30 (train: Bruxelles-Midi)
| 25, lunchtime
| CrownePlaza (Europa)
|-
| Mordante
| 22, lunchtime
| 24, lunchtime
| Bruegel YH
|-
| Noyga (together with boucman)
| 22, 22:10 (train: Bruxelles-Midi)
| 24, 18:40 (train: Bruxelles-Midi)
| Hotel Du Congres
|-
| PingPangQui
| 21st, evening
| 25th, late afternoon
| Bruegel YH (no bed for 23rd yet)
|-
| Rhonda
| 22, 08:40 (BRU)
| 24, 19:50 (BRU)
| NH Brussels City Centre
|-
| YogiHH
| 22, 19:40 (BRU)
| 24, 20:00 (BRU)
| Floris Louise
|-

|}

== Maps ==
* [http://tinyurl.com/3a65gr Bruegel YH]
* [http://tinyurl.com/35br9c Brussels Central (Train Station) → Bruegel YH]
* [http://tinyurl.com/37d9v4 Bruegel YH → Brussels Central (Train Station) → Novotel Grand Place]
* [http://tinyurl.com/2mzns6 Novotel Grand Place]
* [http://tinyurl.com/3dggg3 CrownePlaza (Europa)]
* [http://tinyurl.com/36epxj FOSDEM]
* [http://tinyurl.com/2w4bms Novotel Grand Place -> FOSDEM]

== Transportation ==
Information about how to reach the FOSDEM is listed at the [http://fosdem.org/2008/practical/transportation official transportation subpage].

Short version of how to get there for those that reside in Bruegel YH and Novotel Grand Place:

* Enter Bus 71 (Debrouckere - Central Station ("Gare Centrale") - Delta) somewhere at 'Central Station'
* Leave the bus at "ULB" (crossroads Ave. Adolphe Buyl - Sq. Deveze)
* Walk down Ave. Paul Heger on your right hand.

Fosdem2008

2008-02-19T21:00:50Z

Noyga: /* Schedule/Plans */

== General information ==
* Fosdem - http://fosdem.org/2008/
* Dave's talk (Chavanne, Saturday, 15:00-15:45) - http://fosdem.org/2008/schedule/events/240

== Schedule/Plans ==

{| border="1" width="100%"
|-
!
! Arrival
! Departure
! Accomodation
|-
| Boucman
| 22, 21:10 (train: Bruxelles-Midi)
| 24, 18:40 (train: Bruxelles-Midi)
| Hotel Du Congres
|-
| David & Lisa
| 18, morning
| 25, morning
| Novotel Grand Place
|-
| ettin
| 22, 9:15 (BRU)
| 24, 15:25 (BRU)
| Bruegel YH
|-
| grzywacz
| 22, 20:35 (CHA)
| 24, 20:50 (CHA)
| Bruegel YH
|-
| Ivanovic
| 22, lunchtime
| 25, lunchtime
| Bruegel YH
|-
| Mist (aka cycholka)
| 22, 19:30 (train: Bruxelles-Midi)
| 25, lunchtime
| CrownePlaza (Europa)
|-
| Mordante
| 22, lunchtime
| 24, lunchtime
| Bruegel YH
|-
| Noyga (together with boucman)
| 22, 21:10 (train: Bruxelles-Midi)
| 24, 18:40 (train: Bruxelles-Midi)
| Hotel Du Congres
|-
| PingPangQui
| 21st, evening
| 25th, late afternoon
| Bruegel YH (no bed for 23rd yet)
|-
| Rhonda
| 22, 08:40 (BRU)
| 24, 19:50 (BRU)
| NH Brussels City Centre
|-
| YogiHH
| 22, 19:40 (BRU)
| 24, 20:00 (BRU)
| Floris Louise
|-

|}

== Maps ==
* [http://tinyurl.com/3a65gr Bruegel YH]
* [http://tinyurl.com/35br9c Brussels Central (Train Station) → Bruegel YH]
* [http://tinyurl.com/37d9v4 Bruegel YH → Brussels Central (Train Station) → Novotel Grand Place]
* [http://tinyurl.com/2mzns6 Novotel Grand Place]
* [http://tinyurl.com/3dggg3 CrownePlaza (Europa)]
* [http://tinyurl.com/36epxj FOSDEM]
* [http://tinyurl.com/2w4bms Novotel Grand Place -> FOSDEM]

== Transportation ==
Information about how to reach the FOSDEM is listed at the [http://fosdem.org/2008/practical/transportation official transportation subpage].

Short version of how to get there for those that reside in Bruegel YH and Novotel Grand Place:

* Enter Bus 71 (Debrouckere - Central Station ("Gare Centrale") - Delta) somewhere at 'Central Station'
* Leave the bus at "ULB" (crossroads Ave. Adolphe Buyl - Sq. Deveze)
* Walk down Ave. Paul Heger on your right hand.

FrenchTranslation

2008-02-11T21:06:52Z

Noyga: /* Aujourd'hui, qui fait quoi ? */

Battle for Wesnoth - Traduction française
== Le mot d'introduction ==

Cette page sert à mieux coordonner l'effort de tous et à donner les informations souvent demandées avant de se lancer dans la traduction française.

== Règles de traduction ==
=== Respect des termes de l'univers de Wesnoth ===
Pour améliorer la cohérence de l'ensemble des traductions, plusieurs Wikis servent de dictionnaires pour décrire l'univers de Wesnoth :
# unités : [[FrenchUnits]] ;
# noms communs : [[NomsCommuns]] ;
# noms propres : [[NomsPropres]].

=== Respect du contexte ===
Il est important de correctement traduire les différents textes. Il ne suffit pas de traduire mot à mot les différentes phrases, il faut aussi faire très attention au contexte.

=== Respect des règles de typographie ===

==== Titres ====
Les titres des campagnes, des scénarios et des chapitres doivent suivre les règles de la langue française. Ces règles se trouvent sur http://fr.wikipedia.org/wiki/Wikip%C3%A9dia:Conventions_typographiques.

==== Ponctuation ====
Les traductions doivent aussi suivre les règles de ponctuation de la langue française, essentielles à un bon affichage du texte ; par exemple, l'utilisation d'une espace fine avant le signe « : » évitera que ce signe ne se trouve en début de ligne d'un texte. Ces règles se trouvent sur http://www.reveenjoie-poesie.com/outils-linguistiques/Typographie_francaise.html.

Il est préférable de ne pas mettre de virgule ni avant le « et », ni avant le « ou » (contrairement à l'anglais).

Remarque : sous Windows, la combinaison Alt+(0160) permet d'écrire une espace fine (les parenthèses indiquent qu'il faut maintenir la touche Alt appuyée).
Voici d'autres raccourcis : http://www.crdp-montpellier.fr/cd48/tice/trucs/majuscules.htm#win

==== Majuscules ====
Les majuscules doivent être accentuées dans les textes traduits : À, Â, Æ, Ç, É, Ê, È, Î, Ô, Œ, Ù, Û...

Voici également quelques rappels sur des confusions fréquentes :
# pas de majuscules aux noms des races (« nains », « elfes », « orcs », etc.) ;
# majuscules aux noms de clans ou de factions (les humains de « l'Ordre de la Serre Pourpre ») ;
# majuscules aux points cardinaux quand on parle d'une partie d'un tout (« les forêts de l'Ouest » peuvent se trouver à l'est), et minuscule quand on parle de la direction (« aller vers le nord »).

=== Respect des règles de l'orthographe ===
Il est préférable de soigner son orthographe : le CNRS et l'ATILF fournissent un dictionnaire en ligne performant et complet : http://atilf.atilf.fr/

Les rectifications d'orthographes préconisées par l'Académie Française peuvent s'appliquer (http://www.academie-francaise.fr/langue/orthographe/regles.html).

== Principes de traduction pour Wesnoth ==
Le principe est de mettre à jour les fichiers .po, fichiers servant à gérer les traductions dans Wesnoth. Les échanges se font via la mailing list.

=== S'inscrire à la mailing list ===
La mailing list francophone de Wesnoth est l'outil privilégié pour
# d'abord avertir les traducteurs que vous allez commencer une traduction (et éviter de travailler sur le même fichier),
# envoyer ses traductions pour validation ou relecture,
# poser des questions.

Pour s'inscrire à la mailing list, envoyez un mail vide ayant comme sujet « subscribe » (il sera traité par un robot) ; ou cliquez directement ici mailto:wesnoth-request@ml.free.fr?subject=subscribe et envoyez...

Les responsables des différentes mailing list sont ici : [[WesnothTranslations]].

Les archives de la mailing list sont ici : http://news.gmane.org/gmane.games.wesnoth-fr ; vous pouvez vous abonner au serveur de news news.gmane.org (gmane.games.wesnoth-fr).

Il est également possible de discuter sur le canal IRC #wesnothfr (sur irc.freenode.net) ou sur le forum, mais l'équipe de traduction française ne s'y promène que rarement.

=== Récupérer les fichiers .po nécessaires ===
Les fichiers à traduire sont accessibles :
# soit par cette page : http://gettext.wesnoth.org/ (le plus simple),
# soit par le CVS : http://savannah.nongnu.org/cvs/?group=wesnoth (si on aime CVS).

=== Modifier les fichiers .po et vérifier le statut des lignes traduites ===
Plusieurs logiciels permettent de modifier ces fichiers :
# les éditeurs de texte
#* notepad++ (http://notepad-plus.sourceforge.net/fr/site.htm) ;
#* textpad (http://www.textpad.com/);
#* ou, pour Mac, Textwrangler (http://www.barebones.com/products/textwrangler/index.shtml) ;
#* et puis bien d'autres encore...
# ou des éditeurs spécifiques aux fichiers .po
#* poEdit, pour Mac et PC (http://www.poedit.net/) ;
#* KBabel (http://i18n.kde.org/tools/kbabel/) ;
#* gtranslator (http://gtranslator.sourceforge.net/).

Chaque champ de traduction possède un statut :
# si vous traduisez pour la première fois un champ, mettez-le en traduction approximative ("fuzzy" en anglais), et ce même si c'est une traduction très basique ; toute traduction doit être relue au moins une fois avant d'être approuvée ;
# si vous relisez un champ, libre à vous de décider de son statut après votre relecture ;
#* sortez-le de son état approximatif si vous le considérez incontestablement bien traduit ;
#* laissez-le à l'état approximatif et demandez une deuxième relecture si vous n'êtes pas sûr de la traduction.

=== Tester sa traduction ===
Si vous le désirez, vous pouvez immédiatement tester votre traduction :
# enlevez l'option fuzzy de la ligne (ou des lignes) que vous voulez vérifier ;
# générez un fichier compilé « .mo » à partir du fichier texte « .po » ;
#*En ligne de commande : la commande « msgfmt » peut être utilisée avec le nom du fichier « .po » (exemple : « msgfmt mon_fichier.po -o mon_fichier.mo » générera « mon_fichier.mo »).
#*Avec l'éditeur « poedit » : « Fichier -> Préférence », onglet « Editeur, cochez la case « Compiler automatiquement les fichiers .mo lors de la sauvegarde » ; sauvez le fichier.
# copiez votre fichier dans le répertoire contenant les traductions et renommez-le ;
#*Sous Windows, <Répertoire d'installation de Wesnoth>\fr\LC_MESSAGES\<Nom du fichier à tester> (Exemple : C:\Wesnoth\po\fr\LC_MESSAGES\wesnoth-utbs.mo) ;
#*Sous Linux, répertoire en fonction de la distribution (Exemple Mandriva : /usr/share/locale/fr/LC_MESSAGES).
# jouez.... jusqu'au moment où le texte traduit est censé apparaître ; il n'est pas nécessaire de tout reprendre depuis le début, une sauvegarde fonctionne. Un texte traduit sans erreur apparaît... traduit.

Remarque : pour accélérer les tests, vous pouvez utiliser le mode debug de Wesnoth :
#Pour passer en mode débug :
#*taper : (pour ouvrir le mode de commande), puis : debug<entrée>
#*ou taper "wesnoth.exe --debug",
#*ou taper "wesnoth.exe -d"
# pour utiliser le mode débug :
#*":debug" entre en mode debug
#*":n" termine le scénario immédiatement

=== Envoyer sa traduction ===
Une traduction terminée est compressée, puis envoyée à la ML.

Il est préférable, en cas de relecture, de signaler les modifications dans le corps du mail, par exemple en faisant comme ci-dessous :
#Exemple 1 (refonte d'une phrase) : N° ligne Anciene version => Nouvelle version.
#Exemple 2 (correction d'une faute, indiquée par des *) : N°Ligne Ancien*n*e version

Il est également possible de générer un fichier différentiel entre l'ancienne et la nouvelle version ; mais l'expérience semble montrer que cela est peu relu.
Cette techique est surtout à utiliser qu'en cas de modifications massives (cas où le suivi ligne à ligne serait complexe et lourd).

=== Attention ===
Il y a un bug récurent dans les fichiers po : lorsque la phrase traduite commence par "$", rien ne s'affiche

dans le jeu. Pour corriger le problème, il suffit de mettre un simple espace devant le signe (seulement quand la phrase commence par $)

== Aujourd'hui, qui fait quoi ? ==
Ce chapitre vous permet de savoir qui fait quoi...

Date de dernière mise à jour : 11/02/2008
* Traductions
** wesnoth (.po principal) : Noyga
** wesnoth-multiplayer (Multijoueur) : Noyga
** wesnoth-httt (Heir To The Throne / L'Héritier du trône) : La_vie_en_Wose
** wesnoth-thot (The Hammer of Thursagan) : Dylann/gotrek860
** wesnoth-nr (Northern Rebirth) : Damien
** wesnoth-tsg (The South Guard) : Damien
** wesnoth-l (Liberty) : Pierre
** wesnoth-did (Descent in the Darkness) : Jean-joseph
* Relectures / À relire
** wesnoth-lib (Librairie commune) : Noyga

FrenchTranslation

2008-02-11T11:25:50Z

Noyga: /* Aujourd'hui, qui fait quoi ? */

Battle for Wesnoth - Traduction française
== Le mot d'introduction ==

Cette page sert à mieux coordonner l'effort de tous et à donner les informations souvent demandées avant de se lancer dans la traduction française.

== Règles de traduction ==
=== Respect des termes de l'univers de Wesnoth ===
Pour améliorer la cohérence de l'ensemble des traductions, plusieurs Wikis servent de dictionnaires pour décrire l'univers de Wesnoth :
# unités : [[FrenchUnits]] ;
# noms communs : [[NomsCommuns]] ;
# noms propres : [[NomsPropres]].

=== Respect du contexte ===
Il est important de correctement traduire les différents textes. Il ne suffit pas de traduire mot à mot les différentes phrases, il faut aussi faire très attention au contexte.

=== Respect des règles de typographie ===

==== Titres ====
Les titres des campagnes, des scénarios et des chapitres doivent suivre les règles de la langue française. Ces règles se trouvent sur http://fr.wikipedia.org/wiki/Wikip%C3%A9dia:Conventions_typographiques.

==== Ponctuation ====
Les traductions doivent aussi suivre les règles de ponctuation de la langue française, essentielles à un bon affichage du texte ; par exemple, l'utilisation d'une espace fine avant le signe « : » évitera que ce signe ne se trouve en début de ligne d'un texte. Ces règles se trouvent sur http://www.reveenjoie-poesie.com/outils-linguistiques/Typographie_francaise.html.

Il est préférable de ne pas mettre de virgule ni avant le « et », ni avant le « ou » (contrairement à l'anglais).

Remarque : sous Windows, la combinaison Alt+(0160) permet d'écrire une espace fine (les parenthèses indiquent qu'il faut maintenir la touche Alt appuyée).
Voici d'autres raccourcis : http://www.crdp-montpellier.fr/cd48/tice/trucs/majuscules.htm#win

==== Majuscules ====
Les majuscules doivent être accentuées dans les textes traduits : À, Â, Æ, Ç, É, Ê, È, Î, Ô, Œ, Ù, Û...

Voici également quelques rappels sur des confusions fréquentes :
# pas de majuscules aux noms des races (« nains », « elfes », « orcs », etc.) ;
# majuscules aux noms de clans ou de factions (les humains de « l'Ordre de la Serre Pourpre ») ;
# majuscules aux points cardinaux quand on parle d'une partie d'un tout (« les forêts de l'Ouest » peuvent se trouver à l'est), et minuscule quand on parle de la direction (« aller vers le nord »).

=== Respect des règles de l'orthographe ===
Il est préférable de soigner son orthographe : le CNRS et l'ATILF fournissent un dictionnaire en ligne performant et complet : http://atilf.atilf.fr/

Les rectifications d'orthographes préconisées par l'Académie Française peuvent s'appliquer (http://www.academie-francaise.fr/langue/orthographe/regles.html).

== Principes de traduction pour Wesnoth ==
Le principe est de mettre à jour les fichiers .po, fichiers servant à gérer les traductions dans Wesnoth. Les échanges se font via la mailing list.

=== S'inscrire à la mailing list ===
La mailing list francophone de Wesnoth est l'outil privilégié pour
# d'abord avertir les traducteurs que vous allez commencer une traduction (et éviter de travailler sur le même fichier),
# envoyer ses traductions pour validation ou relecture,
# poser des questions.

Pour s'inscrire à la mailing list, envoyez un mail vide ayant comme sujet « subscribe » (il sera traité par un robot) ; ou cliquez directement ici mailto:wesnoth-request@ml.free.fr?subject=subscribe et envoyez...

Les responsables des différentes mailing list sont ici : [[WesnothTranslations]].

Les archives de la mailing list sont ici : http://news.gmane.org/gmane.games.wesnoth-fr ; vous pouvez vous abonner au serveur de news news.gmane.org (gmane.games.wesnoth-fr).

Il est également possible de discuter sur le canal IRC #wesnothfr (sur irc.freenode.net) ou sur le forum, mais l'équipe de traduction française ne s'y promène que rarement.

=== Récupérer les fichiers .po nécessaires ===
Les fichiers à traduire sont accessibles :
# soit par cette page : http://gettext.wesnoth.org/ (le plus simple),
# soit par le CVS : http://savannah.nongnu.org/cvs/?group=wesnoth (si on aime CVS).

=== Modifier les fichiers .po et vérifier le statut des lignes traduites ===
Plusieurs logiciels permettent de modifier ces fichiers :
# les éditeurs de texte
#* notepad++ (http://notepad-plus.sourceforge.net/fr/site.htm) ;
#* textpad (http://www.textpad.com/);
#* ou, pour Mac, Textwrangler (http://www.barebones.com/products/textwrangler/index.shtml) ;
#* et puis bien d'autres encore...
# ou des éditeurs spécifiques aux fichiers .po
#* poEdit, pour Mac et PC (http://www.poedit.net/) ;
#* KBabel (http://i18n.kde.org/tools/kbabel/) ;
#* gtranslator (http://gtranslator.sourceforge.net/).

Chaque champ de traduction possède un statut :
# si vous traduisez pour la première fois un champ, mettez-le en traduction approximative ("fuzzy" en anglais), et ce même si c'est une traduction très basique ; toute traduction doit être relue au moins une fois avant d'être approuvée ;
# si vous relisez un champ, libre à vous de décider de son statut après votre relecture ;
#* sortez-le de son état approximatif si vous le considérez incontestablement bien traduit ;
#* laissez-le à l'état approximatif et demandez une deuxième relecture si vous n'êtes pas sûr de la traduction.

=== Tester sa traduction ===
Si vous le désirez, vous pouvez immédiatement tester votre traduction :
# enlevez l'option fuzzy de la ligne (ou des lignes) que vous voulez vérifier ;
# générez un fichier compilé « .mo » à partir du fichier texte « .po » ;
#*En ligne de commande : la commande « msgfmt » peut être utilisée avec le nom du fichier « .po » (exemple : « msgfmt mon_fichier.po -o mon_fichier.mo » générera « mon_fichier.mo »).
#*Avec l'éditeur « poedit » : « Fichier -> Préférence », onglet « Editeur, cochez la case « Compiler automatiquement les fichiers .mo lors de la sauvegarde » ; sauvez le fichier.
# copiez votre fichier dans le répertoire contenant les traductions et renommez-le ;
#*Sous Windows, <Répertoire d'installation de Wesnoth>\fr\LC_MESSAGES\<Nom du fichier à tester> (Exemple : C:\Wesnoth\po\fr\LC_MESSAGES\wesnoth-utbs.mo) ;
#*Sous Linux, répertoire en fonction de la distribution (Exemple Mandriva : /usr/share/locale/fr/LC_MESSAGES).
# jouez.... jusqu'au moment où le texte traduit est censé apparaître ; il n'est pas nécessaire de tout reprendre depuis le début, une sauvegarde fonctionne. Un texte traduit sans erreur apparaît... traduit.

Remarque : pour accélérer les tests, vous pouvez utiliser le mode debug de Wesnoth :
#Pour passer en mode débug :
#*taper : (pour ouvrir le mode de commande), puis : debug<entrée>
#*ou taper "wesnoth.exe --debug",
#*ou taper "wesnoth.exe -d"
# pour utiliser le mode débug :
#*":debug" entre en mode debug
#*":n" termine le scénario immédiatement

=== Envoyer sa traduction ===
Une traduction terminée est compressée, puis envoyée à la ML.

Il est préférable, en cas de relecture, de signaler les modifications dans le corps du mail, par exemple en faisant comme ci-dessous :
#Exemple 1 (refonte d'une phrase) : N° ligne Anciene version => Nouvelle version.
#Exemple 2 (correction d'une faute, indiquée par des *) : N°Ligne Ancien*n*e version

Il est également possible de générer un fichier différentiel entre l'ancienne et la nouvelle version ; mais l'expérience semble montrer que cela est peu relu.
Cette techique est surtout à utiliser qu'en cas de modifications massives (cas où le suivi ligne à ligne serait complexe et lourd).

=== Attention ===
Il y a un bug récurent dans les fichiers po : lorsque la phrase traduite commence par "$", rien ne s'affiche

dans le jeu. Pour corriger le problème, il suffit de mettre un simple espace devant le signe (seulement quand la phrase commence par $)

== Aujourd'hui, qui fait quoi ? ==
Ce chapitre vous permet de savoir qui fait quoi...

Date de dernière mise à jour : 11/02/2008
* Traductions
** wesnoth (.po principal) : Noyga
** wesnoth-multiplayer (Multijoueur) : Noyga
** wesnoth-httt (Heir To The Throne / L'Héritier du trône) : La_vie_en_Wose
** wesnoth-thot (The Hammer of Thursagan) : Dylann/gotrek860
** wesnoth-nr (Northern Rebirth) : Damien
** wesnoth-tsg (The South Guard) : Damien
** wesnoth-l (Liberty) : Pierre
* Relectures / À relire
** wesnoth-lib (Librairie commune) : Noyga

FrenchTranslation

2008-02-11T11:25:01Z

Noyga: /* Aujourd'hui, qui fait quoi ? */

Battle for Wesnoth - Traduction française
== Le mot d'introduction ==

Cette page sert à mieux coordonner l'effort de tous et à donner les informations souvent demandées avant de se lancer dans la traduction française.

== Règles de traduction ==
=== Respect des termes de l'univers de Wesnoth ===
Pour améliorer la cohérence de l'ensemble des traductions, plusieurs Wikis servent de dictionnaires pour décrire l'univers de Wesnoth :
# unités : [[FrenchUnits]] ;
# noms communs : [[NomsCommuns]] ;
# noms propres : [[NomsPropres]].

=== Respect du contexte ===
Il est important de correctement traduire les différents textes. Il ne suffit pas de traduire mot à mot les différentes phrases, il faut aussi faire très attention au contexte.

=== Respect des règles de typographie ===

==== Titres ====
Les titres des campagnes, des scénarios et des chapitres doivent suivre les règles de la langue française. Ces règles se trouvent sur http://fr.wikipedia.org/wiki/Wikip%C3%A9dia:Conventions_typographiques.

==== Ponctuation ====
Les traductions doivent aussi suivre les règles de ponctuation de la langue française, essentielles à un bon affichage du texte ; par exemple, l'utilisation d'une espace fine avant le signe « : » évitera que ce signe ne se trouve en début de ligne d'un texte. Ces règles se trouvent sur http://www.reveenjoie-poesie.com/outils-linguistiques/Typographie_francaise.html.

Il est préférable de ne pas mettre de virgule ni avant le « et », ni avant le « ou » (contrairement à l'anglais).

Remarque : sous Windows, la combinaison Alt+(0160) permet d'écrire une espace fine (les parenthèses indiquent qu'il faut maintenir la touche Alt appuyée).
Voici d'autres raccourcis : http://www.crdp-montpellier.fr/cd48/tice/trucs/majuscules.htm#win

==== Majuscules ====
Les majuscules doivent être accentuées dans les textes traduits : À, Â, Æ, Ç, É, Ê, È, Î, Ô, Œ, Ù, Û...

Voici également quelques rappels sur des confusions fréquentes :
# pas de majuscules aux noms des races (« nains », « elfes », « orcs », etc.) ;
# majuscules aux noms de clans ou de factions (les humains de « l'Ordre de la Serre Pourpre ») ;
# majuscules aux points cardinaux quand on parle d'une partie d'un tout (« les forêts de l'Ouest » peuvent se trouver à l'est), et minuscule quand on parle de la direction (« aller vers le nord »).

=== Respect des règles de l'orthographe ===
Il est préférable de soigner son orthographe : le CNRS et l'ATILF fournissent un dictionnaire en ligne performant et complet : http://atilf.atilf.fr/

Les rectifications d'orthographes préconisées par l'Académie Française peuvent s'appliquer (http://www.academie-francaise.fr/langue/orthographe/regles.html).

== Principes de traduction pour Wesnoth ==
Le principe est de mettre à jour les fichiers .po, fichiers servant à gérer les traductions dans Wesnoth. Les échanges se font via la mailing list.

=== S'inscrire à la mailing list ===
La mailing list francophone de Wesnoth est l'outil privilégié pour
# d'abord avertir les traducteurs que vous allez commencer une traduction (et éviter de travailler sur le même fichier),
# envoyer ses traductions pour validation ou relecture,
# poser des questions.

Pour s'inscrire à la mailing list, envoyez un mail vide ayant comme sujet « subscribe » (il sera traité par un robot) ; ou cliquez directement ici mailto:wesnoth-request@ml.free.fr?subject=subscribe et envoyez...

Les responsables des différentes mailing list sont ici : [[WesnothTranslations]].

Les archives de la mailing list sont ici : http://news.gmane.org/gmane.games.wesnoth-fr ; vous pouvez vous abonner au serveur de news news.gmane.org (gmane.games.wesnoth-fr).

Il est également possible de discuter sur le canal IRC #wesnothfr (sur irc.freenode.net) ou sur le forum, mais l'équipe de traduction française ne s'y promène que rarement.

=== Récupérer les fichiers .po nécessaires ===
Les fichiers à traduire sont accessibles :
# soit par cette page : http://gettext.wesnoth.org/ (le plus simple),
# soit par le CVS : http://savannah.nongnu.org/cvs/?group=wesnoth (si on aime CVS).

=== Modifier les fichiers .po et vérifier le statut des lignes traduites ===
Plusieurs logiciels permettent de modifier ces fichiers :
# les éditeurs de texte
#* notepad++ (http://notepad-plus.sourceforge.net/fr/site.htm) ;
#* textpad (http://www.textpad.com/);
#* ou, pour Mac, Textwrangler (http://www.barebones.com/products/textwrangler/index.shtml) ;
#* et puis bien d'autres encore...
# ou des éditeurs spécifiques aux fichiers .po
#* poEdit, pour Mac et PC (http://www.poedit.net/) ;
#* KBabel (http://i18n.kde.org/tools/kbabel/) ;
#* gtranslator (http://gtranslator.sourceforge.net/).

Chaque champ de traduction possède un statut :
# si vous traduisez pour la première fois un champ, mettez-le en traduction approximative ("fuzzy" en anglais), et ce même si c'est une traduction très basique ; toute traduction doit être relue au moins une fois avant d'être approuvée ;
# si vous relisez un champ, libre à vous de décider de son statut après votre relecture ;
#* sortez-le de son état approximatif si vous le considérez incontestablement bien traduit ;
#* laissez-le à l'état approximatif et demandez une deuxième relecture si vous n'êtes pas sûr de la traduction.

=== Tester sa traduction ===
Si vous le désirez, vous pouvez immédiatement tester votre traduction :
# enlevez l'option fuzzy de la ligne (ou des lignes) que vous voulez vérifier ;
# générez un fichier compilé « .mo » à partir du fichier texte « .po » ;
#*En ligne de commande : la commande « msgfmt » peut être utilisée avec le nom du fichier « .po » (exemple : « msgfmt mon_fichier.po -o mon_fichier.mo » générera « mon_fichier.mo »).
#*Avec l'éditeur « poedit » : « Fichier -> Préférence », onglet « Editeur, cochez la case « Compiler automatiquement les fichiers .mo lors de la sauvegarde » ; sauvez le fichier.
# copiez votre fichier dans le répertoire contenant les traductions et renommez-le ;
#*Sous Windows, <Répertoire d'installation de Wesnoth>\fr\LC_MESSAGES\<Nom du fichier à tester> (Exemple : C:\Wesnoth\po\fr\LC_MESSAGES\wesnoth-utbs.mo) ;
#*Sous Linux, répertoire en fonction de la distribution (Exemple Mandriva : /usr/share/locale/fr/LC_MESSAGES).
# jouez.... jusqu'au moment où le texte traduit est censé apparaître ; il n'est pas nécessaire de tout reprendre depuis le début, une sauvegarde fonctionne. Un texte traduit sans erreur apparaît... traduit.

Remarque : pour accélérer les tests, vous pouvez utiliser le mode debug de Wesnoth :
#Pour passer en mode débug :
#*taper : (pour ouvrir le mode de commande), puis : debug<entrée>
#*ou taper "wesnoth.exe --debug",
#*ou taper "wesnoth.exe -d"
# pour utiliser le mode débug :
#*":debug" entre en mode debug
#*":n" termine le scénario immédiatement

=== Envoyer sa traduction ===
Une traduction terminée est compressée, puis envoyée à la ML.

Il est préférable, en cas de relecture, de signaler les modifications dans le corps du mail, par exemple en faisant comme ci-dessous :
#Exemple 1 (refonte d'une phrase) : N° ligne Anciene version => Nouvelle version.
#Exemple 2 (correction d'une faute, indiquée par des *) : N°Ligne Ancien*n*e version

Il est également possible de générer un fichier différentiel entre l'ancienne et la nouvelle version ; mais l'expérience semble montrer que cela est peu relu.
Cette techique est surtout à utiliser qu'en cas de modifications massives (cas où le suivi ligne à ligne serait complexe et lourd).

=== Attention ===
Il y a un bug récurent dans les fichiers po : lorsque la phrase traduite commence par "$", rien ne s'affiche

dans le jeu. Pour corriger le problème, il suffit de mettre un simple espace devant le signe (seulement quand la phrase commence par $)

== Aujourd'hui, qui fait quoi ? ==
Ce chapitre vous permet de savoir qui fait quoi...

Date de dernière mise à jour : 08/02/2008
* Traductions
** wesnoth (.po principal) : Noyga
** wesnoth-multiplayer (Multijoueur) : Noyga
** wesnoth-httt (Heir To The Throne / L'Héritier du trône) : La_vie_en_Wose
** wesnoth-thot (The Hammer of Thursagan) : Dylann/gotrek860
** wesnoth-nr (Northern Rebirth) : Damien
** wesnoth-tsg (The South Guard) : Damien
** wesnoth-l (Liberty) : Pierre
* Relectures / À relire
** wesnoth-lib (Librairie commune) : Noyga

FrenchTranslation

2008-02-09T09:49:44Z

Noyga: /* Aujourd'hui, qui fait quoi ? */

Battle for Wesnoth - Traduction française
== Le mot d'introduction ==

Cette page sert à mieux coordonner l'effort de tous et à donner les informations souvent demandées avant de se lancer dans la traduction française.

== Règles de traduction ==
=== Respect des termes de l'univers de Wesnoth ===
Pour améliorer la cohérence de l'ensemble des traductions, plusieurs Wikis servent de dictionnaires pour décrire l'univers de Wesnoth :
# unités : [[FrenchUnits]] ;
# noms communs : [[NomsCommuns]] ;
# noms propres : [[NomsPropres]].

=== Respect du contexte ===
Il est important de correctement traduire les différents textes. Il ne suffit pas de traduire mot à mot les différentes phrases, il faut aussi faire très attention au contexte.

=== Respect des règles de typographie ===

==== Titres ====
Les titres des campagnes, des scénarios et des chapitres doivent suivre les règles de la langue française. Ces règles se trouvent sur http://fr.wikipedia.org/wiki/Wikip%C3%A9dia:Conventions_typographiques.

==== Ponctuation ====
Les traductions doivent aussi suivre les règles de ponctuation de la langue française, essentielles à un bon affichage du texte ; par exemple, l'utilisation d'une espace fine avant le signe « : » évitera que ce signe ne se trouve en début de ligne d'un texte. Ces règles se trouvent sur http://www.reveenjoie-poesie.com/outils-linguistiques/Typographie_francaise.html.

Il est préférable de ne pas mettre de virgule ni avant le « et », ni avant le « ou » (contrairement à l'anglais).

Remarque : sous Windows, la combinaison Alt+(0160) permet d'écrire une espace fine (les parenthèses indiquent qu'il faut maintenir la touche Alt appuyée).
Voici d'autres raccourcis : http://www.crdp-montpellier.fr/cd48/tice/trucs/majuscules.htm#win

==== Majuscules ====
Les majuscules doivent être accentuées dans les textes traduits : À, Â, Æ, Ç, É, Ê, È, Î, Ô, Œ, Ù, Û...

Voici également quelques rappels sur des confusions fréquentes :
# pas de majuscules aux noms des races (« nains », « elfes », « orcs », etc.) ;
# majuscules aux noms de clans ou de factions (les humains de « l'Ordre de la Serre Pourpre ») ;
# majuscules aux points cardinaux quand on parle d'une partie d'un tout (« les forêts de l'Ouest » peuvent se trouver à l'est), et minuscule quand on parle de la direction (« aller vers le nord »).

=== Respect des règles de l'orthographe ===
Il est préférable de soigner son orthographe : le CNRS et l'ATILF fournissent un dictionnaire en ligne performant et complet : http://atilf.atilf.fr/

Les rectifications d'orthographes préconisées par l'Académie Française peuvent s'appliquer (http://www.academie-francaise.fr/langue/orthographe/regles.html).

== Principes de traduction pour Wesnoth ==
Le principe est de mettre à jour les fichiers .po, fichiers servant à gérer les traductions dans Wesnoth. Les échanges se font via la mailing list.

=== S'inscrire à la mailing list ===
La mailing list francophone de Wesnoth est l'outil privilégié pour
# d'abord avertir les traducteurs que vous allez commencer une traduction (et éviter de travailler sur le même fichier),
# envoyer ses traductions pour validation ou relecture,
# poser des questions.

Pour s'inscrire à la mailing list, envoyez un mail vide ayant comme sujet « subscribe » (il sera traité par un robot) ; ou cliquez directement ici mailto:wesnoth-request@ml.free.fr?subject=subscribe et envoyez...

Les responsables des différentes mailing list sont ici : [[WesnothTranslations]].

Les archives de la mailing list sont ici : http://news.gmane.org/gmane.games.wesnoth-fr ; vous pouvez vous abonner au serveur de news news.gmane.org (gmane.games.wesnoth-fr).

Il est également possible de discuter sur le canal IRC #wesnothfr (sur irc.freenode.net) ou sur le forum, mais l'équipe de traduction française ne s'y promène que rarement.

=== Récupérer les fichiers .po nécessaires ===
Les fichiers à traduire sont accessibles :
# soit par cette page : http://gettext.wesnoth.org/ (le plus simple),
# soit par le CVS : http://savannah.nongnu.org/cvs/?group=wesnoth (si on aime CVS).

=== Modifier les fichiers .po et vérifier le statut des lignes traduites ===
Plusieurs logiciels permettent de modifier ces fichiers :
# les éditeurs de texte
#* notepad++ (http://notepad-plus.sourceforge.net/fr/site.htm) ;
#* textpad (http://www.textpad.com/);
#* ou, pour Mac, Textwrangler (http://www.barebones.com/products/textwrangler/index.shtml) ;
#* et puis bien d'autres encore...
# ou des éditeurs spécifiques aux fichiers .po
#* poEdit, pour Mac et PC (http://www.poedit.net/) ;
#* KBabel (http://i18n.kde.org/tools/kbabel/) ;
#* gtranslator (http://gtranslator.sourceforge.net/).

Chaque champ de traduction possède un statut :
# si vous traduisez pour la première fois un champ, mettez-le en traduction approximative ("fuzzy" en anglais), et ce même si c'est une traduction très basique ; toute traduction doit être relue au moins une fois avant d'être approuvée ;
# si vous relisez un champ, libre à vous de décider de son statut après votre relecture ;
#* sortez-le de son état approximatif si vous le considérez incontestablement bien traduit ;
#* laissez-le à l'état approximatif et demandez une deuxième relecture si vous n'êtes pas sûr de la traduction.

=== Tester sa traduction ===
Si vous le désirez, vous pouvez immédiatement tester votre traduction :
# enlevez l'option fuzzy de la ligne (ou des lignes) que vous voulez vérifier ;
# générez un fichier compilé « .mo » à partir du fichier texte « .po » ;
#*En ligne de commande : la commande « msgfmt » peut être utilisée avec le nom du fichier « .po » (exemple : « msgfmt mon_fichier.po -o mon_fichier.mo » générera « mon_fichier.mo »).
#*Avec l'éditeur « poedit » : « Fichier -> Préférence », onglet « Editeur, cochez la case « Compiler automatiquement les fichiers .mo lors de la sauvegarde » ; sauvez le fichier.
# copiez votre fichier dans le répertoire contenant les traductions et renommez-le ;
#*Sous Windows, <Répertoire d'installation de Wesnoth>\fr\LC_MESSAGES\<Nom du fichier à tester> (Exemple : C:\Wesnoth\po\fr\LC_MESSAGES\wesnoth-utbs.mo) ;
#*Sous Linux, répertoire en fonction de la distribution (Exemple Mandriva : /usr/share/locale/fr/LC_MESSAGES).
# jouez.... jusqu'au moment où le texte traduit est censé apparaître ; il n'est pas nécessaire de tout reprendre depuis le début, une sauvegarde fonctionne. Un texte traduit sans erreur apparaît... traduit.

Remarque : pour accélérer les tests, vous pouvez utiliser le mode debug de Wesnoth :
#Pour passer en mode débug :
#*taper : (pour ouvrir le mode de commande), puis : debug<entrée>
#*ou taper "wesnoth.exe --debug",
#*ou taper "wesnoth.exe -d"
# pour utiliser le mode débug :
#*":debug" entre en mode debug
#*":n" termine le scénario immédiatement

=== Envoyer sa traduction ===
Une traduction terminée est compressée, puis envoyée à la ML.

Il est préférable, en cas de relecture, de signaler les modifications dans le corps du mail, par exemple en faisant comme ci-dessous :
#Exemple 1 (refonte d'une phrase) : N° ligne Anciene version => Nouvelle version.
#Exemple 2 (correction d'une faute, indiquée par des *) : N°Ligne Ancien*n*e version

Il est également possible de générer un fichier différentiel entre l'ancienne et la nouvelle version ; mais l'expérience semble montrer que cela est peu relu.
Cette techique est surtout à utiliser qu'en cas de modifications massives (cas où le suivi ligne à ligne serait complexe et lourd).

=== Attention ===
Il y a un bug récurent dans les fichiers po : lorsque la phrase traduite commence par "$", rien ne s'affiche

dans le jeu. Pour corriger le problème, il suffit de mettre un simple espace devant le signe (seulement quand la phrase commence par $)

== Aujourd'hui, qui fait quoi ? ==
Ce chapitre vous permet de savoir qui fait quoi...

Date de dernière mise à jour : 08/02/2008
* Traductions
** wesnoth (.po principal) : Noyga
** wesnoth-multiplayer (Multijoueur) : Noyga
** wesnoth-httt (Heir To The Throne / L'Héritier du trône) : La_vie_en_Wose
** wesnoth-thot (The Hammer of Thursagan) : Dylann/gotrek860
** wesnoth-nr (Northern Rebirth) : Damien
** wesnoth-tsg (The South Guard) : Damien
* Relectures / À relire
** wesnoth-lib (Librairie commune) : Noyga

FrenchTranslation

2008-02-03T18:18:05Z

Noyga: /* Aujourd'hui, qui fait quoi ? */

Battle for Wesnoth - Traduction française
== Le mot d'introduction ==

Cette page sert à mieux coordonner l'effort de tous et à donner les informations souvent demandées avant de se lancer dans la traduction française.

== Règles de traduction ==
=== Respect des termes de l'univers de Wesnoth ===
Pour améliorer la cohérence de l'ensemble des traductions, plusieurs Wikis servent de dictionnaires pour décrire l'univers de Wesnoth :
# unités : [[FrenchUnits]] ;
# noms communs : [[NomsCommuns]] ;
# noms propres : [[NomsPropres]].

=== Respect du contexte ===
Il est important de correctement traduire les différents textes. Il ne suffit pas de traduire mot à mot les différentes phrases, il faut aussi faire très attention au contexte.

=== Respect des règles de typographie ===

==== Titres ====
Les titres des campagnes, des scénarios et des chapitres doivent suivre les règles de la langue française. Ces règles se trouvent sur http://fr.wikipedia.org/wiki/Wikip%C3%A9dia:Conventions_typographiques.

==== Ponctuation ====
Les traductions doivent aussi suivre les règles de ponctuation de la langue française, essentielles à un bon affichage du texte ; par exemple, l'utilisation d'une espace fine avant le signe « : » évitera que ce signe ne se trouve en début de ligne d'un texte. Ces règles se trouvent sur http://www.reveenjoie-poesie.com/outils-linguistiques/Typographie_francaise.html.

Il est préférable de ne pas mettre de virgule ni avant le « et », ni avant le « ou » (contrairement à l'anglais).

Remarque : sous Windows, la combinaison Alt+(0160) permet d'écrire une espace fine (les parenthèses indiquent qu'il faut maintenir la touche Alt appuyée).
Voici d'autres raccourcis : http://www.crdp-montpellier.fr/cd48/tice/trucs/majuscules.htm#win

==== Majuscules ====
Les majuscules doivent être accentuées dans les textes traduits : À, Â, Æ, Ç, É, Ê, È, Î, Ô, Œ, Ù, Û...

Voici également quelques rappels sur des confusions fréquentes :
# pas de majuscules aux noms des races (« nains », « elfes », « orcs », etc.) ;
# majuscules aux noms de clans ou de factions (les humains de « l'Ordre de la Serre Pourpre ») ;
# majuscules aux points cardinaux quand on parle d'une partie d'un tout (« les forêts de l'Ouest » peuvent se trouver à l'est), et minuscule quand on parle de la direction (« aller vers le nord »).

=== Respect des règles de l'orthographe ===
Il est préférable de soigner son orthographe : le CNRS et l'ATILF fournissent un dictionnaire en ligne performant et complet : http://atilf.atilf.fr/

Les rectifications d'orthographes préconisées par l'Académie Française peuvent s'appliquer (http://www.academie-francaise.fr/langue/orthographe/regles.html).

== Principes de traduction pour Wesnoth ==
Le principe est de mettre à jour les fichiers .po, fichiers servant à gérer les traductions dans Wesnoth. Les échanges se font via la mailing list.

=== S'inscrire à la mailing list ===
La mailing list francophone de Wesnoth est l'outil privilégié pour
# d'abord avertir les traducteurs que vous allez commencer une traduction (et éviter de travailler sur le même fichier),
# envoyer ses traductions pour validation ou relecture,
# poser des questions.

Pour s'inscrire à la mailing list, envoyez un mail vide ayant comme sujet « subscribe » (il sera traité par un robot) ; ou cliquez directement ici mailto:wesnoth-request@ml.free.fr?subject=subscribe et envoyez...

Les responsables des différentes mailing list sont ici : [[WesnothTranslations]].

Les archives de la mailing list sont ici : http://news.gmane.org/gmane.games.wesnoth-fr ; vous pouvez vous abonner au serveur de news news.gmane.org (gmane.games.wesnoth-fr).

Il est également possible de discuter sur le canal IRC #wesnothfr (sur irc.freenode.net) ou sur le forum, mais l'équipe de traduction française ne s'y promène que rarement.

=== Récupérer les fichiers .po nécessaires ===
Les fichiers à traduire sont accessibles :
# soit par cette page : http://gettext.wesnoth.org/ (le plus simple),
# soit par le CVS : http://savannah.nongnu.org/cvs/?group=wesnoth (si on aime CVS).

=== Modifier les fichiers .po et vérifier le statut des lignes traduites ===
Plusieurs logiciels permettent de modifier ces fichiers :
# les éditeurs de texte
#* notepad++ (http://notepad-plus.sourceforge.net/fr/site.htm) ;
#* textpad (http://www.textpad.com/);
#* ou, pour Mac, Textwrangler (http://www.barebones.com/products/textwrangler/index.shtml) ;
#* et puis bien d'autres encore...
# ou des éditeurs spécifiques aux fichiers .po
#* poEdit, pour Mac et PC (http://www.poedit.net/) ;
#* KBabel (http://i18n.kde.org/tools/kbabel/) ;
#* gtranslator (http://gtranslator.sourceforge.net/).

Chaque champ de traduction possède un statut :
# si vous traduisez pour la première fois un champ, mettez-le en traduction approximative ("fuzzy" en anglais), et ce même si c'est une traduction très basique ; toute traduction doit être relue au moins une fois avant d'être approuvée ;
# si vous relisez un champ, libre à vous de décider de son statut après votre relecture ;
#* sortez-le de son état approximatif si vous le considérez incontestablement bien traduit ;
#* laissez-le à l'état approximatif et demandez une deuxième relecture si vous n'êtes pas sûr de la traduction.

=== Tester sa traduction ===
Si vous le désirez, vous pouvez immédiatement tester votre traduction :
# enlevez l'option fuzzy de la ligne (ou des lignes) que vous voulez vérifier ;
# générez un fichier compilé « .mo » à partir du fichier texte « .po » ;
#*En ligne de commande : la commande « msgfmt » peut être utilisée avec le nom du fichier « .po » (exemple : « msgfmt mon_fichier.po -o mon_fichier.mo » générera « mon_fichier.mo »).
#*Avec l'éditeur « poedit » : « Fichier -> Préférence », onglet « Editeur, cochez la case « Compiler automatiquement les fichiers .mo lors de la sauvegarde » ; sauvez le fichier.
# copiez votre fichier dans le répertoire contenant les traductions et renommez-le ;
#*Sous Windows, <Répertoire d'installation de Wesnoth>\fr\LC_MESSAGES\<Nom du fichier à tester> (Exemple : C:\Wesnoth\po\fr\LC_MESSAGES\wesnoth-utbs.mo) ;
#*Sous Linux, répertoire en fonction de la distribution (Exemple Mandriva : /usr/share/locale/fr/LC_MESSAGES).
# jouez.... jusqu'au moment où le texte traduit est censé apparaître ; il n'est pas nécessaire de tout reprendre depuis le début, une sauvegarde fonctionne. Un texte traduit sans erreur apparaît... traduit.

Remarque : pour accélérer les tests, vous pouvez utiliser le mode debug de Wesnoth :
#Pour passer en mode débug :
#*taper : (pour ouvrir le mode de commande), puis : debug<entrée>
#*ou taper "wesnoth.exe --debug",
#*ou taper "wesnoth.exe -d"
# pour utiliser le mode débug :
#*":debug" entre en mode debug
#*":n" termine le scénario immédiatement

=== Envoyer sa traduction ===
Une traduction terminée est compressée, puis envoyée à la ML.

Il est préférable, en cas de relecture, de signaler les modifications dans le corps du mail, par exemple en faisant comme ci-dessous :
#Exemple 1 (refonte d'une phrase) : N° ligne Anciene version => Nouvelle version.
#Exemple 2 (correction d'une faute, indiquée par des *) : N°Ligne Ancien*n*e version

Il est également possible de générer un fichier différentiel entre l'ancienne et la nouvelle version ; mais l'expérience semble montrer que cela est peu relu.
Cette techique est surtout à utiliser qu'en cas de modifications massives (cas où le suivi ligne à ligne serait complexe et lourd).

=== Attention ===
Il y a un bug récurent dans les fichiers po : lorsque la phrase traduite commence par "$", rien ne s'affiche

dans le jeu. Pour corriger le problème, il suffit de mettre un simple espace devant le signe (seulement quand la phrase commence par $)

== Aujourd'hui, qui fait quoi ? ==
Ce chapitre vous permet de savoir qui fait quoi...

Date de dernière mise à jour : 14/01/2008
* Traductions
** wesnoth (.po principal) : Noyga
** wesnoth-multiplayer (Multijoueur) : Noyga
** wesnoth-httt (Heir To The Throne / L'Héritier du trône) : La_vie_en_Wose
** wesnoth-thot (The Hammer of Thursagan) : Dylann/gotrek860
* Relectures / À relire
** wesnoth-lib (Librairie commune) : Noyga

FrenchTranslation

2008-02-03T18:17:49Z

Noyga: /* Aujourd'hui, qui fait quoi ? */

Battle for Wesnoth - Traduction française
== Le mot d'introduction ==

Cette page sert à mieux coordonner l'effort de tous et à donner les informations souvent demandées avant de se lancer dans la traduction française.

== Règles de traduction ==
=== Respect des termes de l'univers de Wesnoth ===
Pour améliorer la cohérence de l'ensemble des traductions, plusieurs Wikis servent de dictionnaires pour décrire l'univers de Wesnoth :
# unités : [[FrenchUnits]] ;
# noms communs : [[NomsCommuns]] ;
# noms propres : [[NomsPropres]].

=== Respect du contexte ===
Il est important de correctement traduire les différents textes. Il ne suffit pas de traduire mot à mot les différentes phrases, il faut aussi faire très attention au contexte.

=== Respect des règles de typographie ===

==== Titres ====
Les titres des campagnes, des scénarios et des chapitres doivent suivre les règles de la langue française. Ces règles se trouvent sur http://fr.wikipedia.org/wiki/Wikip%C3%A9dia:Conventions_typographiques.

==== Ponctuation ====
Les traductions doivent aussi suivre les règles de ponctuation de la langue française, essentielles à un bon affichage du texte ; par exemple, l'utilisation d'une espace fine avant le signe « : » évitera que ce signe ne se trouve en début de ligne d'un texte. Ces règles se trouvent sur http://www.reveenjoie-poesie.com/outils-linguistiques/Typographie_francaise.html.

Il est préférable de ne pas mettre de virgule ni avant le « et », ni avant le « ou » (contrairement à l'anglais).

Remarque : sous Windows, la combinaison Alt+(0160) permet d'écrire une espace fine (les parenthèses indiquent qu'il faut maintenir la touche Alt appuyée).
Voici d'autres raccourcis : http://www.crdp-montpellier.fr/cd48/tice/trucs/majuscules.htm#win

==== Majuscules ====
Les majuscules doivent être accentuées dans les textes traduits : À, Â, Æ, Ç, É, Ê, È, Î, Ô, Œ, Ù, Û...

Voici également quelques rappels sur des confusions fréquentes :
# pas de majuscules aux noms des races (« nains », « elfes », « orcs », etc.) ;
# majuscules aux noms de clans ou de factions (les humains de « l'Ordre de la Serre Pourpre ») ;
# majuscules aux points cardinaux quand on parle d'une partie d'un tout (« les forêts de l'Ouest » peuvent se trouver à l'est), et minuscule quand on parle de la direction (« aller vers le nord »).

=== Respect des règles de l'orthographe ===
Il est préférable de soigner son orthographe : le CNRS et l'ATILF fournissent un dictionnaire en ligne performant et complet : http://atilf.atilf.fr/

Les rectifications d'orthographes préconisées par l'Académie Française peuvent s'appliquer (http://www.academie-francaise.fr/langue/orthographe/regles.html).

== Principes de traduction pour Wesnoth ==
Le principe est de mettre à jour les fichiers .po, fichiers servant à gérer les traductions dans Wesnoth. Les échanges se font via la mailing list.

=== S'inscrire à la mailing list ===
La mailing list francophone de Wesnoth est l'outil privilégié pour
# d'abord avertir les traducteurs que vous allez commencer une traduction (et éviter de travailler sur le même fichier),
# envoyer ses traductions pour validation ou relecture,
# poser des questions.

Pour s'inscrire à la mailing list, envoyez un mail vide ayant comme sujet « subscribe » (il sera traité par un robot) ; ou cliquez directement ici mailto:wesnoth-request@ml.free.fr?subject=subscribe et envoyez...

Les responsables des différentes mailing list sont ici : [[WesnothTranslations]].

Les archives de la mailing list sont ici : http://news.gmane.org/gmane.games.wesnoth-fr ; vous pouvez vous abonner au serveur de news news.gmane.org (gmane.games.wesnoth-fr).

Il est également possible de discuter sur le canal IRC #wesnothfr (sur irc.freenode.net) ou sur le forum, mais l'équipe de traduction française ne s'y promène que rarement.

=== Récupérer les fichiers .po nécessaires ===
Les fichiers à traduire sont accessibles :
# soit par cette page : http://gettext.wesnoth.org/ (le plus simple),
# soit par le CVS : http://savannah.nongnu.org/cvs/?group=wesnoth (si on aime CVS).

=== Modifier les fichiers .po et vérifier le statut des lignes traduites ===
Plusieurs logiciels permettent de modifier ces fichiers :
# les éditeurs de texte
#* notepad++ (http://notepad-plus.sourceforge.net/fr/site.htm) ;
#* textpad (http://www.textpad.com/);
#* ou, pour Mac, Textwrangler (http://www.barebones.com/products/textwrangler/index.shtml) ;
#* et puis bien d'autres encore...
# ou des éditeurs spécifiques aux fichiers .po
#* poEdit, pour Mac et PC (http://www.poedit.net/) ;
#* KBabel (http://i18n.kde.org/tools/kbabel/) ;
#* gtranslator (http://gtranslator.sourceforge.net/).

Chaque champ de traduction possède un statut :
# si vous traduisez pour la première fois un champ, mettez-le en traduction approximative ("fuzzy" en anglais), et ce même si c'est une traduction très basique ; toute traduction doit être relue au moins une fois avant d'être approuvée ;
# si vous relisez un champ, libre à vous de décider de son statut après votre relecture ;
#* sortez-le de son état approximatif si vous le considérez incontestablement bien traduit ;
#* laissez-le à l'état approximatif et demandez une deuxième relecture si vous n'êtes pas sûr de la traduction.

=== Tester sa traduction ===
Si vous le désirez, vous pouvez immédiatement tester votre traduction :
# enlevez l'option fuzzy de la ligne (ou des lignes) que vous voulez vérifier ;
# générez un fichier compilé « .mo » à partir du fichier texte « .po » ;
#*En ligne de commande : la commande « msgfmt » peut être utilisée avec le nom du fichier « .po » (exemple : « msgfmt mon_fichier.po -o mon_fichier.mo » générera « mon_fichier.mo »).
#*Avec l'éditeur « poedit » : « Fichier -> Préférence », onglet « Editeur, cochez la case « Compiler automatiquement les fichiers .mo lors de la sauvegarde » ; sauvez le fichier.
# copiez votre fichier dans le répertoire contenant les traductions et renommez-le ;
#*Sous Windows, <Répertoire d'installation de Wesnoth>\fr\LC_MESSAGES\<Nom du fichier à tester> (Exemple : C:\Wesnoth\po\fr\LC_MESSAGES\wesnoth-utbs.mo) ;
#*Sous Linux, répertoire en fonction de la distribution (Exemple Mandriva : /usr/share/locale/fr/LC_MESSAGES).
# jouez.... jusqu'au moment où le texte traduit est censé apparaître ; il n'est pas nécessaire de tout reprendre depuis le début, une sauvegarde fonctionne. Un texte traduit sans erreur apparaît... traduit.

Remarque : pour accélérer les tests, vous pouvez utiliser le mode debug de Wesnoth :
#Pour passer en mode débug :
#*taper : (pour ouvrir le mode de commande), puis : debug<entrée>
#*ou taper "wesnoth.exe --debug",
#*ou taper "wesnoth.exe -d"
# pour utiliser le mode débug :
#*":debug" entre en mode debug
#*":n" termine le scénario immédiatement

=== Envoyer sa traduction ===
Une traduction terminée est compressée, puis envoyée à la ML.

Il est préférable, en cas de relecture, de signaler les modifications dans le corps du mail, par exemple en faisant comme ci-dessous :
#Exemple 1 (refonte d'une phrase) : N° ligne Anciene version => Nouvelle version.
#Exemple 2 (correction d'une faute, indiquée par des *) : N°Ligne Ancien*n*e version

Il est également possible de générer un fichier différentiel entre l'ancienne et la nouvelle version ; mais l'expérience semble montrer que cela est peu relu.
Cette techique est surtout à utiliser qu'en cas de modifications massives (cas où le suivi ligne à ligne serait complexe et lourd).

=== Attention ===
Il y a un bug récurent dans les fichiers po : lorsque la phrase traduite commence par "$", rien ne s'affiche

dans le jeu. Pour corriger le problème, il suffit de mettre un simple espace devant le signe (seulement quand la phrase commence par $)

== Aujourd'hui, qui fait quoi ? ==
Ce chapitre vous permet de savoir qui fait quoi...

Date de dernière mise à jour : 14/01/2008
* Traductions
** wesnoth (.po principal) : Noyga
** wesnoth-multiplayer (Multijoueur) : Noyga
** wesnoth-httt (Heir To The Throne / L'Héritier du trône) : La_vie_en_Wose
** wesnoth-thot (The hammer of Thursagan) : Dylann/gotrek860
* Relectures / À relire
** wesnoth-lib (Librairie commune) : Noyga