Hi List,
and welcome back to Mr Wanderer. I've read messages about translations, and
i've looked at .po files in cvs. If You want i could try to make italian
files (it seems simple to do, i will only write a string in italian under
that in english! Easy for me too!). I don't know english so well, but i
think to understand all essential (and i have a dictionary). If this can
help Your work tell me somethings, otherwise ...

ciao,
fran.

Yes, that is all you need to do. Just send the finished file to the
list! Unfortunately, I do not think you will be in time for 5.11, as it
is already being released, but it should be OK for 5.12.

On Thu, 2009-09-24 at 06:47 -0700, francibal wrote:
> Hi List,
> and welcome back to Mr Wanderer. I've read messages about translations, and
> i've looked at .po files in cvs. If You want i could try to make italian
> files (it seems simple to do, i will only write a string in italian under
> that in english! Easy for me too!). I don't know english so well, but i
> think to understand all essential (and i have a dictionary). If this can
> help Your work tell me somethings, otherwise ...
> 
> ciao,
> fran.
> 
-- 
Saludos,
Felipe Sateler

> Yes, that is all you need to do. Just send the finished file to the
> list! Unfortunately, I do not think you will be in time for 5.11, as it
> is already being released, but it should be OK for 5.12.
>

Felipe is right.  The translatiosn are just English String followed by
translation

Basically easy until the order of args in printf format sneeds to be
changed, when there is some syntax to do that.  It is also incremental. 
One can do a few until bored.  Either send revided .po files to me, or the
developer list or ask for SF write access by mailing me.

The French and Columbian-Spanish translatiosn are largely under control. 
The  Italian, German and Russian are only what I could do with Babelfish
and a dictionary, and are VERY suspect.

We did have a Japanese translation once, but it got lost in csound4->csound5

By the way, as far as I am concerned 5.11 is not rekleased yet -- Friday
at the earlest.  It is just that SF changes make it harder to create a
release and then make it available.

==John ff




Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

You can control your translation work by running the following command 
on your po file:

msgfmt -c --statistics italian.po

Take care not to change anything in the English strings because they 
have to match exactly the strings in the source files (i.e. if you find 
a typo in an English string, report it to John ffitch  but don't correct 
it yourself).

You have to balance exactly the format specifiers (%d, %f, etc) and the 
carriage return character (\n)

Regards

Francois Pinot

