Make Guarani available

l10n
#1

Hello

I have sent an email before asking the Guarani pack to be able to download.

They told me they were going to change the local code on pootle from Gn to
Gug but never got done.

I have reached 33% now, and have completed the sw, sd, sc (uiconfig)
folders and have done some work on other folders.

I would like to know if there's anything I can do to make the pack
available.

-Gio

#2

Hi :slight_smile:
Sorry you had no replies over the weekend! I gather people were busy as
there are a couple of massive tradeshows and other events coming up soon.

Hopefully someone will be able to help you get this sorted out fairly
soon!
Good luck and regards from
Tom :slight_smile:

#3

Still no replies

Can anyone help me?

#4

Hi Giovani,
Sorry for the delay, Cloph have been swamped by the infra problems, but we
discussed it during our team meeting and we find 30% a bit short to have a
regular build and he also have to change the local. Do you need a build to
check your localization?
Cheers
Sophie

#5

Hi Giovanni,

I have sent an email before asking the Guarani pack to be able to
download.

They told me they were going to change the local code on pootle from Gn to
Gug but never got done.

Who told you that? I asked Cloph to change gn to gug, but he is rather busy.

I have reached 33% now, and have completed the sw, sd, sc (uiconfig)
folders and have done some work on other folders.

I would like to know if there's anything I can do to make the pack
available.

Guarani is targetted for LibreOffice 4.5. First language packs will be
available from TDF with 4.5 betas. See the release plan.
http://wiki.documentfoundation.org/ReleasePlan

However, you can always build LibreOffice yourself from source code,
see https://wiki.documentfoundation.org/Development
We can help you, if you get stuck.

Best regards,
Andras

#6

Hi,
Just wondering: why do we need to change the locale code?

Rimas

#7

Hello,

Ive been trying to build libreoffice for the past two days but I'm getting
stuck

ive used

./autogen.sh --with-lang=gug (just like Andras mention in a previous email)
make && make dev-install && exit

and thisis where im getting suck

test@test-VirtualBox:~/core$ make && make dev-install && exit
mkdir -p /home/test/core/instdir
/home/test/core/solenv/bin/install-gdb-printers -a /home/test/core/instdir
-c
make -j 1 -rs -f /home/test/core/Makefile.gbuild all
[build DEP] LNK:Library/libsvxcorelo.so
[build LNK] Library/libsvxcorelo.so
/home/test/core/workdir/CxxObject/svx/source/sdr/contact/viewcontactofsdrpathobj.o:
file not recognized: File truncated
collect2: error: ld returned 1 exit status
make[1]: *** [/home/test/core/instdir/program/libsvxcorelo.so] Error 1
make: *** [build] Error 2

Also, I apologize if this is not the right mailist for devs.

-Gio

#8

Hi,

Hello,

Ive been trying to build libreoffice for the past two days but I'm getting
stuck

ive used

./autogen.sh --with-lang=gug (just like Andras mention in a previous email)
make && make dev-install && exit

You don't have to use "&& make dev-install && exit". Single "make"
will do. LibreOffice can be started as instdir/program/soffice

and thisis where im getting suck

[build LNK] Library/libsvxcorelo.so
/home/test/core/workdir/CxxObject/svx/source/sdr/contact/viewcontactofsdrpathobj.o:
file not recognized: File truncated

Please check, if your disk is full. If not, do a "make svx.clean",
then "make" again. It can be a random temporary problem.

Regards,
Andras

#9

Thanks, that seemed to work

#10

Thanks Tom, it seems you're right: gn is considered a macrolanguage:
http://www-01.sil.org/iso639-3/documentation.asp?id=grn .

Regards,
Rimas

2015.02.20 16:40, Tom Davies rašė:

#11

Hello again.

Quick question about the 'Master' build.

Does the master build gets updated everytime i work on pootle or does it
have to be updated manually?

Last time it was added to master when it was only 15% completed.

I just finished building and I'm pretty happy the way its looking. I have
completed writer/presentation/draw (have corrected some errors too) and
just about to finish calc now .

I was the guarani master could be update until today if possible.

PS: Thanks Andras for all the help

-Gio

#12

Hi Giovanni,

Hello again.

Quick question about the 'Master' build.

Does the master build gets updated everytime i work on pootle or does it
have to be updated manually?

