I think that the important question is how to test the translations.
I asked this question more than a year ago and there was no answer.
So, we just have to bear with this and try to do our best for the rest.
Dashamir
I think that the important question is how to test the translations.
I asked this question more than a year ago and there was no answer.
So, we just have to bear with this and try to do our best for the rest.
Dashamir
I agree
Are the spec files of daily RPM builds available somewhere?
I suppose I could build language pack for myself.
It would be a great help for localization process.
Thanks
Those spec files are part of the source code, but you do not need to
build RPMs, you can configure the build --with-lang=<your language
and make dev-install.
Andras
Hi,
Translations were updated for LibreOffice 4.0.0 beta2, rc1, rc2. Next
comes rc3, then 4.0.1 rc1, rc2 and so on. Basically you get updated
language pack in every second week. If you need it more frequently,
you can build LibreOffice yourself.
Best regards,
Andras
Hello,
Assuming that I have a full git copy of libreoffice's core repository,
(and a .zip snapshot of translations repo)
can I build a langpack for my language only?
Is it necessary to build the whole LibreOffice?
Regards.
Building OpenOffice these days isn't SO difficult. Of course, you'd have to be prepared to spend some GBs and some bandwidth and some time building. Several gigs of storage, about 1 gig of downloads, several hours on a fairly modern desktop.
Not a negligible effort, yes. I also wouldn't mind seeing the result of a quick fix, well, quickly.
So I'll reformulate Baurzhan's question.
Assuming one has:
1) binary build versioned A.B.C installed,
2) the POT set known to be used to compile the translation for the A.B.C,
could one proceed like following, assuring the IDs remains fixed:
1) pull the strings' IDs from .res files of the installation,
2) (re)build the updated .res files from the updated POT/PO set?
It's possible to do such thing with binary editor, so why not with LibO standard/SDK/... toolset?
Yury
Hello,
I kinda solved this issue by making a nightly builds of LO 4.0,
at each build I pull zip file for my language from pootle with latest
translations,
and replace old translations.
Build takes ~8 Hours on my hardware
Cheers,
Well, yes, kinda, provided you can spare the cycles.
I'm somewhat surprised, though, that nobody else replied to that.
Yury
Yeah,
Actually a friend of mine provided a VPS to me,
I did like 20 builds until I succeeded.
In case if someone is interested, I can share RPMs for Fedora 18 64-bit;)
Cheers,