broken readlicense in m234

As readlicense module's translatable content is a bit broken, Pavel removed m234 pot-tarball from his directory. It was not usable anyways, due po2oo and gsicheck errors. See issue 82771

Happy Birthday, OO.o!

After I've read about 7th birthday of OO.o, I started to dig mailing list archives to find out how old is Estonian translation of OO.o. Looks like we started translation project in 6th October 2001 (mailing list was created and started work with localedata). So we had a quiet 6th birthday without precious presents about one week ago. Using archives, I wrote a short localization chronology, unfortunately in Estonian... :)

new strings in m233

New module was introduced, sdext. The path to translatable files is at least 3 inches longer than in any existing module: sdext/source/minimizer/registry/data/org/openoffice/Office. There is something more too long, because GSICHECK gives an error checking this module:

• Error: Line format, Line 32589, UniqueID
  sdext/source\minimizer\registry\data\org\openoffice\Office\Addons.xcu/value/.Addons.AddonUI.OfficeMenuBarMerging.org.openoffice.Office.SunPresentationMinimizer.org.openoffice.Office.SunPresentationMinimizerCommand1.MenuItems.org.openoffice.Office.SunPresentationMinimizerExecute2/Title//:
  GID and LID may only be 125 chars long each!  "en-US"

• Error: Line format, Line 32591, UniqueID
  sdext/source\minimizer\registry\data\org\openoffice\Office\Addons.xcu/value/.Addons.AddonUI.OfficeMenuBarMerging.org.openoffice.Office.SunPresentationMinimizer.org.openoffice.Office.SunPresentationMinimizerCommand2.MenuItems.org.openoffice.Office.SunPresentationMinimizerAbout1/Title//:
  GID and LID may only be 125 chars long each!  "en-US"

Filed as http://www.openoffice.org/issues/show_bug.cgi?id=82571

My opinion about different options when translating OO.o

... is following:

• Some people translate sdf-files with spreadsheet applications... brr..
• Translation framework held up by Pavel Janik: it was the way to involve existing freeware translators to OO.o translation. It was very important to use their TM databases at starting point for many languages. As it is easy to use and quite flexible it is at moment a very good way for communities sharing translators with other teams.
• Pootle - it is the best way to involve EVERYONE. Some teams don't want everyone. Me too. OO.o is a production level application already long time, there are printed books about OO.o in many languages, we should think twice before changing something in user interface. It needs strong administration etc. Anyways, it is a very good option too in many cases and the best feature is that Pootle can be used together with previous option.
• Something for professional translators. I don't maybe fully understand what all this XLIFF etc. means, but I can understand that this may be important for so-said Sun-languages. I've never met any professional translator of my language personally, I've only seen some MSW and MSO translations and these make me sick (not only me, users too - these translations are subject of common fleering in our country). It is still for me unclear, how version control systems can handle XLIFF-format, as OLT output is packed to xlz-files and how readable is the changes output. Anyways, for my team this option is meaningless, as we don't have currently any people working with other formats except gettext one.

It's just my thoughts, I don't want to agitate someone. Maybe just we have to think not only 'what will be in future' but also 'what we have already'. And how to make it better.

Checking translations

We are checking all changes in string translations in very easy way: our Estoanian team linguist (Marek Laane, JCA) is subscribed to et-cvs@openoffice.org mailing lists. When a commit is made he just writes his comments to the same list. We are using the same system in all projects, for projects without needed infrastructure (Firefox, Thunderbird) we use Google Groups with or without RSS feature for redirecting version-control-system commit messages, for projects with common mailing list for all changes (like openSUSE) I first automatically filter out et/po messages using my GMail account which deletes all other languages commits and redirects et/po commits to Google group. It's very easy to do because diffs of po-files are easy readable.

Some pickups from NLC meeting in Barcelona

I've reminded later that Basque team lead told that he has to overread every incoming file from translators from beginning till the end (if I understood right). I've tried to keep it simpler - when I've got the file, I'm doing following:

• remerge it to latest pot-set just to be sure
• take a look at statistics to find fuzzy and untranslated strings and fix them if I can
• commit to CVS repository
• read commit log to see what is changed
• fix the errors when needed
• commit again when needed

When I've got file from trusted people (hm, I trust generally all people, but lets say ... trusted quality) I'll skip the last 3 steps or I'll write it in my ToDo. It's easy to do because diffs of po-files are easy readable.

Barcelona!

