I18n: Unterschied zwischen den Versionen

Aus OrgaMon Wiki
Zur Navigation springen Zur Suche springen
Keine Bearbeitungszusammenfassung
KKeine Bearbeitungszusammenfassung
 
(2 dazwischenliegende Versionen von 2 Benutzern werden nicht angezeigt)
Zeile 1: Zeile 1:
OrgaMon is a native German Product. Even if the GUI can be translated without recompile OrgaMon, internal Datastructures will belong German. First lets give a overview how you can prepare OrgaMon for your localization.  
<b><u>Internationalization</u></b>
 
OrgaMon is a native German Product. Even if the GUI can be translated without recompile OrgaMon, internal Datastructures will belong German. First let's give a survey how you can prepare OrgaMon for your localization.  


== System - Settings ==
== System - Settings ==
Zeile 19: Zeile 21:




Now, Lets start introduce how OrgaMon do this.<br>
Now, lets start introduce how OrgaMon is doing this.<br>
<br>
<br>


Zeile 55: Zeile 57:
http://dybdahl.dk/dxgettext/
http://dybdahl.dk/dxgettext/


OrgaMon can not read .po Files. They must be converted to .mo Files. The downloades Tools will enable you to do this conversation for you. The "ggfmt" will generate a .mo file from a given .po - File. After any change of the .po File you must generate the .mo file. OrgaMon must be restartet so that changed content of the .mo is recognized.
OrgaMon can not read .po Files. They must be converted to .mo Files. The downloaded Tools will enable you to do this conversation for you. The "ggfmt" will generate a .mo file from a given .po - File. After any changing of the .po File is done, you can generate the .mo file. OrgaMon must be restartet so that changed content of the .mo is recognized.


== Developement Cycle ==
== Developement Cycle ==

Aktuelle Version vom 18. September 2007, 11:19 Uhr

Internationalization

OrgaMon is a native German Product. Even if the GUI can be translated without recompile OrgaMon, internal Datastructures will belong German. First let's give a survey how you can prepare OrgaMon for your localization.

System - Settings

## Landesspezifische Einstellungen mit den entsprechenden Default-Werten
## sobald kein Wert angegeben ist. Hier muss man also definitiv eine 
## Angabe machen, um die deutschen Defaults zu umgehen.


OrtFormat=%l-%p %o %s 

BearbeiterSprache=DE

TimeServer=ptbtime1.ptb.de,ptbtime2.ptb.de

Auftragsmedium=Telefon,Fax,Persönlich,Brief,Webshop

Auftragsmotivation=Musikmesse 2003,Katalog A,Katalog B,ohne


Now, lets start introduce how OrgaMon is doing this.

Preparation

get default.po

Ask the developer for the default.po. Place the File

 default.po 

to

 <OrgaMon.exe-Path>\locale\en\LC_MESSAGES\default.po 

or any other localization you want to build (Replace the "en" by the locale-Alias of your choice).

'Tip: Check yours computer locale by starting Orgamon an read the text on lower border after the @'
'Tip: Switch OrgaMons locale setting by typing in the Commandline:'

 cd \<Your-OrgaMon.exe-Path>
 set lang=en
 OrgaMon

Install a special Texteditor

All your Translation work is saved in a single File (a .po File). You can edit this with a simple Text Editor, but there is a better way: Downlaod and install the famous po-Editor:

http://www.poedit.org/

Install a Compiler

http://dybdahl.dk/dxgettext/

OrgaMon can not read .po Files. They must be converted to .mo Files. The downloaded Tools will enable you to do this conversation for you. The "ggfmt" will generate a .mo file from a given .po - File. After any changing of the .po File is done, you can generate the .mo file. OrgaMon must be restartet so that changed content of the .mo is recognized.

Developement Cycle

  • Edit your .po File
  • save it
  • change to the explorer
  • right click on the .po File, choose "Open with" -> "ggfmt"
  • restart OrgaMon