On 18/01/2007, at 6:47 PM, Pavel Janík wrote:
Is it OK to submit a GSI file with no blank lines between strings?
The answer is simple: there is no need to include blank lines
between strings... If you have blank lines in the current GSI file,
you can save up to 6 bytes...
Great, tha
Is it OK to submit a GSI file with no blank lines between strings?
The answer is simple: there is no need to include blank lines between
strings... If you have blank lines in the current GSI file, you can
save up to 6 bytes...
--
Pavel Janík
[EMAIL PROTECTED]
Answering my own mail here...
On 18/01/2007, at 5:14 PM, Clytie Siddall wrote:
I will try re-merging the files and running the conversion again.
I re-merged the files from m199 POT, using pomigrate2 [1], then ran
po2oo again to convert back to .sdf format.
That worked. I have a 12MB out
HI again :)
On 18/01/2007, at 5:02 PM, Aiet Kolkhi wrote:
Yes, we did that a while ago. I'm not sure if the Help files were
migrated, though. They might still be 2.1.
I see. Then copying helpcontent2 and all GUI foldes to one folder and
updating them from the latest milestone would solve the
Yes, we did that a while ago. I'm not sure if the Help files were
migrated, though. They might still be 2.1.
I see. Then copying helpcontent2 and all GUI foldes to one folder and
updating them from the latest milestone would solve the problem.
Combine the files, then reconvert. OK, I'll try to
Thanks for your reply, Aiet. :)
On 18/01/2007, at 4:48 PM, Aiet Kolkhi wrote:
having the OOo GUI and UA separated is very handy in Pootle, but when
it comes to SDI submission, you should combine existing GUI and UA,
compile SDI file and submit it as SDF.
Oh.
First you should migrate your PO
I tried running po2oo (Translate Toolkit) on the helpcontent2
directory, using the whole en_US.sdf file as the template, but the
process complained that it couldn't find the template for any of the
files.
Are you sure you are using the en-US template that came with the same
milestone PO files co
Hi Clytie,
having the OOo GUI and UA separated is very handy in Pootle, but when
it comes to SDI submission, you should combine existing GUI and UA,
compile SDI file and submit it as SDF.
First you should migrate your PO files to at least m199 milestone,
localize the remaining phrases and then c
Thanks to both Ain and Rafaella for their replies :)
On 17/01/2007, at 11:47 PM, Rafaella Braconi wrote:
Ain Vagula wrote:
On 1/17/07, Ain Vagula <[EMAIL PROTECTED]> wrote:
On 1/17/07, Clytie Siddall <[EMAIL PROTECTED]> wrote:
> Hi everyone :)
>
> Are there any different instructions for s
Hi
Ain Vagula wrote:
On 1/17/07, Ain Vagula <[EMAIL PROTECTED]> wrote:
On 1/17/07, Clytie Siddall <[EMAIL PROTECTED]> wrote:
> Hi everyone :)
>
> Are there any different instructions for submitting helpcontent2
> (Help)? Should it also be a .sdf file?
Helpcontent belongs to the same sdf-file
On 1/17/07, Ain Vagula <[EMAIL PROTECTED]> wrote:
On 1/17/07, Clytie Siddall <[EMAIL PROTECTED]> wrote:
> Hi everyone :)
>
> Are there any different instructions for submitting helpcontent2
> (Help)? Should it also be a .sdf file?
Helpcontent belongs to the same sdf-file when creating with toolk
On 1/17/07, Clytie Siddall <[EMAIL PROTECTED]> wrote:
Hi everyone :)
Are there any different instructions for submitting helpcontent2
(Help)? Should it also be a .sdf file?
Helpcontent belongs to the same sdf-file when creating with toolkit
from po-repository created with the same toolkit.
Hi everyone :)
Are there any different instructions for submitting helpcontent2
(Help)? Should it also be a .sdf file?
I saw something about only submitting completed strings. Is that
required? If so, Is there a quick way to strip any incomplete strings
out of files?
Our translation wor
13 matches
Mail list logo