17.09 Leaving home in 7.30 at morning. Driving 3 hours (horas). In Tallinn's airport at 10.30. Check-in, quick lunch, to plane... bzzzzzz ... 15.45 - in Barcelona. Heat! +28 degrees. And we all have clothes as we left home at +2 degrees we should bury the earlier decision to get to city with train. Thanks to taxi driver with license to 4 places who takes us all 5 people with a lot of baggage into center of city. 30 minutes driving and here we are - in the middle of the historical Barcelona. Our ho(s)tel is placed at street Jaume I, 50 meters from the Plaza of Saint Jaume. The 3rd floor is 5th floor in reality when starting measuring from earth but OK. There is a TV, shower and toilet (seat is a bit broken but dontmind). Quick walk to Cathedral's plaza, dinner etc. Greatest experience was Sangria de Cava which was really good in such heat. Back to hotel, and to sleep. Realized that its not possible to sleep with open balcony door - bells at every 15 minutes, street musicians, and rolling beer-wine-whatever barrels in early morning/late night. 18.09 First thing in morning - to Aquarium. Sharks, corals, Linux penguins etc. Quick lunch, starting to search for university. Found in 30 minutes, another 5 minutes to find the room where NLC meeting takes place. Took some pictures from old university which is itself worth of visiting Barcelona. Meeting started at 15 PM as should be. Most things talked were already discussed during last year at IRC meetings. Pootle, XLIFF, QA process, etc. I'm not a big fan of first 2 ones, but I started to think, that when I'm where I am - at 10% untranslated helpcontent2 - then maybe Pootle is really a good option to give access to everyone to these parts of Help that I'm not able to translate myself. I still do not understand how to get human-readable commit logs using XLIFF format, as reading of commit logs is the mother of wisdom. Important thing I learned - it was how to pronounce word 'GNOME'. Interesting, do local Gnome translators know it? Back to hotel, learned to use Barcelona's metro, then to Sagrada Familia to see it highlighted in night. 19.09 Woke up early, to Zoo. Met my grandfather and other relatives. Then tried to swim in sea at Barceloneta. There was although no need to swim. It was enough to stay in 20-cm-water and wait for next big wave. In evening back to Sagrada Familia to see it from inside and visit the museum. Biggest experience was the hanging model made by Gaudi for structural analysis. Simple conclusion - when there is no computer, you have to build one. 20.09 In 9 AM from Plaza Catalunya straight to Montserrat monastery, afterwards to Freixenet cava industry. Was a great trip, thanks to our guide Adrian who also took a picture from me and my family! In the late evening to see Magic Fountain of Mountjuic. 21.09 Starting to pack. Then to stores to buy souvenirs, dinner, taxi, airport, 4 hours flight, at 23 PM back in Tallinn. Waiting for luggage whole hour, searching a) where I left my car b) where I left my parking ticket. In 3.00 at night back in home. Resume: There are many dogs in streets of Barcelona, but I've seen only two cats. Apparently dogs are destroyed all cats. I find it great. I have a foxterrier at home and we share some attitudes about a lot of things.

Changed strings in OOG_m3

about 15 changes in scp2/source/ooo (language names and related strings) and one error fix in chart2/source/controller/dialogs

string changes in m222

As string freeze were long time ago I start again write about latest changes: - in m222 are three new strings in framework/source/classes/resource.src ...

string changes in m211

A few changes, mostly in comments.

string changes in m210

There are 14 pot-files added, some are relevant, some not. See also issue 76550 and issue 76551. More than 20 existing po-files are touched too, mostly comment changes. You need to fix fuzzy strings to see main menu labels translated in next build.

String changes in SRC_m208

One string is added in sw module and two added and one changed in svx module. A lot of fixes and changes in most helpcontent2 subdirectories (some hundreds).

String changes in SRC_m207

There are 5 changed UI strings in 3 different modules (filter/source/, sfx2/source/, svx/source/) in m207.

String changes in devel branch (post 2.2)

• m199 - many changes, new module for language names (with a lot of errors fixed in m204)
• m200 - one string removed
• m201 - looks like I've missed this...
• m202 - one string changed, two removed
• m203 - many changes in Help strings (some hundreds...)
• m204 - language names in instsetoo_native/inc_openoffice/windows/msi_languages, scp2/source/ooo
• m205 - no changes
• m206 - no changes

additional strings for 2.2

As mentioned at Release Meeting, there are some last-minute-strings to translate (24 phrases in svx/source/dialog). Pavel has uploaded new pot file for m199, containing these strings. Warm winter in Europe doesn't let UI strings freeze.

changed strings in m199

Exactly two weeeks before translation deadline we have a lot of changed UI strings in upcoming m199 (about 150 as far I counted). Mostly these are about interface for selecting default language(s) of extensions. Strange only, that now we have already 3 identical sets of these language name strings in different modules...

Windows Hen

Despite all checks MS made when choosing name 'Vista' they missed Latvian language. In Latvian 'Vista' means 'hen'. Looks like Latvians have good ground to check all incoming copies of Vista against salmonella-virus and maybe even apply additional taxes to price of Vista as this may be a food product coming from non-EU country.