LibreOffice build with local PO-file

l10n
#1

Hi all

Tell me please, how can I make LibreOffice build from sources with my .po
file for testing our translation?
I tried replace po-file from my local copy of git repository to our po-file
and build, but LibreOffice builded with old translation.

Best regards, Doroshenko Alexey.

#2

$ cd po/
$ make update-sdf

Then build as usual.

Best regards,
Andras

#3

Thank you, I'll try it.

#4

Hi,

Do we have a complete LOCAL BUILD instructions, an url would be fine?
If not, could you share yours...Thanks,
Anousak

#5

Hi,

Hi,

Do we have a complete LOCAL BUILD instructions, an url would be fine?
If not, could you share yours...Thanks,

I also would like to read the instructions if any, otherwise it would be
best to have a Wiki page on how to build a localized one.
IMHO it should describe
* further required packages/dependencies such as translate-toolkit
* passing the --with-lang option to configure or autogen.sh
* updating lo-build-*.sdf by `make update-sdf`
Any suggestions?

Cheers,
-- Takeshi Abe

#6

Hi,

Hi,

Do we have a complete LOCAL BUILD instructions, an url would be fine?
If not, could you share yours...Thanks,

I also would like to read the instructions if any, otherwise it would be
best to have a Wiki page on how to build a localized one.
IMHO it should describe
* further required packages/dependencies such as translate-toolkit
* passing the --with-lang option to configure or autogen.sh
* updating lo-build-*.sdf by `make update-sdf`
Any suggestions?

There are build instructions at the wiki, at
http://wiki.documentfoundation.org/Development/How_to_build
There are two phases in building LibreOffice, the part where you clone
the repositories (needs fast connections) and the actual compilation
(took me three hours). Subsequent building of LibreOffice should be
must faster, so you would keep around the files. My build directory is
8.2GB, which is fine for the thrill to have compiled such a big
program. Therefore, estimate 10GB of space for LibO building and
installation.

The Wiki page is currently quite good, however it can become even
better if we note down even the small gotchas. So, write down if
something needs to get updated on the wiki.

Simos

#7

