-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jean-Christophe Helary ha scritto:
>
> On 19 juin 07, at 17:12, Alessandro Cattelan wrote:
>> I don't understand why you need to create .pot instead of .po files. I
>> converted the sdf to po files and OmegaT just ignores the msgstr
>> content, so wha
Thank you Alessandro...
Best,
Charles.
Alessandro Cattelan a écrit :
> Charles-H. Schulz ha scritto:
> > Hi,
>
> > sorry this is a side question, as I'm trying to understand the way to
> > work with OmegaT and how we end up enriching / easing the localization
> > processes.
> > What exactly is t
On 19 juin 07, at 19:51, Rafaella Braconi wrote:
yes, I was also suggesting jean-Christophe to use that tmx files
but I think that he really want to make sure to get the most
updated tmx files...
I am currently loading them and I don't see anything problematic.
Are you referring to the
Hi Jean-Christophe,
Jean-Christophe Helary wrote:
On 19 juin 07, at 18:17, Rafaella Braconi wrote:
Hi Alessandro, Jean-Christophe,
Alessandro Cattelan wrote:
Jean-Christophe Helary ha scritto:
I think Rafaella should be able to provide you with proper TMX files
that match the .sdf cont
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Charles-H. Schulz ha scritto:
> Hi,
>
> sorry this is a side question, as I'm trying to understand the way to
> work with OmegaT and how we end up enriching / easing the localization
> processes.
> What exactly is translation memory and TMX and how do
Hi,
sorry this is a side question, as I'm trying to understand the way to
work with OmegaT and how we end up enriching / easing the localization
processes.
What exactly is translation memory and TMX and how do they work?
Thank you,
Charles.
--
On 19 juin 07, at 17:12, Alessandro Cattelan wrote:
I don't understand why you need to create .pot instead of .po files. I
converted the sdf to po files and OmegaT just ignores the msgstr
content, so what is the use of having a pot file with empty msgstr
fields?
Because I am pretty sure Omeg
On 19 juin 07, at 18:17, Rafaella Braconi wrote:
Hi Alessandro, Jean-Christophe,
Alessandro Cattelan wrote:
Jean-Christophe Helary ha scritto:
I think Rafaella should be able to provide you with proper TMX files
that match the .sdf contents.
Rafaella has already provided us with the OLH
Hi Alessandro, Jean-Christophe,
Alessandro Cattelan wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jean-Christophe Helary ha scritto:
Basically OmegaT's PO handling is only (just like for monolingual files)
to put in the target editing field the contents of source, for edition.
Omeg
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jean-Christophe Helary ha scritto:
> Basically OmegaT's PO handling is only (just like for monolingual files)
> to put in the target editing field the contents of source, for edition.
>
> OmegaT is not able to know that a target already exist and to p
On 19 juin 07, at 15:50, Alessandro Cattelan wrote:
Now I have one more question to which I'm sure Jean-Cristophe has the
answer... ;o)
When opening a project with OmegaT I thought that the text in
msgstr in
the PO file would show up in the target segment, but that is not the
case. I think
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
F Wolff ha scritto:
> On Di, 2007-06-19 at 07:56 +0200, Alessandro Cattelan wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Hi,
>> The first segment that OmegaT opens for every PO file is the following:
>>
>> "Project-Id-Version: PACK
On Di, 2007-06-19 at 07:56 +0200, Alessandro Cattelan wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi,
> The first segment that OmegaT opens for every PO file is the following:
>
> "Project-Id-Version: PACKAGE VERSION\n"
> "Report-Msgid-Bugs-To:
> http://qa.openoffice.org/issues/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
The first segment that OmegaT opens for every PO file is the following:
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To:
http://qa.openoffice.org/issues/enter_bug.cgi?subcomponent=ui&comment=&short_desc=Localization%20issue%20in%20f
14 matches
Mail list logo
