Pavel's diary

People from l10n project are working on producing testing PO files for 2.0 translations.

Ivo is working on updating transex3 project in ivo05 child workspace, I extracted GSI files for several languages and David generated testing PO files from them.

So far, it looks quite OK. Of course there are still several issues but mainly cosmetic ones.

PO files are structured in directory structure similar to the original source code structure, but they contain comments (references) that are redundant (because of parent directory names).

Current approach is problematic for long continuous texts like README files, because it doesn't keep the order of text in the original files. Translating such mis-ordered stuff is quite problematic because you do not see context. -----

Milestone SRX645_m48 was announced (with dr24, unopp4bugs01 and schoasis integrated), OpenOffice.org Newsletter 09/2004 published, Engineering Steering Committee announced and last (but not least) reals appeared back on IRC. -----

I updated my build system so it can extract GSI/SDF files also for 680/1.9.x/2.0 branch. First testing files are available here.

Please have a look at them and report your findings to dev@l10n. -----

Dan Ohnesorg prepared photo-report from our trip to Berlin to visit OOoCon2004. Comments are in Czech, but photos and multi-language ;-)

Photos include pictures of Berlin (from car), Erwin Schrödinger-Zentrum, 1st day, 2nd day, 3rd day. -----

64bit porting is now in svtools project:

Making: ../../unxlngx4.pro/slo/parhtml.obj
/home/pavel/BuildDir/ccache /usr/bin/g++ -fmessage-length=0 -c -I. -I. -I../inc -I../../inc -I../../unx/inc -I../../unxlngx4.pro/inc -I. -I/home/pavel/BuildDir/ooo_cws_src680_ooo64bit02_src/solver/680/unxlngx4.pro/inc/stl -I/home/pavel/BuildDir/ooo_cws_src680_ooo64bit02_src/solver/680/unxlngx4.pro/inc/external -I/home/pavel/BuildDir/ooo_cws_src680_ooo64bit02_src/solver/680/unxlngx4.pro/inc -I/home/pavel/BuildDir/ooo_cws_src680_ooo64bit02_src/solenv/unxlngx4/inc -I/home/pavel/BuildDir/ooo_cws_src680_ooo64bit02_src/solenv/inc -I/home/pavel/BuildDir/ooo_cws_src680_ooo64bit02_src/res -I/home/pavel/BuildDir/ooo_cws_src680_ooo64bit02_src/solver/680/unxlngx4.pro/inc/stl -I/home/pavel/BuildDir/ooo_cws_src680_ooo64bit02_src/solenv/inc/Xp31 -I/opt/java/include -I/opt/java/include/linux -I/opt/java/include/native_threads/include -I/usr/X11R6/include -I. -I../../res -I. -O0 -fno-strict-aliasing -pipe -fno-for-scope -fpermissive -fno-use-cxa-atexit -include preinclude.h -fno-exceptions -fPIC -DLINUX -DUNX -DVCL -DGCC -DC300 -DX86_64 -DGXX_INCLUDE_PATH=/usr/include/g++ -DCVER=C300 -D_USE_NAMESPACE -DGLIBC=2 -DX86_64 -D_PTHREADS -D_REENTRANT -DNEW_SOLAR -D_USE_NAMESPACE=1 -DSTLPORT_VERSION=400 -D__DMAKE -DUNIX -DCPPU_ENV=gcc3 -DSUPD=680 -DPRODUCT -DNDEBUG -DPRODUCT_FULL -DOSL_DEBUG_LEVEL=0 -DOPTIMIZE -DEXCEPTIONS_OFF -DCUI -DSOLAR_JAVA -DSRC680 -DUPD=\"680\" -DMINOR=\"m45\" -DBUILD_ID=\"8790\" -DSHAREDLIB -D_DLL_ -DMULTITHREAD -w -o ../../unxlngx4.pro/slo/parhtml.o /home/pavel/BuildDir/ooo_cws_src680_ooo64bit02_src/svtools/source/svhtml/parhtml.cxx
/home/pavel/BuildDir/ooo_cws_src680_ooo64bit02_src/svtools/source/svhtml/parhtml.cxx:195: error: prototype for `ULONG HTMLOption::GetNumber() const' does not match any in class `HTMLOption'
../../inc/parhtml.hxx:162: error: candidate is: sal_uInt32 HTMLOption::GetNumber() const
/home/pavel/BuildDir/ooo_cws_src680_ooo64bit02_src/svtools/source/svhtml/parhtml.cxx:195: error: `ULONG HTMLOption::GetNumber() const' and `sal_uInt32 HTMLOption::GetNumber() const' cannot be overloaded
/home/pavel/BuildDir/ooo_cws_src680_ooo64bit02_src/svtools/source/svhtml/parhtml.cxx: In member function `void HTMLOption::GetNumbers(SvULongs&, unsigned char) const':
/home/pavel/BuildDir/ooo_cws_src680_ooo64bit02_src/svtools/source/svhtml/parhtml.cxx:264: error: call of overloaded `Insert(unsigned int, USHORT)' is ambiguous
../../inc/svstdarr.hxx:98: error: candidates are: void SvULongs::Insert(const SvULongs*, short unsigned int, short unsigned int, short unsigned int)
../../inc/svstdarr.hxx:98: error: void SvULongs::Insert(const ULONG&, short unsigned int)
dmake: Error code 1, while making '../../unxlngx4.pro/slo/parhtml.obj'
---* TG_SLO.MK *---