jpff@cs.bath.ac.uk a écrit :
>> Yes, that is all you need to do. Just send the finished file to the
>> list! Unfortunately, I do not think you will be in time for 5.11, as it
>> is already being released, but it should be OK for 5.12.
>>
>>     
>
> Felipe is right.  The translatiosn are just English String followed by
> translation
>
> Basically easy until the order of args in printf format sneeds to be
> changed, when there is some syntax to do that.  It is also incremental. 
> One can do a few until bored.  Either send revided .po files to me, or the
> developer list or ask for SF write access by mailing me.
>
> The French and Columbian-Spanish translatiosn are largely under control. 
> The  Italian, German and Russian are only what I could do with Babelfish
> and a dictionary, and are VERY suspect.
>
> We did have a Japanese translation once, but it got lost in csound4->csound5
>
> By the way, as far as I am concerned 5.11 is not rekleased yet -- Friday
> at the earlest.  It is just that SF changes make it harder to create a
> release and then make it available.
>
> ==John ff
>
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>   



Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Many thanks,
i will try to do this work better as possible (by my ability).
I hope to send a file soon (but i don't saw 187 pages of strings!!!).

Again thanks,

ciao,
fran.


PINOT François wrote:
> 
> You can control your translation work by running the following command 
> on your po file:
> 
> msgfmt -c --statistics italian.po
> 
> Take care not to change anything in the English strings because they 
> have to match exactly the strings in the source files (i.e. if you find 
> a typo in an English string, report it to John ffitch  but don't correct 
> it yourself).
> 
> You have to balance exactly the format specifiers (%d, %f, etc) and the 
> carriage return character (\n)
> 
> Regards
> 
> Francois Pinot
> 
> jpff@cs.bath.ac.uk a écrit :
>>> Yes, that is all you need to do. Just send the finished file to the
>>> list! Unfortunately, I do not think you will be in time for 5.11, as it
>>> is already being released, but it should be OK for 5.12.
>>>
>>>     
>>
>> Felipe is right.  The translatiosn are just English String followed by
>> translation
>>
>> Basically easy until the order of args in printf format sneeds to be
>> changed, when there is some syntax to do that.  It is also incremental. 
>> One can do a few until bored.  Either send revided .po files to me, or
>> the
>> developer list or ask for SF write access by mailing me.
>>
>> The French and Columbian-Spanish translatiosn are largely under control. 
>> The  Italian, German and Russian are only what I could do with Babelfish
>> and a dictionary, and are VERY suspect.
>>
>> We did have a Japanese translation once, but it got lost in
>> csound4->csound5
>>
>> By the way, as far as I am concerned 5.11 is not rekleased yet -- Friday
>> at the earlest.  It is just that SF changes make it harder to create a
>> release and then make it available.
>>
>> ==John ff
>>
>>
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>   
> 
> 
> 
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
> 
> 

-- 
View this message in context: http://www.nabble.com/translation-tp25569867p25602037.html
Sent from the Csound - General mailing list archive at Nabble.com.



Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Hi Mr. All,
apologies for my ignorance...

i'm working on italian translation but i need other advice.
i'm started with open office, and i have translated some strings with right
(i hope)
formatting, but: if source string had (into) an ending return (\n) character
i have copied in the same way. Now i've discover (like Captain Cook!)
specific programs like poedit.
I can not open my file with these last programs, but, moreover, here source
strings do not have \n visible (strings with \n into), and i don't know if i
can make the same things in translation and the program then automatically
make this work (to me seems wrong).

Can You use an open office file? Or it is a wrong format that requier more
work to You later?

Again apologies (i know You are now working to next release),

thanks and ciao,
fran.


francibal wrote:
> 
> Hi List,
> and welcome back to Mr Wanderer. I've read messages about translations,
> and i've looked at .po files in cvs. If You want i could try to make
> italian files (it seems simple to do, i will only write a string in
> italian under that in english! Easy for me too!). I don't know english so
> well, but i think to understand all essential (and i have a dictionary).
> If this can help Your work tell me somethings, otherwise ...
> 
> ciao,
> fran.
> 
> 

I use a pure text editor like jEdit, which doesn't add extra information 
on text formatting as does OpenOffice. Poedit is a good choice too. I 
prefer to use jEdit because it has syntax highlighting.

Unfortunately you'll have do start again from the original file because 
your OpenOffice file has probably extra word processing information 
inadequate here.

Moreover, you have to respect the encoding which is UTF-8 in that case. 
Normally jEdit and poedit take care of this.

Regards

Francois Pinot

francibal a écrit :
> Hi Mr. All,
> apologies for my ignorance...
>
> i'm working on italian translation but i need other advice.
> i'm started with open office, and i have translated some strings with right
> (i hope)
> formatting, but: if source string had (into) an ending return (\n) character
> i have copied in the same way. Now i've discover (like Captain Cook!)
> specific programs like poedit.
> I can not open my file with these last programs, but, moreover, here source
> strings do not have \n visible (strings with \n into), and i don't know if i
> can make the same things in translation and the program then automatically
> make this work (to me seems wrong).
>
> Can You use an open office file? Or it is a wrong format that requier more
> work to You later?
>
> Again apologies (i know You are now working to next release),
>
> thanks and ciao,
> fran.
>
>
> francibal wrote:
>   
>> Hi List,
>> and welcome back to Mr Wanderer. I've read messages about translations,
>> and i've looked at .po files in cvs. If You want i could try to make
>> italian files (it seems simple to do, i will only write a string in
>> italian under that in english! Easy for me too!). I don't know english so
>> well, but i think to understand all essential (and i have a dictionary).
>> If this can help Your work tell me somethings, otherwise ...
>>
>> ciao,
>> fran.
>>
>>
>>     
>
>   



Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Thanks Mr. Francois,

if You have a little bit time could You try if allegated file is usable
or not ?
Maybe i can save some work ...

Thanks again,

ciao,
fran

http://www.nabble.com/file/p25625040/italian_01.po italian_01.po 

PINOT Francois wrote:
> 
> I use a pure text editor like jEdit, which doesn't add extra information 
> on text formatting as does OpenOffice. Poedit is a good choice too. I 
> prefer to use jEdit because it has syntax highlighting.
> 
> Unfortunately you'll have do start again from the original file because 
> your OpenOffice file has probably extra word processing information 
> inadequate here.
> 
> Moreover, you have to respect the encoding which is UTF-8 in that case. 
> Normally jEdit and poedit take care of this.
> 
> Regards
> 
> Francois Pinot
> 
> francibal a écrit :
>> Hi Mr. All,
>> apologies for my ignorance...
>>
>> i'm working on italian translation but i need other advice.
>> i'm started with open office, and i have translated some strings with
>> right
>> (i hope)
>> formatting, but: if source string had (into) an ending return (\n)
>> character
>> i have copied in the same way. Now i've discover (like Captain Cook!)
>> specific programs like poedit.
>> I can not open my file with these last programs, but, moreover, here
>> source
>> strings do not have \n visible (strings with \n into), and i don't know
>> if i
>> can make the same things in translation and the program then
>> automatically
>> make this work (to me seems wrong).
>>
>> Can You use an open office file? Or it is a wrong format that requier
>> more
>> work to You later?
>>
>> Again apologies (i know You are now working to next release),
>>
>> thanks and ciao,
>> fran.
>>
>>
>> francibal wrote:
>>   
>>> Hi List,
>>> and welcome back to Mr Wanderer. I've read messages about translations,
>>> and i've looked at .po files in cvs. If You want i could try to make
>>> italian files (it seems simple to do, i will only write a string in
>>> italian under that in english! Easy for me too!). I don't know english
>>> so
>>> well, but i think to understand all essential (and i have a dictionary).
>>> If this can help Your work tell me somethings, otherwise ...
>>>
>>> ciao,
>>> fran.
>>>
>>>
>>>     
>>
>>   
> 
> 
> 
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
> 
> 

-- 
View this message in context: http://www.nabble.com/translation-tp25569867p25625040.html
Sent from the Csound - General mailing list archive at Nabble.com.



Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

I modified the encoding to utf-8 (was iso-8859-1) and added a '\n' 
character that was missing on line 171. Seems OK now.

Regards

Francois Pinot

francibal a écrit :
> Thanks Mr. Francois,
>
> if You have a little bit time could You try if allegated file is usable
> or not ?
> Maybe i can save some work ...
>
> Thanks again,
>
> ciao,
> fran
>
> http://www.nabble.com/file/p25625040/italian_01.po italian_01.po 
>
> PINOT Francois wrote:
>   
>> I use a pure text editor like jEdit, which doesn't add extra information 
>> on text formatting as does OpenOffice. Poedit is a good choice too. I 
>> prefer to use jEdit because it has syntax highlighting.
>>
>> Unfortunately you'll have do start again from the original file because 
>> your OpenOffice file has probably extra word processing information 
>> inadequate here.
>>
>> Moreover, you have to respect the encoding which is UTF-8 in that case. 
>> Normally jEdit and poedit take care of this.
>>
>> Regards
>>
>> Francois Pinot
>>
>> francibal a écrit :
>>     
>>> Hi Mr. All,
>>> apologies for my ignorance...
>>>
>>> i'm working on italian translation but i need other advice.
>>> i'm started with open office, and i have translated some strings with
>>> right
>>> (i hope)
>>> formatting, but: if source string had (into) an ending return (\n)
>>> character
>>> i have copied in the same way. Now i've discover (like Captain Cook!)
>>> specific programs like poedit.
>>> I can not open my file with these last programs, but, moreover, here
>>> source
>>> strings do not have \n visible (strings with \n into), and i don't know
>>> if i
>>> can make the same things in translation and the program then
>>> automatically
>>> make this work (to me seems wrong).
>>>
>>> Can You use an open office file? Or it is a wrong format that requier
>>> more
>>> work to You later?
>>>
>>> Again apologies (i know You are now working to next release),
>>>
>>> thanks and ciao,
>>> fran.
>>>
>>>
>>> francibal wrote:
>>>   
>>>       
>>>> Hi List,
>>>> and welcome back to Mr Wanderer. I've read messages about translations,
>>>> and i've looked at .po files in cvs. If You want i could try to make
>>>> italian files (it seems simple to do, i will only write a string in
>>>> italian under that in english! Easy for me too!). I don't know english
>>>> so
>>>> well, but i think to understand all essential (and i have a dictionary).
>>>> If this can help Your work tell me somethings, otherwise ...
>>>>
>>>> ciao,
>>>> fran.
>>>>
>>>>
>>>>     
>>>>         
>>>   
>>>       
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>>
>>     
>
>   


Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

THANKS!

now i will try to use right way, now!

thanks,
ciao,
fran.


PINOT Francois wrote:
> 
> I modified the encoding to utf-8 (was iso-8859-1) and added a '\n' 
> character that was missing on line 171. Seems OK now.
> 
> Regards
> 
> Francois Pinot
> 
> francibal a écrit :
>> Thanks Mr. Francois,
>>
>> if You have a little bit time could You try if allegated file is usable
>> or not ?
>> Maybe i can save some work ...
>>
>> Thanks again,
>>
>> ciao,
>> fran
>>
>> http://www.nabble.com/file/p25625040/italian_01.po italian_01.po 
>>
>> PINOT Francois wrote:
>>   
>>> I use a pure text editor like jEdit, which doesn't add extra information 
>>> on text formatting as does OpenOffice. Poedit is a good choice too. I 
>>> prefer to use jEdit because it has syntax highlighting.
>>>
>>> Unfortunately you'll have do start again from the original file because 
>>> your OpenOffice file has probably extra word processing information 
>>> inadequate here.
>>>
>>> Moreover, you have to respect the encoding which is UTF-8 in that case. 
>>> Normally jEdit and poedit take care of this.
>>>
>>> Regards
>>>
>>> Francois Pinot
>>>
>>> francibal a écrit :
>>>     
>>>> Hi Mr. All,
>>>> apologies for my ignorance...
>>>>
>>>> i'm working on italian translation but i need other advice.
>>>> i'm started with open office, and i have translated some strings with
>>>> right
>>>> (i hope)
>>>> formatting, but: if source string had (into) an ending return (\n)
>>>> character
>>>> i have copied in the same way. Now i've discover (like Captain Cook!)
>>>> specific programs like poedit.
>>>> I can not open my file with these last programs, but, moreover, here
>>>> source
>>>> strings do not have \n visible (strings with \n into), and i don't know
>>>> if i
>>>> can make the same things in translation and the program then
>>>> automatically
>>>> make this work (to me seems wrong).
>>>>
>>>> Can You use an open office file? Or it is a wrong format that requier
>>>> more
>>>> work to You later?
>>>>
>>>> Again apologies (i know You are now working to next release),
>>>>
>>>> thanks and ciao,
>>>> fran.
>>>>
>>>>
>>>> francibal wrote:
>>>>   
>>>>       
>>>>> Hi List,
>>>>> and welcome back to Mr Wanderer. I've read messages about
>>>>> translations,
>>>>> and i've looked at .po files in cvs. If You want i could try to make
>>>>> italian files (it seems simple to do, i will only write a string in
>>>>> italian under that in english! Easy for me too!). I don't know english
>>>>> so
>>>>> well, but i think to understand all essential (and i have a
>>>>> dictionary).
>>>>> If this can help Your work tell me somethings, otherwise ...
>>>>>
>>>>> ciao,
>>>>> fran.
>>>>>
>>>>>
>>>>>     
>>>>>         
>>>>   
>>>>       
>>>
>>> Send bugs reports to this list.
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>> csound"
>>>
>>>
>>>     
>>
>>   
> 
> 
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
> # Csound Audio Synthesis System
> # Copyright (C) 2007 John ffitch and Csound community
> # This file is distributed under the same license as the Csound package.
> # John ffitch , 2007.
> #
> msgid ""
> msgstr ""
> "Project-Id-Version: CSOUND 5.xx\n"
> "Report-Msgid-Bugs-To: \n"
> "POT-Creation-Date: 2008-07-26 19:39+0100\n"
> "PO-Revision-Date: 2008-09-07 15:25+0100\n"
> "Last-Translator:\n"
> "Language-Team: Italian\n"
> "MIME-Version: 1.0\n"
> "Content-Type: text/plain; charset=UTF-8\n"
> "Content-Transfer-Encoding: 8bit\n"
> 
> #: Engine/auxfd.c:97
> #, c-format
> msgid "fdclose: no record of fd %p"
> msgstr "fdclose: non c'è registrazione di fd %p"
> 
> #: Engine/auxfd.c:144
> #, c-format
> msgid "auxlist for instr %d (%p):\n"
> msgstr "auxlist per strumento %d (%p):\n"
> 
> #: Engine/auxfd.c:148
> #, c-format
> msgid "\tauxch at %p: size %ld, auxp %p, endp %p\n"
> msgstr "\tauxch a %p: dimensione %ld, auxp %p, endp %p\n"
> 
> #: Engine/auxfd.c:158
> #, c-format
> msgid "fdlist for instr %d (%p):"
> msgstr "fdlist per strumento %d (%p):"
> 
> #: Engine/auxfd.c:161
> #, c-format
> msgid "  fd %p in %p"
> msgstr "  fd %p in %p"
> 
> #: Engine/cfgvar.c:57
> msgid "(no error)"
> msgstr "(nessun errore)"
> 
> #: Engine/cfgvar.c:58
> msgid "invalid variable name"
> msgstr "nome di variabile non valido"
> 
> #: Engine/cfgvar.c:59
> msgid "invalid variable type"
> msgstr "tipo di variabile non valido"
> 
> #: Engine/cfgvar.c:60
> msgid "invalid flags specified"
> msgstr "opzione (flag) non valida"
> 
> #: Engine/cfgvar.c:61
> msgid "NULL pointer argument"
> msgstr "argomento del puntatore NULL"
> 
> #: Engine/cfgvar.c:62
> msgid "the specified value is too high"
> msgstr "il valore specificato è troppo alto"
> 
> #: Engine/cfgvar.c:63
> msgid "the specified value is too low"
> msgstr "il valore specificato è troppo basso"
> 
> #: Engine/cfgvar.c:64
> msgid "the specified value is not an integer power of two"
> msgstr "il valore specificato non è un intero potenza di due"
> 
> #: Engine/cfgvar.c:65
> msgid "invalid boolean value; must be 0 or 1"
> msgstr "valore booleano non valido; deve essere 0 oppure 1"
> 
> #: Engine/cfgvar.c:66 Opcodes/osc-sock.c:272
> msgid "memory allocation failed"
> msgstr "allocazione di memoria fallita"
> 
> #: Engine/cfgvar.c:67
> msgid "string exceeds maximum allowed length"
> msgstr "la lunghezza della stringa supera il valore permesso"
> 
> #: Engine/cfgvar.c:68
> msgid "(unknown error)"
> msgstr "(errore sconosciuto)"
> 
> #: Engine/csound_orc_compile.c:459
> #, c-format
> msgid "create_opcode: No rule to handle statemnent of type %d\n"
> msgstr "create_opcode: Non c'è regola per una dichiarazione di tipo %d\n"
> 
> #: Engine/csound_orc_compile.c:645
> #, c-format
> msgid "create_instrument: instr num %ld\n"
> msgstr "create_instrument: strumento num %ld\n"
> 
> #: Engine/csound_orc_compile.c:654
> #, c-format
> msgid "create_instrument: instr name %s\n"
> msgstr "create_instrument: nome dello strumento %s\n"
> 
> #: Engine/csound_orc_compile.c:661 Engine/otran.c:340
> msgid "invalid name for instrument"
> msgstr "nome dello strumento non valido"
> 
> #: Engine/csound_orc_compile.c:665 Engine/otran.c:345
> #, c-format
> msgid "instr %s redefined"
> msgstr "ridefinito lo strumento %s"
> 
> #: Engine/csound_orc_compile.c:806 Engine/otran.c:142 Engine/symbtab.c:393
> #, c-format
> msgid "invalid input type for opcode %s"
> msgstr "tipo di input non valido per l'opcode %s"
> 
> #: Engine/csound_orc_compile.c:811 Engine/otran.c:147 Engine/symbtab.c:398
> #, c-format
> msgid "too many input args for opcode %s"
> msgstr "troppi argomenti in input per l'opcode %s"
> 
> #: Engine/csound_orc_compile.c:826 Engine/otran.c:162 Engine/symbtab.c:413
> #, c-format
> msgid "too many output args for opcode %s"
> msgstr "troppi argomenti in output per l'opcode %s"
> 
> #: Engine/csound_orc_compile.c:842 Engine/otran.c:181 Engine/symbtab.c:432
> #, c-format
> msgid "invalid output type for opcode %s"
> msgstr "tipo di output non valido per l'opcode %s"
> 
> #: Engine/csound_orc_compile.c:927 Engine/otran.c:328
> #, c-format
> msgid "instr %ld redefined"
> msgstr "strumento %ld ridefinito"
> 
> #: Engine/csound_orc_compile.c:937
> msgid "!!! csound->opcodeInfo is NULL !!!\n"
> msgstr "!!! csound->opcodeInfo è NULL !!!\n"
> 
> #: Engine/csound_orc_compile.c:1076
> #, c-format
> msgid "Unknown TREE node of type %d found in root.\n"
> msgstr "Nodo sconosciuto di tipo %d trovato in root.\n"
> 
> #: Engine/csound_orc_compile.c:1132 Engine/otran.c:552 Engine/otran.c:1396
> #, c-format
> msgid "%s invalid sample rate"
> msgstr "%s frequenza di campionamento (sr) non valida"
> 
> #: Engine/csound_orc_compile.c:1134 Engine/otran.c:554 Engine/otran.c:1398
> #, c-format
> msgid "%s invalid control rate"
> msgstr "%s frequenza dei segnali di controllo (kr) non valida"
> 
> #: Engine/csound_orc_compile.c:1137 Engine/otran.c:557 Engine/otran.c:1394
> #, c-format
> msgid "%s invalid ksmps value"
> msgstr "%s valore di ksmps non valido"
> 
> #: Engine/csound_orc_compile.c:1139 Engine/otran.c:559 Engine/otran.c:1400
> #, c-format
> msgid "%s inconsistent sr, kr, ksmps"
> msgstr "%s incoerenti sr, kr, ksmps"
> 
> #: Engine/csound_orc_compile.c:1151
> msgid "perf-pass statements illegal in header blk\n"
> msgstr "Le dichiarazioni di esecuzione sono vietate nel blocco
> intestazione (header)\n"
> 
> #: Engine/csound_orc_compile.c:1155
> #, c-format
> msgid "%d syntax errors in orchestra.  compilation invalid\n"
> msgstr "%d errore\\i di sintassi nell'orchestra.  Compilazione non
> valida\n"
> 
> #: Engine/csound_orc_compile.c:1215 Engine/otran.c:643
> msgid "inconsistent argoff sumcount"
> msgstr "argoff sumcount incoerente"
> 
> #: Engine/csound_orc_compile.c:1287 Engine/otran.c:712
> #, c-format
> msgid "LABELS list is full...extending to %d\n"
> msgstr "La lista etichette è piena...estesa a %d\n"
> 
> #: Engine/csound_orc_compile.c:1325 Engine/otran.c:750
> #, c-format
> msgid "GOTOS list is full..extending to %d\n"
> msgstr "La lista GOTOS è piena...estesa a %d\n"
> 
> #: Engine/csound_orc_compile.c:1358 Engine/otran.c:783
> #, c-format
> msgid "target label '%s' not found"
> msgstr "obiettivo dell'etichetta '%s' non trovato"
> 
> #: Engine/csound_orc_compile.c:1423 Engine/otran.c:838
> #, c-format
> msgid "string syntax '%s'"
> msgstr "sintassi della stringa '%s'"
> 
> #: Engine/csound_orc_compile.c:1473 Engine/otran.c:888
> #, c-format
> msgid "numeric syntax '%s'"
> msgstr "sintassi numerica '%s'"
> 
> 

-- 
View this message in context: http://www.nabble.com/translation-tp25569867p25625213.html
Sent from the Csound - General mailing list archive at Nabble.com.



Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Again me,
i'm working on italian translation and this is my file (it is in progress, i
need to clear myself about some word), BUT i need to know if it is OK.
If someone could take a look and tell me if file is ok (about format and
coding) i will be grateful him/her.

