1 |
Hmm, never thought of doing translations. |
2 |
Is there a lot of stuff left to do in English to French translations? Or |
3 |
just some article here and there? |
4 |
|
5 |
Damien |
6 |
|
7 |
On 02/28/13 23:47, José Fournier wrote: |
8 |
> Hi, |
9 |
> |
10 |
> I think I have found a solution to my problem. In fact copying the |
11 |
> original file from EN to FR folder and then translating works. The |
12 |
> only trouble I had was that the link to the file (chapter) was not yet |
13 |
> present in the master document /doc/fr/handbook/handbook-amd64.xml. |
14 |
> We have something to learn every day . |
15 |
> |
16 |
> Now everything renders correctly in the browser. |
17 |
> |
18 |
> |
19 |
> On 02/28/13 18:47, José Fournier wrote: |
20 |
>> Hi, |
21 |
>> |
22 |
>> Up to now I have updated the translation of files that were already |
23 |
>> committed both sides (original and translation). Using gorg on a |
24 |
>> checkout of the CVS provides a very easy way to see the English file |
25 |
>> and the translated file side by side in a browser. This way one can |
26 |
>> check the textual aspect of the document as well as its rendering |
27 |
>> (the tags). |
28 |
>> Now I come to a file which original only exists. Copying it into the |
29 |
>> equivalent folder of the target language doesn't suffice to make it |
30 |
>> appear in the browser. The only thing that is rendered is "cannot |
31 |
>> convert nil into string". I guess the file has to be committed first |
32 |
>> to be viewable in the browser. But I have no right to do so at the |
33 |
>> moment. |
34 |
>> My question is how to do this locally in order to have gorg render it |
35 |
>> normally ? |
36 |
>> |
37 |
>> I hope my question is not too stupid and that the answer is not |
38 |
>> obvious in the GDP documentation. |
39 |
>> |
40 |
>> Thanks in advance for help |
41 |
>> |
42 |
>> José |
43 |
>> |
44 |
>> |
45 |
>> |
46 |
>> |
47 |
> |
48 |
> |