ERROR: Error 65280 occurred while making /home/pavel/BuildDir/ooo_cws_src680_ooo64bit02_src/svtools/source/svhtml
dmake: Error code 1, while making 'build_all'
---* TG_SLO.MK *---

I wonder who invented the name SvULongs. -----

I have just finished migration from licq and xchat to Gaim 1.0.0. Should you have any problems with contacting me, please use other communication means you know ;-)

I wonder why I also had to hit issue 1030896 (Gaim crashes when opening preferences dialog). -----

I agree with Eike ;-). (On the other hand, having Ilsa John as a host have had several advantages, one of them being unbelievably delicious dinners in the evenings ;-)

And yes, OOoCon2004 was a huge success! -----

I hope to meet you in Berlin. It is unbelievable hard to prepare everything before I leave.

I've finished with reading the schedule. There are times when I need to have two brothers to visit everything I want to.

I'll be in Prague tomorrow and am leaving for Berlin tomorrow afternoon. -----

Another interesting news about 2.0 (1.9.54 currently) is Mozilla/Netscape plugin. As this will be highly valuated feature, please test it carefully and report issue to IssueZilla. -----

Many people wonder what does it mean when you say: "It is fixed in pj02." or similar magic. OpenOffice.org projects uses so called child workspaces for implementing fixes or new features to the source code. Child workspace isolates the changes needed to fix issues.

EIS (Environment Information System) helps you (and also developers) to navigate through the world of child workspaces.

On the main page, click on "Child workspaces" and "Search". In this form, just enter the name of the child workspace you are looking for and press "Find" or press the key Enter on your keyboard. You'll see detailed informations about the child workspace, issues fixed in this child workspace, modules in this workspace etc. -----

Extras module of OpenOffice.org contains several different directories that are relevant for localizers. In this entry, I'm going to describe how files in the directory palettes works, where they are used etc. in upcoming OpenOffice.org 2.0.

The directory extras/source/palettes contains files with different extensions:

• sob - Bitmaps
• soc - Colors (palettes)
• sod - Line styles
• soe - Arrow styles
• sog - Gradients
• soh - Hatching

Where to find them all in GUI? As you probably know, I'm very bad user of OpenOffice.org so I had to ask Tom Verbeek, extras maintainer, for help. He provided very good description.

Start OpenOffice.org Draw and create new drawing. Now draw a line (e.g. with arrow on one side) and a rectangle like on the following image. The line is solid, with simple arrow. The rectangle is filed with "Blue 7" color (the default).

Now imagine you want to change properties/look of the rectangle. Press right button on it, and click on Area first and select Colors tab. You'll see the following dialog (click on the image to see large version).



You can see the "Load Color List" icon there. By using this icon, you can load Colors defined in files with extension soc.

There are Gradients, Hatching and Bitmaps tabs on this dialog where you can load gradient styles (with the extension .sog), hatching styles (with the extension .soh) or bitmaps (with the extension .sob).

Press Escape several times to get back to the drawing and press right button on the line and select Line. You'll see another dialog with several tabs:



In the tab Line Styles you can select the style of the line and also open Line styles stored in a file with extension sod. In the tab Arrow Styles you can select the style of arrows and also open Arrow styles stored in a file with extension soe.

Now you know how to use these files, but what about their internal structure and location in OpenOffice.org source code and installed product?

