blob: 0229dccb13534b18536b02991522d4d30ceb9270 (
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
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
|
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<title></title>
<link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
<link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
<link rel="stylesheet" media="print" type="text/css" href="./print.css" />
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
</head>
<body>
<a href=.>start</a></br>
<h1><a name="general_usage" id="general_usage">General Usage</a></h1>
<div class="level1">
<p>
The tools follow a general usage convention which is helpful to understand.
</p>
</div>
<!-- SECTION "General Usage" [1-106] -->
<h2><a name="input_output" id="input_output">Input & Output</a></h2>
<div class="level2">
<p>
The last two arguments of your command are the input and output directories:
</p>
<pre class="code">moz2po <input> <output></pre>
<p>
You can of course still us the -i and -o options which allows you to reorder commands
</p>
<pre class="code">moz2po -o <output> -i <input></pre>
</div>
<!-- SECTION "Input & Output" [107-359] -->
<h2><a name="error_reporting" id="error_reporting">Error Reporting</a></h2>
<div class="level2">
<p>
All tools accept the option --errorlevel. If you find a bug add this option and send the traceback to the developers.
</p>
<pre class="code">moz2po <other-options> --errorlevel=traceback</pre>
</div>
<!-- SECTION "Error Reporting" [360-558] -->
<h2><a name="templates" id="templates">Templates</a></h2>
<div class="level2">
<p>
If you are working with any file format and you wish to preserve comments and layout then use your source file
as a template.
</p>
<pre class="code">po2dtd -t <source-file> <input> <output></pre>
<p>
This will use the files in <source-file> as a template merge the <acronym title="Gettext Portable Object">PO</acronym> files in <input> and create new <acronym title="Document Type Definition">DTD</acronym> files in <output>
</p>
<p>
If you ran this without the templates you would get valid <acronym title="Document Type Definition">DTD</acronym> files but they would not preserve the layout or all the comments from the source <acronym title="Document Type Definition">DTD</acronym> file
</p>
<p>
The same concept of templates is also used when you merge files.
</p>
<pre class="code">pomerge -t <old> <fixes> <new></pre>
<p>
This would take the <old> files merge in the <fix>'s and output new <acronym title="Gettext Portable Object">PO</acronym> files, preserving formatting, into <new>. You can use the same directory for <old> and <new> if you want the merges to overwrite files in <old>
</p>
</div>
<!-- SECTION "Templates" [559-1345] -->
<h2><a name="source2target" id="source2target">source2target</a></h2>
<div class="level2">
<p>
The converters all follow this convention:
</p>
<ul>
<li class="level1"><div class="li"> source = the format from which you are converting e.g. in oo2po we are converting from OpenOffice.org SDF/GSI</div>
</li>
<li class="level1"><div class="li"> target = the format into which you are converting e.g. in oo2po we are converting to Gettext <acronym title="Gettext Portable Object">PO</acronym></div>
</li>
</ul>
</div>
<!-- SECTION "source2target" [1346-1631] -->
<h2><a name="getting_help" id="getting_help">Getting Help</a></h2>
<div class="level2">
<p>
The --help option will always list the available commands for the tool.
</p>
<pre class="code">moz2po --help</pre>
</div>
<!-- SECTION "Getting Help" [1632-] --></body>
</html>
|