You have to update it manually. You can download po files in a zip
from Pootle, and unzip them in translations/.

Last time it was added to master when it was only 15% completed.

Last time I added it, also manually. Just to see, if it works.

Keep up the good work. :slight_smile:

Best regards,
Andras

#13

I just downloaded the po zip and extracted to /core/translations/

When i go to language settings and choose Guarani it still gives me the old
translation.

I can't really figure out how to apply the new one.

#14

Make sure, that you overwrite old 'gug' files, and don't forget to
rebuild LibreOffice.

Regards,
Andras

#15

Sorry for the amateur questions, i'm not really a developer.

I just went back and ran

cd core
./autogen.sh with-lang=gug
make
(files already on translations folder)

But it didn't seem to do the trick.

I was wondering if you could guide me how to do it.

Again, sorry

-Gio

#16

Sorry for the amateur questions, i'm not really a developer.

I just went back and ran

cd core
./autogen.sh with-lang=gug
make
(files already on translations folder)

But it didn't seem to do the trick.

I was wondering if you could guide me how to do it.

Again, sorry

-Gio

#17

Maybe dependencies are not set correctly, I don't know... I've never
built LibreOffice like this myself. When you ran make, did you see
your language dependent targets (RES, XCU, UI, etc.) rebuilt? If it's
a dependency problem, then you can always 'make clean' things, and
then make again. Maybe it's an overkill to issue a toplevel make
clean, and rebuild everything from scratch. For example, if you want
to rebuild sw onyl, then 'make sw.clean && make sw' will do the trick.

Best regards,
Andras

#18

Hello again,

I've tried just about everything.

I tried building from scratch again and unziping the Pootle files on the
'translations' folder before the build. That didn't work.
I tried make clean && make and that didn't work either.
I tried 'make translations' and it build one POT file but didn't make any
effect.
So far it only looks like my first build back when I was at 15% (on pootle).

I am getting two errors but I'm not sure if it has anything to do with the
translation

I don't know what it could be.

*File tested,Execution Time
(ms)msobrightnesscontrast.docx,/home/test/core/sw/qa/extras/ooxmlimport/ooxmlimport.cxx:2213:testMsoBrightnessContrast::Importequality
assertion failed- Expected: 56374- Actual : 74306File tested,Execution
Time
(ms)picture-with-schemecolor.docx,/home/test/core/sw/qa/extras/ooxmlimport/ooxmlimport.cxx:1989:testPictureWithSchemeColor::Importequality
assertion failed- Expected: �- Actual : File tested,Execution Time
(ms)math-malformed_xml.docx,33*

*ooxmlimport.cxx:2213:AssertionTest name:
testMsoBrightnessContrast::Importequality assertion failed- Expected:
56374- Actual : 74306ooxmlimport.cxx:1989:AssertionTest name:
testPictureWithSchemeColor::Importequality assertion failed- Expected: �-
Actual : Failures !!!Run: 173 Failure total: 2 Failures: 2 Errors: 0*

*Error: a unit test failed, please do one of:export
DEBUGCPPUNIT=TRUE # for exception catchingexport
CPPUNITTRACE="gdb --args" # for interactive debugging on Linuxexport
VALGRIND=memcheck # for memory checkingand retry using: make
CppunitTest_sw_ooxmlimport/home/test/core/solenv/gbuild/CppunitTest.mk:81:
recipe for target '/home/test/core/workdir/CppunitTest/sw_ooxmlimport.test'
failedmake[1]: ***
[/home/test/core/workdir/CppunitTest/sw_ooxmlimport.test] Error
1Makefile:243: recipe for target 'build' failedmake: *** [build] Error 2*

#19

Hi :slight_smile:
I think the questions are interesting. It is stuff that i have never had
to deal with. I think the English Documentation team would "be completely
at sea" if they had to do any of this.

Would a fairly simple script help at all or is it about as
straight-forwards as reasonably possible? Would a script just create more
problems in dealing with this sort of thing? Of course one advantage of
not using a script is that there are other places to seek help and also if
people learn this from here then they can apply that knowledge elsewhere
too.

Hmmm, i guess i am not hugely in favour of a script after-all unless it is
likely to be simple to write and likely to improve things.
Regards from
Tom :slight_smile:

#20

I managed to get it to work. I just end up deleted everything and started
fresh.

Sorry for the inconvenience.

-Gio