The source code directory extras/source/palettes has the following structure: it contains files standard.so? where ? stands for letters b, c, d, e, g or h and also other files (like web.soc or html.soc) and directory lang. Common files are not to be translated. So only lang directory is interesting for localizers. It contains directories named according to ISO codes (see the table of supported languages) with additional files. If you plan to create localized version, you have to translate (or at least copy) the directory en-US. E.g. I had to copy and translate files in en-US directory to the directory cs (see child workspace pj05 and issue #i34312#).

When you install e.g. English version of the latest milestone (SRC680_m54 right now), all of these files are in your .../user/config directory.

And now some words about the structure of every file type.

• sob file contains bitmaps. The file is ZIPed with classic ZIP/JAR and contains office:bitmap-table XML element and several images.
• soc file contains colors in office:color-table XML element with their definitions inside draw:color elements. It is in UTF-8 and you have to translate the names of colors in draw:name.
• sod file contains line styles in office:dash-table XML element with their definitions inside draw:stroke-dash elements. It is in UTF-8 and you have to translate the names of line styles.
• soe file contains arrow styles in office:marker-table XML element with their definitions inside draw:marker elements. It is in UTF-8 and you have to translate the names of arrow styles.
• sog file contains gradient styles in office:gradient-table XML element with their definitions inside draw:gradient elements. It is in UTF-8 and you have to translate the names of gradient styles.
• soh file contains hatching styles in office:hatch-table XML element with their definitions inside draw:hatch elements. It is in UTF-8 and you have to translate the names of hatching styles.

You can also rename files copied from en-US directory to help users understand the contents of files (e.g. hatching.soh is very strange for Czech people, but srafovani.soh is quite ok).

And this is all. Hopefully this will help you to localize even small details like this one. -----

SRC680_m54 has been built by Hamburg RE. Child Workspaces integrated include tablebutton, dr20, vcl25, swundo03, oasissysint, pj01, svg02, i18n14, encodingfix, sardinian, dr12, insight02, desktintgr02, opendocbehavior, toolbars2, qwizards2, improveforms, getfilesize1, ooo20040704, gtkfpicker1, iha02, enhselect, dba15, kurdish, ab10fixes, vq01, vcl26, ooo20040815, customizer, swqbugfixes06, impress11, pdf01, filteredcells, lookup.

I have already finished building it and uploaded my builds (English and Czech) at ftp.linux.cz

There are several issues we identified:

• The most important issue is that on GNU/Linux, you have to remove -fno-rtti from solenv/inc/unxlngi4.mk to get OpenOffice.org running at all.
• #i32963# - the RPM packages contain %post scripts that do something useful only when the package is installed to /opt/openoffice/1.9.54. There is a workaround for this in the issue.
• Modules vcl and crashrep use module gtk which for StarOffice only, thus string gtk has to be prefixed by SO: in prj/build.lst. vcl is fixed in ause011, crashrep is fixed in pj04.
• #i32398# - repeated builds in libxml2 result in a build failure. This is fixed in child workspace pj02.
• #i33481# - this issue is multi-project. Several files are affected: autodoc/source/ary/inc/nametreenode.hxx, autodoc/source/ary/store/t_storg.hxx, stoc/source/security/lru_cache.h, ucb/source/inc/regexpmap.tpt. The typename was brought in by gcc34 changes but these changes broke .NET2002 compiler on Windows. We probably need to invent a mechanism to overcome this bug, because we want both .NET2002 and .NET2003 to be supported compilers.
• #i33509# - nsplugin uses gtk/gtk.h include file, but doesn't add proper include paths in CFLAGS.
• #i33458# - repeated builds in scripting/java fails on Windows. Temporary fix is in the issue - simply remove clean target from dependencies. Scripting project has several other minor/non-build issues (#i33504#).
• #i33528# - sc/source/core/data/compressedarray.cxx compilation failure.

-----

You are looking for OpenOffice.org people? You can find a list of them at Ximian@Novell site. Many of them hang on IRC channel #openoffice.org on Freenode.net. Join us there. -----

I updated ccache in my build system to version 2.4. ccache is "compiler cache" and saves me about three fourths of time needed to produce binary installation sets of OpenOffice.org. -----

According to yesterday's MF Dnes newspaper, Vladimář Mlynář (Czech Ministry of Informatics) want Czech post to stay in the form of state-owned company in the future. -----

Build-14 is being mirrored to ftp.linux.cz (Windows builds are complete now, GNU/Linux and Solaris builds are work in progress). This build uses the same source code as OpenOffice.org 1.1.3 RC1 will use. This means it is based on milestone SRX645_m47 with child workspaces jloo113 and defsymcvt integrated.

Please test it and report results. -----

Bash Blogger (appeared on Freshmeat last week) is another shell only blog engine (my diary/blog is running on Nanoblogger). -----

SRX645_m47 contains fixes for the issue #i33983# I reported, thus I extracted GSI/SDF files and README files again for you. -----

I again decided to take a long weekend away from home and have spent it in Brno with my parents. The only drawback of visiting Brno is that I do not have fast connectivity there (I still use GPRS and am waiting for either ET to offer different CDMA modem or Tmobile to offer EDGE for better price than ET's CDMA ;-).

So when I came back, I was delighted. So many interesting news in OpenOffice.org world. Let's summarize them.

Two milestones are ready now - SRC680_m53 (child workspaces integrated: cfglogging, help2, referr, fontlists03, xmlsec05) and SRX645_m47 (ooo113l10nfix was integrated).

Joerg Budischewski plans to update Python in OpenOffice.org to 2.2.2 to 2.3.4.

Louis is asking for ideas about his presentation "State of the project year 4".

According to Jacqueline McNally, Sander Vesik is moving to Estonia. (Jacqueline: yes, it is also important that he will be marketing contact there ;-). -----

I have extracted GSI files and README files from SRX645_m46. This milestone will be the base for OpenOffice.org 1.1.3 release.

Please check your files and report results to IZ. It seems that there were problems during the merge, because many strings have bad encoding. I reported this as issue #i33983#. -----

This milestone will be the base for 1.1.3 release. The following child workspaces were integrated: vclppbugs3, vclppbugs4, vclppbugs5, ooo113localedata, ooo113fix2 and ooo113l10n. I'm away from home now and will be back on Sunday evening, so I can't test it. Please test it and report results so we can have 1.1.4 sooner and better.

Right now, he still have several issues to be solved/re-target before 1.1.3 is released. -----

Community child workspace ooo20040815 has been nominated so our build fixes will be soon integrated into HEAD. -----