http://www.nabble.com/file/p25742294/italian.po italian.po 

Ciao,
fran.



francibal wrote:
> 
> THANKS!
> 
> now i will try to use right way, now!
> 
> thanks,
> ciao,
> fran.
> 
> 
> PINOT Francois wrote:
>> 
>> I modified the encoding to utf-8 (was iso-8859-1) and added a '\n' 
>> character that was missing on line 171. Seems OK now.
>> 
>> Regards
>> 
>> Francois Pinot
>> 
>> francibal a écrit :
>>> Thanks Mr. Francois,
>>>
>>> if You have a little bit time could You try if allegated file is usable
>>> or not ?
>>> Maybe i can save some work ...
>>>
>>> Thanks again,
>>>
>>> ciao,
>>> fran
>>>
>>> http://www.nabble.com/file/p25625040/italian_01.po italian_01.po 
>>>
>>> PINOT Francois wrote:
>>>   
>>>> I use a pure text editor like jEdit, which doesn't add extra
>>>> information 
>>>> on text formatting as does OpenOffice. Poedit is a good choice too. I 
>>>> prefer to use jEdit because it has syntax highlighting.
>>>>
>>>> Unfortunately you'll have do start again from the original file because 
>>>> your OpenOffice file has probably extra word processing information 
>>>> inadequate here.
>>>>
>>>> Moreover, you have to respect the encoding which is UTF-8 in that case. 
>>>> Normally jEdit and poedit take care of this.
>>>>
>>>> Regards
>>>>
>>>> Francois Pinot
>>>>
>>>> francibal a écrit :
>>>>     
>>>>> Hi Mr. All,
>>>>> apologies for my ignorance...
>>>>>
>>>>> i'm working on italian translation but i need other advice.
>>>>> i'm started with open office, and i have translated some strings with
>>>>> right
>>>>> (i hope)
>>>>> formatting, but: if source string had (into) an ending return (\n)
>>>>> character
>>>>> i have copied in the same way. Now i've discover (like Captain Cook!)
>>>>> specific programs like poedit.
>>>>> I can not open my file with these last programs, but, moreover, here
>>>>> source
>>>>> strings do not have \n visible (strings with \n into), and i don't
>>>>> know
>>>>> if i
>>>>> can make the same things in translation and the program then
>>>>> automatically
>>>>> make this work (to me seems wrong).
>>>>>
>>>>> Can You use an open office file? Or it is a wrong format that requier
>>>>> more
>>>>> work to You later?
>>>>>
>>>>> Again apologies (i know You are now working to next release),
>>>>>
>>>>> thanks and ciao,
>>>>> fran.
>>>>>
>>>>>
>>>>> francibal wrote:
>>>>>   
>>>>>       
>>>>>> Hi List,
>>>>>> and welcome back to Mr Wanderer. I've read messages about
>>>>>> translations,
>>>>>> and i've looked at .po files in cvs. If You want i could try to make
>>>>>> italian files (it seems simple to do, i will only write a string in
>>>>>> italian under that in english! Easy for me too!). I don't know
>>>>>> english
>>>>>> so
>>>>>> well, but i think to understand all essential (and i have a
>>>>>> dictionary).
>>>>>> If this can help Your work tell me somethings, otherwise ...
>>>>>>
>>>>>> ciao,
>>>>>> fran.
>>>>>>
>>>>>>
>>>>>>     
>>>>>>         
>>>>>   
>>>>>       
>>>>
>>>> Send bugs reports to this list.
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>> "unsubscribe
>>>> csound"
>>>>
>>>>
>>>>     
>>>
>>>   
>> 
>> 
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>> # Csound Audio Synthesis System
>> # Copyright (C) 2007 John ffitch and Csound community
>> # This file is distributed under the same license as the Csound package.
>> # John ffitch , 2007.
>> #
>> msgid ""
>> msgstr ""
>> "Project-Id-Version: CSOUND 5.xx\n"
>> "Report-Msgid-Bugs-To: \n"
>> "POT-Creation-Date: 2008-07-26 19:39+0100\n"
>> "PO-Revision-Date: 2008-09-07 15:25+0100\n"
>> "Last-Translator:\n"
>> "Language-Team: Italian\n"
>> "MIME-Version: 1.0\n"
>> "Content-Type: text/plain; charset=UTF-8\n"
>> "Content-Transfer-Encoding: 8bit\n"
>> 
>> #: Engine/auxfd.c:97
>> #, c-format
>> msgid "fdclose: no record of fd %p"
>> msgstr "fdclose: non c'è registrazione di fd %p"
>> 
>> #: Engine/auxfd.c:144
>> #, c-format
>> msgid "auxlist for instr %d (%p):\n"
>> msgstr "auxlist per strumento %d (%p):\n"
>> 
>> #: Engine/auxfd.c:148
>> #, c-format
>> msgid "\tauxch at %p: size %ld, auxp %p, endp %p\n"
>> msgstr "\tauxch a %p: dimensione %ld, auxp %p, endp %p\n"
>> 
>> #: Engine/auxfd.c:158
>> #, c-format
>> msgid "fdlist for instr %d (%p):"
>> msgstr "fdlist per strumento %d (%p):"
>> 
>> #: Engine/auxfd.c:161
>> #, c-format
>> msgid "  fd %p in %p"
>> msgstr "  fd %p in %p"
>> 
>> #: Engine/cfgvar.c:57
>> msgid "(no error)"
>> msgstr "(nessun errore)"
>> 
>> #: Engine/cfgvar.c:58
>> msgid "invalid variable name"
>> msgstr "nome di variabile non valido"
>> 
>> #: Engine/cfgvar.c:59
>> msgid "invalid variable type"
>> msgstr "tipo di variabile non valido"
>> 
>> #: Engine/cfgvar.c:60
>> msgid "invalid flags specified"
>> msgstr "opzione (flag) non valida"
>> 
>> #: Engine/cfgvar.c:61
>> msgid "NULL pointer argument"
>> msgstr "argomento del puntatore NULL"
>> 
>> #: Engine/cfgvar.c:62
>> msgid "the specified value is too high"
>> msgstr "il valore specificato è troppo alto"
>> 
>> #: Engine/cfgvar.c:63
>> msgid "the specified value is too low"
>> msgstr "il valore specificato è troppo basso"
>> 
>> #: Engine/cfgvar.c:64
>> msgid "the specified value is not an integer power of two"
>> msgstr "il valore specificato non è un intero potenza di due"
>> 
>> #: Engine/cfgvar.c:65
>> msgid "invalid boolean value; must be 0 or 1"
>> msgstr "valore booleano non valido; deve essere 0 oppure 1"
>> 
>> #: Engine/cfgvar.c:66 Opcodes/osc-sock.c:272
>> msgid "memory allocation failed"
>> msgstr "allocazione di memoria fallita"
>> 
>> #: Engine/cfgvar.c:67
>> msgid "string exceeds maximum allowed length"
>> msgstr "la lunghezza della stringa supera il valore permesso"
>> 
>> #: Engine/cfgvar.c:68
>> msgid "(unknown error)"
>> msgstr "(errore sconosciuto)"
>> 
>> #: Engine/csound_orc_compile.c:459
>> #, c-format
>> msgid "create_opcode: No rule to handle statemnent of type %d\n"
>> msgstr "create_opcode: Non c'è regola per una dichiarazione di tipo
>> %d\n"
>> 
>> #: Engine/csound_orc_compile.c:645
>> #, c-format
>> msgid "create_instrument: instr num %ld\n"
>> msgstr "create_instrument: strumento num %ld\n"
>> 
>> #: Engine/csound_orc_compile.c:654
>> #, c-format
>> msgid "create_instrument: instr name %s\n"
>> msgstr "create_instrument: nome dello strumento %s\n"
>> 
>> #: Engine/csound_orc_compile.c:661 Engine/otran.c:340
>> msgid "invalid name for instrument"
>> msgstr "nome dello strumento non valido"
>> 
>> #: Engine/csound_orc_compile.c:665 Engine/otran.c:345
>> #, c-format
>> msgid "instr %s redefined"
>> msgstr "ridefinito lo strumento %s"
>> 
>> #: Engine/csound_orc_compile.c:806 Engine/otran.c:142
>> Engine/symbtab.c:393
>> #, c-format
>> msgid "invalid input type for opcode %s"
>> msgstr "tipo di input non valido per l'opcode %s"
>> 
>> #: Engine/csound_orc_compile.c:811 Engine/otran.c:147
>> Engine/symbtab.c:398
>> #, c-format
>> msgid "too many input args for opcode %s"
>> msgstr "troppi argomenti in input per l'opcode %s"
>> 
>> #: Engine/csound_orc_compile.c:826 Engine/otran.c:162
>> Engine/symbtab.c:413
>> #, c-format
>> msgid "too many output args for opcode %s"
>> msgstr "troppi argomenti in output per l'opcode %s"
>> 
>> #: Engine/csound_orc_compile.c:842 Engine/otran.c:181
>> Engine/symbtab.c:432
>> #, c-format
>> msgid "invalid output type for opcode %s"
>> msgstr "tipo di output non valido per l'opcode %s"
>> 
>> #: Engine/csound_orc_compile.c:927 Engine/otran.c:328
>> #, c-format
>> msgid "instr %ld redefined"
>> msgstr "strumento %ld ridefinito"
>> 
>> #: Engine/csound_orc_compile.c:937
>> msgid "!!! csound->opcodeInfo is NULL !!!\n"
>> msgstr "!!! csound->opcodeInfo è NULL !!!\n"
>> 
>> #: Engine/csound_orc_compile.c:1076
>> #, c-format
>> msgid "Unknown TREE node of type %d found in root.\n"
>> msgstr "Nodo sconosciuto di tipo %d trovato in root.\n"
>> 
>> #: Engine/csound_orc_compile.c:1132 Engine/otran.c:552
>> Engine/otran.c:1396
>> #, c-format
>> msgid "%s invalid sample rate"
>> msgstr "%s frequenza di campionamento (sr) non valida"
>> 
>> #: Engine/csound_orc_compile.c:1134 Engine/otran.c:554
>> Engine/otran.c:1398
>> #, c-format
>> msgid "%s invalid control rate"
>> msgstr "%s frequenza dei segnali di controllo (kr) non valida"
>> 
>> #: Engine/csound_orc_compile.c:1137 Engine/otran.c:557
>> Engine/otran.c:1394
>> #, c-format
>> msgid "%s invalid ksmps value"
>> msgstr "%s valore di ksmps non valido"
>> 
>> #: Engine/csound_orc_compile.c:1139 Engine/otran.c:559
>> Engine/otran.c:1400
>> #, c-format
>> msgid "%s inconsistent sr, kr, ksmps"
>> msgstr "%s incoerenti sr, kr, ksmps"
>> 
>> #: Engine/csound_orc_compile.c:1151
>> msgid "perf-pass statements illegal in header blk\n"
>> msgstr "Le dichiarazioni di esecuzione sono vietate nel blocco
>> intestazione (header)\n"
>> 
>> #: Engine/csound_orc_compile.c:1155
>> #, c-format
>> msgid "%d syntax errors in orchestra.  compilation invalid\n"
>> msgstr "%d errore\\i di sintassi nell'orchestra.  Compilazione non
>> valida\n"
>> 
>> #: Engine/csound_orc_compile.c:1215 Engine/otran.c:643
>> msgid "inconsistent argoff sumcount"
>> msgstr "argoff sumcount incoerente"
>> 
>> #: Engine/csound_orc_compile.c:1287 Engine/otran.c:712
>> #, c-format
>> msgid "LABELS list is full...extending to %d\n"
>> msgstr "La lista etichette è piena...estesa a %d\n"
>> 
>> #: Engine/csound_orc_compile.c:1325 Engine/otran.c:750
>> #, c-format
>> msgid "GOTOS list is full..extending to %d\n"
>> msgstr "La lista GOTOS è piena...estesa a %d\n"
>> 
>> #: Engine/csound_orc_compile.c:1358 Engine/otran.c:783
>> #, c-format
>> msgid "target label '%s' not found"
>> msgstr "obiettivo dell'etichetta '%s' non trovato"
>> 
>> #: Engine/csound_orc_compile.c:1423 Engine/otran.c:838
>> #, c-format
>> msgid "string syntax '%s'"
>> msgstr "sintassi della stringa '%s'"
>> 
>> #: Engine/csound_orc_compile.c:1473 Engine/otran.c:888
>> #, c-format
>> msgid "numeric syntax '%s'"
>> msgstr "sintassi numerica '%s'"
>> 
>> 
> 
> 

