Getting the translation source files

l10n
#1

Hi,

Is there a way to get the sdf files alone, and not the whole tree ?

Even if they're all packed into a big en-US.sdf file.
I use Narro [1] for translating in Romanian and Narro knows both Gettext
and SDF, but I'd rather work on the native file than go through conversion.
And having all the small sdf files is much easier in the localization
process considering the poor context information.

[1]
http://tradu.softwareliber.ro/narro_project_file_list.php?l=ro&p=1&pf=&s=

#2

Here's the current Norwegian Bokmål: http://login.kristshell.net/~olorin/
Notice that "nb.po" and "lo-build-nb.po" (available from the Git repo)
contain LibreOffice specific strings and the GSI_nx.sdf.bz2 files (which
is locally built from PO files extracted by po2oo and rebuilt with
po2oo) a compressed version of the current OOo 3.3 m9 translations.

Olav

#3

Pe 08.10.2010 19:41, Olav Dahlum a scris:

Hi,

Is there a way to get the sdf files alone, and not the whole tree ?

Even if they're all packed into a big en-US.sdf file.
I use Narro [1] for translating in Romanian and Narro knows both Gettext
and SDF, but I'd rather work on the native file than go through conversion.
And having all the small sdf files is much easier in the localization
process considering the poor context information.

[1]
http://tradu.softwareliber.ro/narro_project_file_list.php?l=ro&p=1&pf=&s=

Here's the current Norwegian Bokmål: http://login.kristshell.net/~olorin/
Notice that "nb.po" and "lo-build-nb.po" (available from the Git repo)
contain LibreOffice specific strings and the GSI_nx.sdf.bz2 files (which
is locally built from PO files extracted by po2oo and rebuilt with
po2oo) a compressed version of the current OOo 3.3 m9 translations.

Olav

I'd rather have the GSI file, as it is here
http://ftp.linux.cz/pub/localization/OpenOffice.org/latest/GSI/en-US.sdf
or better yet, all the small files from the source code.

I export in the same format and use the sdf file to rebuild an rpm so I
can have a normal package and don't have to go through the hassle of
building from scratch.

#4

Pe 08.10.2010 20:32, Alexandru Szasz a scris:

Pe 08.10.2010 19:41, Olav Dahlum a scris:

Hi,

Is there a way to get the sdf files alone, and not the whole tree ?

Even if they're all packed into a big en-US.sdf file.
I use Narro [1] for translating in Romanian and Narro knows both Gettext
and SDF, but I'd rather work on the native file than go through conversion.
And having all the small sdf files is much easier in the localization
process considering the poor context information.

[1]
http://tradu.softwareliber.ro/narro_project_file_list.php?l=ro&p=1&pf=&s=

Here's the current Norwegian Bokmål: http://login.kristshell.net/~olorin/
Notice that "nb.po" and "lo-build-nb.po" (available from the Git repo)
contain LibreOffice specific strings and the GSI_nx.sdf.bz2 files (which
is locally built from PO files extracted by po2oo and rebuilt with
po2oo) a compressed version of the current OOo 3.3 m9 translations.

Olav

I'd rather have the GSI file, as it is here
http://ftp.linux.cz/pub/localization/OpenOffice.org/latest/GSI/en-US.sdf
or better yet, all the small files from the source code.

I export in the same format and use the sdf file to rebuild an rpm so I
can have a normal package and don't have to go through the hassle of
building from scratch.

My mistake, I see you have a sdf there, but a translated one (source on
one line, translation on the other); I can get that file now, but I'm
looking for a source for the en-US.sdf so I can just set up a process to
download it periodically and make it available in Narro for translations.

#5

Until we have a process in place, use these for any translation based on
upstream:
http://download.services.openoffice.org/files/extended/ooomisc/sdf/
Here's the one the one above is based on:
http://login.kristshell.net/~olorin/en-US.sdf.tar.bz2

Olav

#6

Pe 08.10.2010 20:51, Olav Dahlum a scris:

Pe 08.10.2010 20:32, Alexandru Szasz a scris:

Pe 08.10.2010 19:41, Olav Dahlum a scris:

Hi,

Is there a way to get the sdf files alone, and not the whole tree ?

Even if they're all packed into a big en-US.sdf file.
I use Narro [1] for translating in Romanian and Narro knows both Gettext
and SDF, but I'd rather work on the native file than go through conversion.
And having all the small sdf files is much easier in the localization
process considering the poor context information.

[1]
http://tradu.softwareliber.ro/narro_project_file_list.php?l=ro&p=1&pf=&s=

Here's the current Norwegian Bokmål: http://login.kristshell.net/~olorin/
Notice that "nb.po" and "lo-build-nb.po" (available from the Git repo)
contain LibreOffice specific strings and the GSI_nx.sdf.bz2 files (which
is locally built from PO files extracted by po2oo and rebuilt with
po2oo) a compressed version of the current OOo 3.3 m9 translations.

Olav

I'd rather have the GSI file, as it is here
http://ftp.linux.cz/pub/localization/OpenOffice.org/latest/GSI/en-US.sdf
or better yet, all the small files from the source code.

I export in the same format and use the sdf file to rebuild an rpm so I
can have a normal package and don't have to go through the hassle of
building from scratch.

My mistake, I see you have a sdf there, but a translated one (source on
one line, translation on the other); I can get that file now, but I'm
looking for a source for the en-US.sdf so I can just set up a process to
download it periodically and make it available in Narro for translations.

Until we have a process in place, use these for any translation based on
upstream:
http://download.services.openoffice.org/files/extended/ooomisc/sdf/
Here's the one the one above is based on:
http://login.kristshell.net/~olorin/en-US.sdf.tar.bz2

Olav

That will do, thank you.