After:
cd po
make update-sdf
LO builded with old translation again, strings from new po-file ignored (

#8

Hi Simos,

(snip)

I also would like to read the instructions if any, otherwise it would be
best to have a Wiki page on how to build a localized one.
IMHO it should describe
* further required packages/dependencies such as translate-toolkit
* passing the --with-lang option to configure or autogen.sh
* updating lo-build-*.sdf by `make update-sdf`
Any suggestions?

There are build instructions at the wiki, at
http://wiki.documentfoundation.org/Development/How_to_build
There are two phases in building LibreOffice, the part where you clone
the repositories (needs fast connections) and the actual compilation
(took me three hours). Subsequent building of LibreOffice should be
must faster, so you would keep around the files. My build directory is
8.2GB, which is fine for the thrill to have compiled such a big
program. Therefore, estimate 10GB of space for LibO building and
installation.

Yes, the How_to_build is indeed useful for me too, and your estimation
sounds the same to my case.
But a localized build needs another consideration to be taken into, like
the above 3 items, which are missing in the page.
For example, if you do not have translate-toolkit installed in advance,
running `make update-sdf` will just fail with a vague error messages.

The Wiki page is currently quite good, however it can become even
better if we note down even the small gotchas. So, write down if
something needs to get updated on the wiki.

Thanks for your suggestion.
I will try adding some of such gotchas to the wiki.

Cheers,
-- Takeshi Abe

#9

You probably did not start a fresh build. Remove
stamp/build.extra.translations and
stamp/build.extra.translations.lang.list, then run make again.

Andras

#10

Hi,

The Wiki page is currently quite good, however it can become even
better if we note down even the small gotchas. So, write down if
something needs to get updated on the wiki.

Thanks for your suggestion.
I will try adding some of such gotchas to the wiki.

done, rather a new page:
http://wiki.documentfoundation.org/Development/How_to_build/localized
Please refine it.

Cheers,
-- Takeshi Abe

#11

You probably did not start a fresh build. Remove
stamp/build.extra.translations and
stamp/build.extra.
translations.lang.list, then run make again.

stamp directory not contain this files

#12

Hi Simos,

Are saying that in order for me to setup local build I would need high
speed Internet and that it requires to download files at least 8.2GB?
Please clarify. Many thanks.

Oh my gosh...my ADSL (256KB/s) would take weeks to complete.

Regards,
Anousak

#13

Hi Simos,

Are saying that in order for me to setup local build I would need high
speed Internet and that it requires to download files at least 8.2GB?
Please clarify. Many thanks.

It is about 8GB of total diskspace, which includes the compiled files that
make the big difference.
The git repositories for libreoffice are about 2GB, which is reasonable for
a project of this magnitude.
Therefore, the build process requires to download about 2GB of data using
the git:// protocol.

Once you have those 2GB clones, subsequent updates are small and easy to do.

In addition to this, there are about 100-200MB of Linux dev packages to help
you compile LibreOffice.

Oh my gosh...my ADSL (256KB/s) would take weeks to complete.

Is that a 2Mbit/s line (256 Kbit/s * 8 KB/Kbit) or a 256Kbit/s line
(32KB/s)?

It is possible to create a ZIP file of those 2GB clones. Then, you can use
your favorite download manager to download this ZIP file from a web server.
Then, you uncompress it in your clone/ directory and continue with the
installation.

Best,
Simos

#14

Simos,

Many thanks for your kind explanation.

Is that a 2Mbit/s line (256 Kbit/s * 8 KB/Kbit) or a 256Kbit/s line
(32KB/s)?

It is possible to create a ZIP file of those 2GB clones. Then, you can use
your favorite download manager to download this ZIP file from a web server.
Then, you uncompress it in your clone/ directory and continue with the
installation.

My Internet line is of 256Kbit/s (ADSL- download stream 256kb/s and up
stream is about 128KB/s per se), what they said, but actual download
speed is about 20-30KB/s.
Would you please suggest on how I can clone and zip before I download
them? I can do some small downloads at later stage. This might be the
way.

Appreciated in advance.

Anousak

#15

Simos,

Many thanks for your kind explanation.

Is that a 2Mbit/s line (256 Kbit/s * 8 KB/Kbit) or a 256Kbit/s line
(32KB/s)?

It is possible to create a ZIP file of those 2GB clones. Then, you can use
your favorite download manager to download this ZIP file from a web server.
Then, you uncompress it in your clone/ directory and continue with the
installation.

My Internet line is of 256Kbit/s (ADSL- download stream 256kb/s and up
stream is about 128KB/s per se), what they said, but actual download
speed is about 20-30KB/s.
Would you please suggest on how I can clone and zip before I download
them? I can do some small downloads at later stage. This might be the
way.

Appreciated in advance.

Hi Anousak,

I prepared these zip files. Here are the instructions on how to use them.
LibreOffice currently uses 1+19 git repositories.
There is a main repository, and inside this repository, in the
'clone/' subdirectory, is the actually code of LibreOffice, in 19 git
repositories.

Some important git background. Let's say that mygitrepo/ is a typical
git repository.
There is a mygitrepo/.git/ directory that contains everything that
makes this a git repository. It has the full history, and all the
source code in a compressed form. The various files you see in
mygitrepo/*.* are simply a checked-out version of the repository.
Therefore, if I want to send you a git repository, I only need to send
you the mygitrepo/ with the mygitrepo/.git/ subdirectory. When you
receive this ZIP file with mygitrepo/ (and .git/ inside), you simply
run the commands

$ cd mygitrepo/
$ ls # no files are
found because I erased them to save space. However, .git is there.
$ ls -d .git # the .git/, that
makes the repository is there. Has all the info we need.
.git/
$ git reset --hard # This is the magic
command. It extracts the files from the repository.
                                                    # This command
undoes the erasing I did in order to save space. Now you have
                                                    # a fully working
git repository!
$ git pull --rebase # With this command you may
update the repository to the latest version.
                                                    # Connects to
git.freedesktop.org to update.

I have two archives for you,
1. loroot.git.17Nov10.zip, the main repository for LibreOffice. It has
a clone/ subdirectory which is empty.
2. clone.git.17Nov10.zip, the 19 repositories of LibreOffice. Put the
dir content into loroot/clone/
For example, the artwork will be found in loroot/clone/artwork/

Download from
a. http://simos.info/LibreOffice/loroot.git.17Nov10.zip 115MB
b. http://simos.info/LibreOffice/clone.git.17Nov10.zip 984MB

Feel free to use a download manager, such as JDownloader.

Remember for each of the 20 repositories to perform the 'git reset
--hard' command in order to restore the source files. For restore the
main repository 'loroot', then restore each of the 19 repos.

Finally, follow the instructions at
http://wiki.documentfoundation.org/Development/How_to_build
When you build LibO for the first time, the build script can see that
you already downloaded those 19 repositories and will continue with
compiling.

Hope this helps,
Simos

p.s.
Here is the list of the 19 repos, in REPOS.txt,

artwork
base
bootstrap
calc
components
extensions
extras
filters
help
impress
libs-core
libs-extern
libs-extern-sys
libs-gui
postprocess
sdk
testing
ure
writer

You can restore all of them with 'git reset --hard' easily if you run

cat REPOS.txt | awk '{ printf "(cd %s ; git reset --hard)\n", $1}'

And here is the output of the above command. You can copy and paste
this in order to restore those 19 repos in one go, very easily.

(cd artwork ; git reset --hard)
(cd base ; git reset --hard)
(cd bootstrap ; git reset --hard)
(cd calc ; git reset --hard)
(cd components ; git reset --hard)
(cd extensions ; git reset --hard)
(cd extras ; git reset --hard)
(cd filters ; git reset --hard)
(cd help ; git reset --hard)
(cd impress ; git reset --hard)
(cd libs-core ; git reset --hard)
(cd libs-extern ; git reset --hard)
(cd libs-extern-sys ; git reset --hard)
(cd libs-gui ; git reset --hard)
(cd postprocess ; git reset --hard)
(cd sdk ; git reset --hard)
(cd testing ; git reset --hard)
(cd ure ; git reset --hard)
(cd writer ; git reset --hard)

#16

Simos,

This is an excellent how-to/instrcution, thanks for the efforts you've
put in. I will download these two files, try to follow your clear
explanation. I am sure to be back on it later.

Ciao!
Regards
Anousak