-- 
View this message in context: http://www.nabble.com/translation-tp25569867p25742294.html
Sent from the Csound - General mailing list archive at Nabble.com.



Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Seems OK except for the end-of-line caracters which are in DOS/Windows 
style (\r\n) instead of unix style (\n). Are you working on a windows 
box? The editor end-of-line style can easily be set in the preferences 
of Poedit or in the Utilities Buffer options of JEdit.

Regards

Francois Pinot

francibal a écrit :
> Again me,
> i'm working on italian translation and this is my file (it is in progress, i
> need to clear myself about some word), BUT i need to know if it is OK.
> If someone could take a look and tell me if file is ok (about format and
> coding) i will be grateful him/her.
>
> http://www.nabble.com/file/p25742294/italian.po italian.po 
>
> Ciao,
> fran.
>
>
>
> francibal wrote:
>   
>> THANKS!
>>
>> now i will try to use right way, now!
>>
>> thanks,
>> ciao,
>> fran.
>>
>>
>> PINOT Francois wrote:
>>     
>>> I modified the encoding to utf-8 (was iso-8859-1) and added a '\n' 
>>> character that was missing on line 171. Seems OK now.
>>>
>>> Regards
>>>
>>> Francois Pinot
>>>
>>> francibal a écrit :
>>>       
>>>> Thanks Mr. Francois,
>>>>
>>>> if You have a little bit time could You try if allegated file is usable
>>>> or not ?
>>>> Maybe i can save some work ...
>>>>
>>>> Thanks again,
>>>>
>>>> ciao,
>>>> fran
>>>>
>>>> http://www.nabble.com/file/p25625040/italian_01.po italian_01.po 
>>>>
>>>> PINOT Francois wrote:
>>>>   
>>>>         
>>>>> I use a pure text editor like jEdit, which doesn't add extra
>>>>> information 
>>>>> on text formatting as does OpenOffice. Poedit is a good choice too. I 
>>>>> prefer to use jEdit because it has syntax highlighting.
>>>>>
>>>>> Unfortunately you'll have do start again from the original file because 
>>>>> your OpenOffice file has probably extra word processing information 
>>>>> inadequate here.
>>>>>
>>>>> Moreover, you have to respect the encoding which is UTF-8 in that case. 
>>>>> Normally jEdit and poedit take care of this.
>>>>>
>>>>> Regards
>>>>>
>>>>> Francois Pinot
>>>>>
>>>>> francibal a écrit :
>>>>>     
>>>>>           
>>>>>> Hi Mr. All,
>>>>>> apologies for my ignorance...
>>>>>>
>>>>>> i'm working on italian translation but i need other advice.
>>>>>> i'm started with open office, and i have translated some strings with
>>>>>> right
>>>>>> (i hope)
>>>>>> formatting, but: if source string had (into) an ending return (\n)
>>>>>> character
>>>>>> i have copied in the same way. Now i've discover (like Captain Cook!)
>>>>>> specific programs like poedit.
>>>>>> I can not open my file with these last programs, but, moreover, here
>>>>>> source
>>>>>> strings do not have \n visible (strings with \n into), and i don't
>>>>>> know
>>>>>> if i
>>>>>> can make the same things in translation and the program then
>>>>>> automatically
>>>>>> make this work (to me seems wrong).
>>>>>>
>>>>>> Can You use an open office file? Or it is a wrong format that requier
>>>>>> more
>>>>>> work to You later?
>>>>>>
>>>>>> Again apologies (i know You are now working to next release),
>>>>>>
>>>>>> thanks and ciao,
>>>>>> fran.
>>>>>>
>>>>>>
>>>>>> francibal wrote:
>>>>>>   
>>>>>>       
>>>>>>             
>>>>>>> Hi List,
>>>>>>> and welcome back to Mr Wanderer. I've read messages about
>>>>>>> translations,
>>>>>>> and i've looked at .po files in cvs. If You want i could try to make
>>>>>>> italian files (it seems simple to do, i will only write a string in
>>>>>>> italian under that in english! Easy for me too!). I don't know
>>>>>>> english
>>>>>>> so
>>>>>>> well, but i think to understand all essential (and i have a
>>>>>>> dictionary).
>>>>>>> If this can help Your work tell me somethings, otherwise ...
>>>>>>>
>>>>>>> ciao,
>>>>>>> fran.
>>>>>>>
>>>>>>>
>>>>>>>     
>>>>>>>         
>>>>>>>               
>>>>>>   
>>>>>>       
>>>>>>             
>>>>> Send bugs reports to this list.
>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>>> "unsubscribe
>>>>> csound"
>>>>>
>>>>>
>>>>>     
>>>>>           
>>>>   
>>>>         
>>> Send bugs reports to this list.
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>> csound"
>>> # Csound Audio Synthesis System
>>> # Copyright (C) 2007 John ffitch and Csound community
>>> # This file is distributed under the same license as the Csound package.
>>> # John ffitch , 2007.
>>> #
>>> msgid ""
>>> msgstr ""
>>> "Project-Id-Version: CSOUND 5.xx\n"
>>> "Report-Msgid-Bugs-To: \n"
>>> "POT-Creation-Date: 2008-07-26 19:39+0100\n"
>>> "PO-Revision-Date: 2008-09-07 15:25+0100\n"
>>> "Last-Translator:\n"
>>> "Language-Team: Italian\n"
>>> "MIME-Version: 1.0\n"
>>> "Content-Type: text/plain; charset=UTF-8\n"
>>> "Content-Transfer-Encoding: 8bit\n"
>>>
>>> #: Engine/auxfd.c:97
>>> #, c-format
>>> msgid "fdclose: no record of fd %p"
>>> msgstr "fdclose: non c'è registrazione di fd %p"
>>>
>>> #: Engine/auxfd.c:144
>>> #, c-format
>>> msgid "auxlist for instr %d (%p):\n"
>>> msgstr "auxlist per strumento %d (%p):\n"
>>>
>>> #: Engine/auxfd.c:148
>>> #, c-format
>>> msgid "\tauxch at %p: size %ld, auxp %p, endp %p\n"
>>> msgstr "\tauxch a %p: dimensione %ld, auxp %p, endp %p\n"
>>>
>>> #: Engine/auxfd.c:158
>>> #, c-format
>>> msgid "fdlist for instr %d (%p):"
>>> msgstr "fdlist per strumento %d (%p):"
>>>
>>> #: Engine/auxfd.c:161
>>> #, c-format
>>> msgid "  fd %p in %p"
>>> msgstr "  fd %p in %p"
>>>
>>> #: Engine/cfgvar.c:57
>>> msgid "(no error)"
>>> msgstr "(nessun errore)"
>>>
>>> #: Engine/cfgvar.c:58
>>> msgid "invalid variable name"
>>> msgstr "nome di variabile non valido"
>>>
>>> #: Engine/cfgvar.c:59
>>> msgid "invalid variable type"
>>> msgstr "tipo di variabile non valido"
>>>
>>> #: Engine/cfgvar.c:60
>>> msgid "invalid flags specified"
>>> msgstr "opzione (flag) non valida"
>>>
>>> #: Engine/cfgvar.c:61
>>> msgid "NULL pointer argument"
>>> msgstr "argomento del puntatore NULL"
>>>
>>> #: Engine/cfgvar.c:62
>>> msgid "the specified value is too high"
>>> msgstr "il valore specificato è troppo alto"
>>>
>>> #: Engine/cfgvar.c:63
>>> msgid "the specified value is too low"
>>> msgstr "il valore specificato è troppo basso"
>>>
>>> #: Engine/cfgvar.c:64
>>> msgid "the specified value is not an integer power of two"
>>> msgstr "il valore specificato non è un intero potenza di due"
>>>
>>> #: Engine/cfgvar.c:65
>>> msgid "invalid boolean value; must be 0 or 1"
>>> msgstr "valore booleano non valido; deve essere 0 oppure 1"
>>>
>>> #: Engine/cfgvar.c:66 Opcodes/osc-sock.c:272
>>> msgid "memory allocation failed"
>>> msgstr "allocazione di memoria fallita"
>>>
>>> #: Engine/cfgvar.c:67
>>> msgid "string exceeds maximum allowed length"
>>> msgstr "la lunghezza della stringa supera il valore permesso"
>>>
>>> #: Engine/cfgvar.c:68
>>> msgid "(unknown error)"
>>> msgstr "(errore sconosciuto)"
>>>
>>> #: Engine/csound_orc_compile.c:459
>>> #, c-format
>>> msgid "create_opcode: No rule to handle statemnent of type %d\n"
>>> msgstr "create_opcode: Non c'è regola per una dichiarazione di tipo
>>> %d\n"
>>>
>>> #: Engine/csound_orc_compile.c:645
>>> #, c-format
>>> msgid "create_instrument: instr num %ld\n"
>>> msgstr "create_instrument: strumento num %ld\n"
>>>
>>> #: Engine/csound_orc_compile.c:654
>>> #, c-format
>>> msgid "create_instrument: instr name %s\n"
>>> msgstr "create_instrument: nome dello strumento %s\n"
>>>
>>> #: Engine/csound_orc_compile.c:661 Engine/otran.c:340
>>> msgid "invalid name for instrument"
>>> msgstr "nome dello strumento non valido"
>>>
>>> #: Engine/csound_orc_compile.c:665 Engine/otran.c:345
>>> #, c-format
>>> msgid "instr %s redefined"
>>> msgstr "ridefinito lo strumento %s"
>>>
>>> #: Engine/csound_orc_compile.c:806 Engine/otran.c:142
>>> Engine/symbtab.c:393
>>> #, c-format
>>> msgid "invalid input type for opcode %s"
>>> msgstr "tipo di input non valido per l'opcode %s"
>>>
>>> #: Engine/csound_orc_compile.c:811 Engine/otran.c:147
>>> Engine/symbtab.c:398
>>> #, c-format
>>> msgid "too many input args for opcode %s"
>>> msgstr "troppi argomenti in input per l'opcode %s"
>>>
>>> #: Engine/csound_orc_compile.c:826 Engine/otran.c:162
>>> Engine/symbtab.c:413
>>> #, c-format
>>> msgid "too many output args for opcode %s"
>>> msgstr "troppi argomenti in output per l'opcode %s"
>>>
>>> #: Engine/csound_orc_compile.c:842 Engine/otran.c:181
>>> Engine/symbtab.c:432
>>> #, c-format
>>> msgid "invalid output type for opcode %s"
>>> msgstr "tipo di output non valido per l'opcode %s"
>>>
>>> #: Engine/csound_orc_compile.c:927 Engine/otran.c:328
>>> #, c-format
>>> msgid "instr %ld redefined"
>>> msgstr "strumento %ld ridefinito"
>>>
>>> #: Engine/csound_orc_compile.c:937
>>> msgid "!!! csound->opcodeInfo is NULL !!!\n"
>>> msgstr "!!! csound->opcodeInfo è NULL !!!\n"
>>>
>>> #: Engine/csound_orc_compile.c:1076
>>> #, c-format
>>> msgid "Unknown TREE node of type %d found in root.\n"
>>> msgstr "Nodo sconosciuto di tipo %d trovato in root.\n"
>>>
>>> #: Engine/csound_orc_compile.c:1132 Engine/otran.c:552
>>> Engine/otran.c:1396
>>> #, c-format
>>> msgid "%s invalid sample rate"
>>> msgstr "%s frequenza di campionamento (sr) non valida"
>>>
>>> #: Engine/csound_orc_compile.c:1134 Engine/otran.c:554
>>> Engine/otran.c:1398
>>> #, c-format
>>> msgid "%s invalid control rate"
>>> msgstr "%s frequenza dei segnali di controllo (kr) non valida"
>>>
>>> #: Engine/csound_orc_compile.c:1137 Engine/otran.c:557
>>> Engine/otran.c:1394
>>> #, c-format
>>> msgid "%s invalid ksmps value"
>>> msgstr "%s valore di ksmps non valido"
>>>
>>> #: Engine/csound_orc_compile.c:1139 Engine/otran.c:559
>>> Engine/otran.c:1400
>>> #, c-format
>>> msgid "%s inconsistent sr, kr, ksmps"
>>> msgstr "%s incoerenti sr, kr, ksmps"
>>>
>>> #: Engine/csound_orc_compile.c:1151
>>> msgid "perf-pass statements illegal in header blk\n"
>>> msgstr "Le dichiarazioni di esecuzione sono vietate nel blocco
>>> intestazione (header)\n"
>>>
>>> #: Engine/csound_orc_compile.c:1155
>>> #, c-format
>>> msgid "%d syntax errors in orchestra.  compilation invalid\n"
>>> msgstr "%d errore\\i di sintassi nell'orchestra.  Compilazione non
>>> valida\n"
>>>
>>> #: Engine/csound_orc_compile.c:1215 Engine/otran.c:643
>>> msgid "inconsistent argoff sumcount"
>>> msgstr "argoff sumcount incoerente"
>>>
>>> #: Engine/csound_orc_compile.c:1287 Engine/otran.c:712
>>> #, c-format
>>> msgid "LABELS list is full...extending to %d\n"
>>> msgstr "La lista etichette è piena...estesa a %d\n"
>>>
>>> #: Engine/csound_orc_compile.c:1325 Engine/otran.c:750
>>> #, c-format
>>> msgid "GOTOS list is full..extending to %d\n"
>>> msgstr "La lista GOTOS è piena...estesa a %d\n"
>>>
>>> #: Engine/csound_orc_compile.c:1358 Engine/otran.c:783
>>> #, c-format
>>> msgid "target label '%s' not found"
>>> msgstr "obiettivo dell'etichetta '%s' non trovato"
>>>
>>> #: Engine/csound_orc_compile.c:1423 Engine/otran.c:838
>>> #, c-format
>>> msgid "string syntax '%s'"
>>> msgstr "sintassi della stringa '%s'"
>>>
>>> #: Engine/csound_orc_compile.c:1473 Engine/otran.c:888
>>> #, c-format
>>> msgid "numeric syntax '%s'"
>>> msgstr "sintassi numerica '%s'"
>>>
>>>
>>>       
>>     
>
>   



Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

