summaryrefslogtreecommitdiff
path: root/docs/Howto_compile_lng_files_from_CLI.txt
blob: 6fe70b0df1d21421a9f15c2a1f45f09e26c435a4 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
This is a guide to compile strgen on gcc

All this is done in the makefile, so it's only interesting for people, who wants to alter something themselves (translators)

HOWTO compile lng files:

First you get strgen compiled (look below/download nightly build/run makefile)

strgen takes the argument of a txt file and translates it to a lng file and places that lng file in the same dir as the txt file.

Example 1:
if you are in the root of your working copy (svn code), you should type
strgen/strgen lang/english.txt
to compile englist.lng. It will be placed in the lang dir

Example 2:
you have strgen but not the source and you want to compile a txt file in the same dir. YOu should type
./strgen english.txt
and you will get english.lng in the same dir

You can change english to whatever language you want

Commands used by strgen

-v --version
strgen will tell what svn revision it is based on

-t
strgen will add <TODO> to the missing strings and use the english strings while compiling
this will need english.txt to be present

-w
strgen will print any missing strings to standard error output(stderr)
this will need english.txt to be present

here are a very useful tool for translators:
http://openttd.rulez.org/


HOWTO compile strgen:
(this should be useless as you can just type make)
Goto the main dir
Compile by typing
gcc strgen/strgen.c -o strgen/strgen -DUNIX
or if you want it to tell the revision too
gcc strgen/strgen.c rev.o -o strgen/strgen -DUNIX -DWITH_REV (this is the one the makefile uses)

you now have a program called strgen in the strgen directory