I changed the line endings and it verifies

818 translated messages, 50 fuzzy translations, 1811 untranslated messages.

Looking hood to me.

=John ff

> Seems OK except for the end-of-line caracters which are in DOS/Windows
> style (\r\n) instead of unix style (\n). Are you working on a windows
> box? The editor end-of-line style can easily be set in the preferences
> of Poedit or in the Utilities Buffer options of JEdit.
>




Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Thanks.
Yes i'm on windows, and i thought to have set end line to unix, (is it ok
unix end line?).
Now i verify.

Many thanks.
Next 1900 lines ...

ciao,
fran



PINOT Francois wrote:
> 
> Seems OK except for the end-of-line caracters which are in DOS/Windows 
> style (\r\n) instead of unix style (\n). Are you working on a windows 
> box? The editor end-of-line style can easily be set in the preferences 
> of Poedit or in the Utilities Buffer options of JEdit.
> 
> Regards
> 
> Francois Pinot
> 
> francibal a écrit :
>> Again me,
>> i'm working on italian translation and this is my file (it is in
>> progress, i
>> need to clear myself about some word), BUT i need to know if it is OK.
>> If someone could take a look and tell me if file is ok (about format and
>> coding) i will be grateful him/her.
>>
>> http://www.nabble.com/file/p25742294/italian.po italian.po 
>>
>> Ciao,
>> fran.
>>
>>
>>
>> francibal wrote:
>>   
>>> THANKS!
>>>
>>> now i will try to use right way, now!
>>>
>>> thanks,
>>> ciao,
>>> fran.
>>>
>>>
>>> PINOT Francois wrote:
>>>     
>>>> I modified the encoding to utf-8 (was iso-8859-1) and added a '\n' 
>>>> character that was missing on line 171. Seems OK now.
>>>>
>>>> Regards
>>>>
>>>> Francois Pinot
>>>>
>>>> francibal a écrit :
>>>>       
>>>>> Thanks Mr. Francois,
>>>>>
>>>>> if You have a little bit time could You try if allegated file is
>>>>> usable
>>>>> or not ?
>>>>> Maybe i can save some work ...
>>>>>
>>>>> Thanks again,
>>>>>
>>>>> ciao,
>>>>> fran
>>>>>
>>>>> http://www.nabble.com/file/p25625040/italian_01.po italian_01.po 
>>>>>
>>>>> PINOT Francois wrote:
>>>>>   
>>>>>         
>>>>>> I use a pure text editor like jEdit, which doesn't add extra
>>>>>> information 
>>>>>> on text formatting as does OpenOffice. Poedit is a good choice too. I 
>>>>>> prefer to use jEdit because it has syntax highlighting.
>>>>>>
>>>>>> Unfortunately you'll have do start again from the original file
>>>>>> because 
>>>>>> your OpenOffice file has probably extra word processing information 
>>>>>> inadequate here.
>>>>>>
>>>>>> Moreover, you have to respect the encoding which is UTF-8 in that
>>>>>> case. 
>>>>>> Normally jEdit and poedit take care of this.
>>>>>>
>>>>>> Regards
>>>>>>
>>>>>> Francois Pinot
>>>>>>
>>>>>> francibal a écrit :
>>>>>>     
>>>>>>           
>>>>>>> Hi Mr. All,
>>>>>>> apologies for my ignorance...
>>>>>>>
>>>>>>> i'm working on italian translation but i need other advice.
>>>>>>> i'm started with open office, and i have translated some strings
>>>>>>> with
>>>>>>> right
>>>>>>> (i hope)
>>>>>>> formatting, but: if source string had (into) an ending return (\n)
>>>>>>> character
>>>>>>> i have copied in the same way. Now i've discover (like Captain
>>>>>>> Cook!)
>>>>>>> specific programs like poedit.
>>>>>>> I can not open my file with these last programs, but, moreover, here
>>>>>>> source
>>>>>>> strings do not have \n visible (strings with \n into), and i don't
>>>>>>> know
>>>>>>> if i
>>>>>>> can make the same things in translation and the program then
>>>>>>> automatically
>>>>>>> make this work (to me seems wrong).
>>>>>>>
>>>>>>> Can You use an open office file? Or it is a wrong format that
>>>>>>> requier
>>>>>>> more
>>>>>>> work to You later?
>>>>>>>
>>>>>>> Again apologies (i know You are now working to next release),
>>>>>>>
>>>>>>> thanks and ciao,
>>>>>>> fran.
>>>>>>>
>>>>>>>
>>>>>>> francibal wrote:
>>>>>>>   
>>>>>>>       
>>>>>>>             
>>>>>>>> Hi List,
>>>>>>>> and welcome back to Mr Wanderer. I've read messages about
>>>>>>>> translations,
>>>>>>>> and i've looked at .po files in cvs. If You want i could try to
>>>>>>>> make
>>>>>>>> italian files (it seems simple to do, i will only write a string in
>>>>>>>> italian under that in english! Easy for me too!). I don't know
>>>>>>>> english
>>>>>>>> so
>>>>>>>> well, but i think to understand all essential (and i have a
>>>>>>>> dictionary).
>>>>>>>> If this can help Your work tell me somethings, otherwise ...
>>>>>>>>
>>>>>>>> ciao,
>>>>>>>> fran.
>>>>>>>>
>>>>>>>>
>>>>>>>>     
>>>>>>>>         
>>>>>>>>               
>>>>>>>   
>>>>>>>       
>>>>>>>             
>>>>>> Send bugs reports to this list.
>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>>>> "unsubscribe
>>>>>> csound"
>>>>>>
>>>>>>
>>>>>>     
>>>>>>           
>>>>>   
>>>>>         
>>>> Send bugs reports to this list.
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>> "unsubscribe
>>>> csound"
>>>> # Csound Audio Synthesis System
>>>> # Copyright (C) 2007 John ffitch and Csound community
>>>> # This file is distributed under the same license as the Csound
>>>> package.
>>>> # John ffitch , 2007.
>>>> #
>>>> msgid ""
>>>> msgstr ""
>>>> "Project-Id-Version: CSOUND 5.xx\n"
>>>> "Report-Msgid-Bugs-To: \n"
>>>> "POT-Creation-Date: 2008-07-26 19:39+0100\n"
>>>> "PO-Revision-Date: 2008-09-07 15:25+0100\n"
>>>> "Last-Translator:\n"
>>>> "Language-Team: Italian\n"
>>>> "MIME-Version: 1.0\n"
>>>> "Content-Type: text/plain; charset=UTF-8\n"
>>>> "Content-Transfer-Encoding: 8bit\n"
>>>>
>>>> #: Engine/auxfd.c:97
>>>> #, c-format
>>>> msgid "fdclose: no record of fd %p"
>>>> msgstr "fdclose: non c'è registrazione di fd %p"
>>>>
>>>> #: Engine/auxfd.c:144
>>>> #, c-format
>>>> msgid "auxlist for instr %d (%p):\n"
>>>> msgstr "auxlist per strumento %d (%p):\n"
>>>>
>>>> #: Engine/auxfd.c:148
>>>> #, c-format
>>>> msgid "\tauxch at %p: size %ld, auxp %p, endp %p\n"
>>>> msgstr "\tauxch a %p: dimensione %ld, auxp %p, endp %p\n"
>>>>
>>>> #: Engine/auxfd.c:158
>>>> #, c-format
>>>> msgid "fdlist for instr %d (%p):"
>>>> msgstr "fdlist per strumento %d (%p):"
>>>>
>>>> #: Engine/auxfd.c:161
>>>> #, c-format
>>>> msgid "  fd %p in %p"
>>>> msgstr "  fd %p in %p"
>>>>
>>>> #: Engine/cfgvar.c:57
>>>> msgid "(no error)"
>>>> msgstr "(nessun errore)"
>>>>
>>>> #: Engine/cfgvar.c:58
>>>> msgid "invalid variable name"
>>>> msgstr "nome di variabile non valido"
>>>>
>>>> #: Engine/cfgvar.c:59
>>>> msgid "invalid variable type"
>>>> msgstr "tipo di variabile non valido"
>>>>
>>>> #: Engine/cfgvar.c:60
>>>> msgid "invalid flags specified"
>>>> msgstr "opzione (flag) non valida"
>>>>
>>>> #: Engine/cfgvar.c:61
>>>> msgid "NULL pointer argument"
>>>> msgstr "argomento del puntatore NULL"
>>>>
>>>> #: Engine/cfgvar.c:62
>>>> msgid "the specified value is too high"
>>>> msgstr "il valore specificato è troppo alto"
>>>>
>>>> #: Engine/cfgvar.c:63
>>>> msgid "the specified value is too low"
>>>> msgstr "il valore specificato è troppo basso"
>>>>
>>>> #: Engine/cfgvar.c:64
>>>> msgid "the specified value is not an integer power of two"
>>>> msgstr "il valore specificato non è un intero potenza di due"
>>>>
>>>> #: Engine/cfgvar.c:65
>>>> msgid "invalid boolean value; must be 0 or 1"
>>>> msgstr "valore booleano non valido; deve essere 0 oppure 1"
>>>>
>>>> #: Engine/cfgvar.c:66 Opcodes/osc-sock.c:272
>>>> msgid "memory allocation failed"
>>>> msgstr "allocazione di memoria fallita"
>>>>
>>>> #: Engine/cfgvar.c:67
>>>> msgid "string exceeds maximum allowed length"
>>>> msgstr "la lunghezza della stringa supera il valore permesso"
>>>>
>>>> #: Engine/cfgvar.c:68
>>>> msgid "(unknown error)"
>>>> msgstr "(errore sconosciuto)"
>>>>
>>>> #: Engine/csound_orc_compile.c:459
>>>> #, c-format
>>>> msgid "create_opcode: No rule to handle statemnent of type %d\n"
>>>> msgstr "create_opcode: Non c'è regola per una dichiarazione di tipo
>>>> %d\n"
>>>>
>>>> #: Engine/csound_orc_compile.c:645
>>>> #, c-format
>>>> msgid "create_instrument: instr num %ld\n"
>>>> msgstr "create_instrument: strumento num %ld\n"
>>>>
>>>> #: Engine/csound_orc_compile.c:654
>>>> #, c-format
>>>> msgid "create_instrument: instr name %s\n"
>>>> msgstr "create_instrument: nome dello strumento %s\n"
>>>>
>>>> #: Engine/csound_orc_compile.c:661 Engine/otran.c:340
>>>> msgid "invalid name for instrument"
>>>> msgstr "nome dello strumento non valido"
>>>>
>>>> #: Engine/csound_orc_compile.c:665 Engine/otran.c:345
>>>> #, c-format
>>>> msgid "instr %s redefined"
>>>> msgstr "ridefinito lo strumento %s"
>>>>
>>>> #: Engine/csound_orc_compile.c:806 Engine/otran.c:142
>>>> Engine/symbtab.c:393
>>>> #, c-format
>>>> msgid "invalid input type for opcode %s"
>>>> msgstr "tipo di input non valido per l'opcode %s"
>>>>
>>>> #: Engine/csound_orc_compile.c:811 Engine/otran.c:147
>>>> Engine/symbtab.c:398
>>>> #, c-format
>>>> msgid "too many input args for opcode %s"
>>>> msgstr "troppi argomenti in input per l'opcode %s"
>>>>
>>>> #: Engine/csound_orc_compile.c:826 Engine/otran.c:162
>>>> Engine/symbtab.c:413
>>>> #, c-format
>>>> msgid "too many output args for opcode %s"
>>>> msgstr "troppi argomenti in output per l'opcode %s"
>>>>
>>>> #: Engine/csound_orc_compile.c:842 Engine/otran.c:181
>>>> Engine/symbtab.c:432
>>>> #, c-format
>>>> msgid "invalid output type for opcode %s"
>>>> msgstr "tipo di output non valido per l'opcode %s"
>>>>
>>>> #: Engine/csound_orc_compile.c:927 Engine/otran.c:328
>>>> #, c-format
>>>> msgid "instr %ld redefined"
>>>> msgstr "strumento %ld ridefinito"
>>>>
>>>> #: Engine/csound_orc_compile.c:937
>>>> msgid "!!! csound->opcodeInfo is NULL !!!\n"
>>>> msgstr "!!! csound->opcodeInfo è NULL !!!\n"
>>>>
>>>> #: Engine/csound_orc_compile.c:1076
>>>> #, c-format
>>>> msgid "Unknown TREE node of type %d found in root.\n"
>>>> msgstr "Nodo sconosciuto di tipo %d trovato in root.\n"
>>>>
>>>> #: Engine/csound_orc_compile.c:1132 Engine/otran.c:552
>>>> Engine/otran.c:1396
>>>> #, c-format
>>>> msgid "%s invalid sample rate"
>>>> msgstr "%s frequenza di campionamento (sr) non valida"
>>>>
>>>> #: Engine/csound_orc_compile.c:1134 Engine/otran.c:554
>>>> Engine/otran.c:1398
>>>> #, c-format
>>>> msgid "%s invalid control rate"
>>>> msgstr "%s frequenza dei segnali di controllo (kr) non valida"
>>>>
>>>> #: Engine/csound_orc_compile.c:1137 Engine/otran.c:557
>>>> Engine/otran.c:1394
>>>> #, c-format
>>>> msgid "%s invalid ksmps value"
>>>> msgstr "%s valore di ksmps non valido"
>>>>
>>>> #: Engine/csound_orc_compile.c:1139 Engine/otran.c:559
>>>> Engine/otran.c:1400
>>>> #, c-format
>>>> msgid "%s inconsistent sr, kr, ksmps"
>>>> msgstr "%s incoerenti sr, kr, ksmps"
>>>>
>>>> #: Engine/csound_orc_compile.c:1151
>>>> msgid "perf-pass statements illegal in header blk\n"
>>>> msgstr "Le dichiarazioni di esecuzione sono vietate nel blocco
>>>> intestazione (header)\n"
>>>>
>>>> #: Engine/csound_orc_compile.c:1155
>>>> #, c-format
>>>> msgid "%d syntax errors in orchestra.  compilation invalid\n"
>>>> msgstr "%d errore\\i di sintassi nell'orchestra.  Compilazione non
>>>> valida\n"
>>>>
>>>> #: Engine/csound_orc_compile.c:1215 Engine/otran.c:643
>>>> msgid "inconsistent argoff sumcount"
>>>> msgstr "argoff sumcount incoerente"
>>>>
>>>> #: Engine/csound_orc_compile.c:1287 Engine/otran.c:712
>>>> #, c-format
>>>> msgid "LABELS list is full...extending to %d\n"
>>>> msgstr "La lista etichette è piena...estesa a %d\n"
>>>>
>>>> #: Engine/csound_orc_compile.c:1325 Engine/otran.c:750
>>>> #, c-format
>>>> msgid "GOTOS list is full..extending to %d\n"
>>>> msgstr "La lista GOTOS è piena...estesa a %d\n"
>>>>
>>>> #: Engine/csound_orc_compile.c:1358 Engine/otran.c:783
>>>> #, c-format
>>>> msgid "target label '%s' not found"
>>>> msgstr "obiettivo dell'etichetta '%s' non trovato"
>>>>
>>>> #: Engine/csound_orc_compile.c:1423 Engine/otran.c:838
>>>> #, c-format
>>>> msgid "string syntax '%s'"
>>>> msgstr "sintassi della stringa '%s'"
>>>>
>>>> #: Engine/csound_orc_compile.c:1473 Engine/otran.c:888
>>>> #, c-format
>>>> msgid "numeric syntax '%s'"
>>>> msgstr "sintassi numerica '%s'"
>>>>
>>>>
>>>>       
>>>     
>>
>>   
> 
> 
> 
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
> 
> 

-- 
View this message in context: http://www.nabble.com/translation-tp25569867p25746089.html
Sent from the Csound - General mailing list archive at Nabble.com.



Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"