OpenOffice.org in Estonian

A cool posting about ribboned interface

2009-06-06T13:26:00.001+03:00

Yesterday I started to search user opinions about ribboned interface in new Autodesk products. As AD official forums are heavily censored and all negative opinions are cut off (censors are quite sloppy, in some places there are answers to these opinions left untouched), I started to search in independent channels and blogs. And I found a very cool and funny posting:

http://architechure.blogspot.com/2009/03/well-intentioned-road-paving.html

I think there is much to learn for UI redesigners.

Ribbons, ribbons, ribbons…

2009-06-05T23:41:00.002+03:00

I’d like to say some words too about this ribboned interface.

It’s OK for small applications like Windows Paint – all is visible and comfortable to handle
It’s not OK for big applications with thousands of commands like AutoCAD or Revit – all necessary is hidden, you have to make several moves to reach elementary tools and all this works painfully slowly. Both releases with number 2010 came with ribboned interface and it was really horrible. Fortunately in AutoCAD I could restore my layout from previous version, without ribbons, for Revit I still hadn’t time to mess with this, but it is not usable at all. In meantime I made my 3D sketches with Google Sketchup which still has normal interface – and this is pretty small application.

So where is the office application in this scale? Somewhere in the middle I think. And this ribboned interface for office is really a touch-and-go thing. When you want to play around with office, it may look amazing, when you need to do your work with office, I don’t know…

Windows 7

2009-05-19T23:05:00.004+03:00

Past week I decided to try Windows 7 RC which is free to use in one year period.

To keep it short - not bad. Faster than XP on the same computer, all drivers work, all needed applications too. Only my GenoPro2007 compatibility options needed some tuning (Disable visual themes, Disable desktop composition) but GenoPro is a piece of software with really bad quality anyways, unfortunately there isn't anything better.

OpenOffice.org 3.0.1 installation was successful, I used it 2-3 days until I got 3.1.0 installer. Upgrading was not so good any more. After removing old version installer said that it is impossible to write into OpenOffice.org3/program directory. I had to stop installation, remove manually OpenOffice.org3 directory and then resume installation. This time I had success.

Windows native open/save dialogs in OpenOffice.org look freaky and behave so too. No autocompletition, no suggested file names. This means, I have used that when I export myfile.odt to pdf, dialog suggests file name myfile.pdf. In this dialog does it not. When I open file file14.ods, save it as file15.ods and then export it to pdf, suggestion line was empty. I chose previous export, file14.pdf and changed 14 to 15. It was clarly written on the file name line file15. When I hit Enter, dialog told me that file14.pdf already exists... so had to write all the filename letter by letter to save it with name file15.pdf.

Following pictures illustrate:

- Windows native dialog in Windows 7 / OpenOffice.org

- Next picture is thes same native Windows 7 file open dialog opened from Notepad2 (very old but my favourite simple text redactor under Windows):

Makes a bit difference?

And Windows Wordpad now supports odt file format (you know, this strange piece of software that comes with Windows and which no one uses). Somehow. Strange ways the formatting artefacts were almost the same as in KWord... mostly some offsets and distortions of paragraph borders and paragraph background colors.

Btw, these screenshots are made with Windows native tool, called "Snipping Tool".

And the most important - when you copy a large amount of files with Windows Explorer and there occurs an error, you can now skip problematic file and proceed instead on starting again... Unbelievable that it took so many years to implement this.

Attention to community translators!

2008-02-15T19:46:00.006+02:00

(Edited 18.02) Today Pavel will generate new set of pot-files using translate-tools 1.1.0. This means that traslation teams, providing localized sdf-files for his build system should perform some additional moves.

Generate sdf-file from existsing translations (when you are not doing it everyday) using OLD TOOLKIT.
Backup all you have (when you keep your files in cvs it's not mandatory, you can easily rollback when something goes wrong).
Download and install the new toolkit from http://translate.sourceforge.net/wiki/toolkit/installation (as there were some issues with released 1.1.0, better download 1.1.1rcX from 18.02 or later)
You need additionally python-lxml package to work with new toolkit, setup doesnt give any messages about it but you cannot generate sdf-files when python-lxml is missing.
Regenerate your translation po-files (this is my command line, use your own paths and language codes) - attention - this will change duplicate styles from kde style to msgctxt:
oo2po -l et /home/ain/ooocvs/et/GSI_et.sdf /home/ain/ooocvs/et/po/ (you can get a warning about 'targetlanguage not found...', this means that you have a file with indicated name completely untranslated, when you agree, it's OK)
Download new pot-files from Pavel's ftp site (with date 15.02.2008 or later).
Merge translations with new pot files (pot2po).
Regenerate new sdf-file with (this is my command line, use your own paths and language codes):
po2oo -l et -t /home/ain/ooocvs/et/en-US.sdf /home/ain/ooocvs/et/po/ GSI_et.sdf
Run gsicheck. (Fixed in 1.1.1rc1 - You may encounter some errors which are caused by bogus whitespaces inside tags (was not problem before, because no tool had any idea that these double-escaped things are tags), for example by backconversion to sdf a tag "<ahelp >" is not recognized (space before closing angle), also tag"<ahelp hid..." (two adjacent spaces). These problems are created by translators using GUI tools because earlier gettext tools didn't know that this double escaped thing was a tag and put linebreak often inside of a tag, and it is very easy with gui tool put additional whitespace in end of such line (translator will not see line ending quotes). This problem should go with new toolkit.) When there are no errors go to 11.
Fix the errors and go back to 9.
Seems like you did it.

Attention: all these new pot files are generated only for OO.o 3.0 development tree. When you still want to provide translations for 2.4 tree (for your own use for example - or when you are distributing community builds), you should either have 2 versions of toolkits installed (eg. one in userspace, one systemwide) or you should convert 2.4 translations to new format too. Pavel told, he will not provide new pot files for 2.4 tree, as there should be no changes in this area any more.

broken readlicense in m234

2007-10-19T22:32:00.000+03:00

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!

2007-10-15T19:20:00.000+03:00

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

2007-10-12T23:59:00.000+03:00

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

2007-09-22T23:49:00.000+03:00

... 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

2007-09-22T23:38:00.000+03:00

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

2007-09-22T23:03:00.000+03:00

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!

2007-09-22T20:45:00.000+03:00

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

2007-08-31T22:25:00.000+03:00

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

2007-07-22T19:43:00.000+03:00

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

2007-04-28T18:54:00.000+03:00

A few changes, mostly in comments.

string changes in m210

2007-04-21T09:33:00.000+03:00

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

2007-04-11T14:24:00.000+03:00

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

2007-03-30T14:32:00.000+03:00

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)

2007-03-19T22:20:00.000+02:00

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

2007-01-16T20:54:00.000+02:00

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

2007-01-04T14:33:00.000+02:00

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

2007-01-04T14:25:00.000+02:00

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.

Changed strings in m191

2006-11-03T20:47:00.000+02:00

In m190 there were no changes. In m191 there are some strings in calc module, introducing the new behaviour of context menu for cells with notes. I'm sorry but still no possibility to show/hide notes for entire selection... http://qa.openoffice.org/issues/show_bug.cgi?id=64322

Changed strings in m189

2006-10-20T12:03:00.000+03:00

M189 has minimal new/changed strings in calc module, coming from R1C1 notation feature.

broken linebreaks from blogger-beta

2006-10-16T14:09:00.000+03:00

Strange, but the bug described in http://vagula.blogspot.com/2006/01/formatting-messages.html that was fixed in January 2006 in Planet OO.o, appears again after switching to blogger beta... Was interpretation fix dependent from site name or smthng like? When yes, maybe should also beta.blogger.com be included into whatever-it-is-or-maybe-not.

string updates in m187 and m188

2006-10-16T13:40:00.000+03:00

A lot of updates in helpcontent, mostly about PDF-export functonality and also Online Update. Some lesser changes in UI too.

Translating openSUSE

2006-10-10T22:27:00.000+03:00

As intermediate piece I decided to translate openSUSE base system into Estonian. Surprisingly beginning was very fast and simple, it took some hours to read a bit wiki and get access to svn repository. After 2 weeks hard work 62% from about 25K strings is translated, 70% is the limit for including into release and there are 10 days left until end of first cycle. Files from elder modules (most of YaST) are very easy to translate because strings have excellent comments. I just found this not fair that only distribution with GOOD estonian translation was Mandriva. And as I've used SUSE since 6.2 release, it is my personal shame that SUSE is still untranslated. :)

new strings in m181

2006-08-09T09:30:00.000+03:00

There are a lot of new strings in m181, mostly about Online Update: Added: et/po/extensions/source/update/check.po et/po/scp2/source/onlineupdate.po Modified: et/po/dbaccess/source/sdbtools/resource.po et/po/instsetoo_native/inc_openoffice/windows/msi_languages.po (*) et/po/officecfg/registry/data/org/openoffice/Office/UI.po et/po/sfx2/source/appl.po et/po/sw/source/ui/dialog.po (*) et/po/svx/source/dialog.po I removed bogus entries from list (caused by translate tookit weirdness), the files marked with * may be bogus too.

Changed strings in m179

2006-07-27T20:53:00.000+03:00

There are 3 changes: - one added string in both dbaccess/source/sdbtools/resource and fpicker/source/office - one removed string from svx/source/intro

changed strings in M178

2006-07-23T15:03:00.000+03:00

As deadline for UI freeze is passed, I'll start blogging again about new or changed strings. :) In m178 two files were affected: - from readlicense_oo/docs/readme the string 'Last updated...' is removed - in svx/source/options three strings are fixed (in Tools.Options dialog)

2006-05-10T22:32:00.000+03:00

Changed strings in m168

Two new strings in instset - about Thai language support. One string removed from svx/source/dialog.

2006-05-02T09:22:00.000+03:00

Annoyance in readme

"HERE is Edward Bear, coming downstairs now, bump, bump, bump, on the back of his head, behind Christopher Robin. It is, as far as he knows, the only way of coming downstairs, but sometimes he feels that there really is another way, if only he could stop bumping for a moment and think of it. And then he feels that perhaps there isn't."

... and the same way we every and every time update the strings in readme when there is no updates really, because of changed date-field which makes whole string new and "fuzzy".

Here it is: "Last updated $Date: 2006/04/28 12:21:31 $". Sometimes I feel that there really is another way for including a date...

2006-04-11T13:50:00.000+03:00

String changes in SRC_m163

First look was promising. Localize has generated a lot of new directories and files... all of them invalid. After Pavel has fixed this and uploaded new set of files, the output was more reasonable:

Modified:

- basctl/source/basicide.po

- dbaccess/source/ui/browser.po, misc.po
- filter/source/pdf.po
- framework/source/classes.po
- helpcontent2/source/text/scalc/01.po
- helpcontent2/source/text/shared/00.po, optionen.po
- helpcontent2/source/text/swriter/01.po, guide.po
- helpcontent2/source/text/shared.po
- officecfg/registry/data/org/openoffice/Office/UI.po
- sd/source/ui/app.po
- sfx2/source/appl.po
- svx/source/dialog.po, tbxctrls.po
- wizards/source/formwizard.po

Most of changes were about enchanchements in PDF-export and new update-checking functionality (and according helpcontent changes).

I found a funny sentence in update-checking help:

"This command is available for the full versions of OpenOffice.org, StarOffice and StarSuite only."

Interesting, do we have some limited version of OO.o? Correct were: "This command is available for OpenOffice.org and the full versions of StarOffice and StarSuite only."

String changes in m162

2006-03-30T21:00:00.000+03:00

Find in the following text module "helpcontent2" update. Didn't find? You are right. Added: /et/po/connectivity/source/resource.po Modified: /et/po/basic/source/classes.po /et/po/dbaccess/source/ui/dlg.po /et/po/desktop/source/app.po /et/po/officecfg/registry/data/org/openoffice/Office/UI.po /et/po/readlicense_oo/docs/readme.po /et/po/sc/source/ui/drawfunc.po, src.po /et/po/sd/source/core.po /et/po/sfx2/source/appl.po /et/po/sw/source/ui/app.po, dbui.po, fldui.po, shells.po /et/po/sw/sdi.po /et/po/svtools/source/dialogs.po, misc.po /et/po/svx/source/dialog.po, items.po /et/po/uui/source.po

String changes in m161

2006-03-24T10:36:00.000+02:00

There were 2 changes: - one string added in desktop/source/app - one string added in sc/source/ui/dbgui

String changes in m160

2006-03-17T19:59:00.000+02:00

A lot of changes, in the 23 files: filter/source/config/fragments/filters instsetoo_native/inc_openoffice/windows/msi_languages officecfg/registry/data/org/openoffice/Office/UI sw/source/ui/dialog, fldui svx/source/dialog helpcontent2/source/text/sbasic/shared/01, 02 helpcontent2/source/text/sbasic/shared helpcontent2/source/text/scalc/01, guide helpcontent2/source/text/shared/explorer/database helpcontent2/source/text/shared/01, 02, autopi, guide, optionen helpcontent2/source/text/simpress/01, guide helpcontent2/source/text/swriter/01, 02, guide helpcontent2/source/text/simpress, swriter

Test posting

2006-03-11T23:15:00.000+02:00

I just discovered the Drivel Journal Editor for blogging... Let's see how it works.

String changes in m159

2006-03-11T10:18:00.000+02:00

I'm a bit confuzed. After update there was only one fuzzy sting (famous Matrixes -> Matrices), but cvs log showed that 19 files were touched, 12 of these in helpcontent. Sure gettext does a lot of work automatically. I'll paste here a log of my cvs-commit, but this affects also many untouched strings. The reason is that about a year ago I turned off line breaking in POT2PO, but msgmerge applies this only in case, when pot file is changed (msgmerge thinks that removing linebreak in PO file is not a change). This means that changing one character in pot files applies also the --no-wrap option. This happens only once with every file, containing linebreaks in strings. Changes log: http://et.openoffice.org/servlets/ReadMsg?list=cvs&msgNo=1090 The process of update was not so smooth, like before, I'll cite Pavel's comment to [Issue 55666] helpex speed optimalizations?: "Thanks goes to Ain who find it by corrupting his local CVS repository by merging wrong POT generated from wrong GSI and all this five minutes before he wanted to go to bed :-)))"

String changes in SRC_m158

2006-03-02T23:15:00.000+02:00

Evolution/Groupwise addressbook support: - dbaccess/source/ui/misc - 2 strings added, 1 changed - extensions/source/abpilot - 2 strings added Other: - svx/source/dialog - tags changed for 2 strings, 4 strings removed

String changes in OOB680_m1

2006-02-13T16:24:00.000+02:00

In modules: - filter/source/xsltdialog : 1 changed comment (no string) - readlicense_oo/docs/readme: 1 string changed - svx/source/dialog : 1 string added - svx/source/intro : 1 string changed

Changed strings in SRC680_M156

2006-02-09T07:40:00.000+02:00

3 changed strings in module *wizard*.

String changes in SRC_m154

2006-01-30T20:09:00.000+02:00

One changed string in desktop/source/migration. (&PRODUCTNAME -> %PRODUCTNAME)

Success stories

2006-01-27T20:35:00.000+02:00

Ain V., white male heterosexual from NE Europe wrote: "Today I could log in into IssueZilla, edit issue and save changes. After this I got even e-mail about changes. Thank you for brilliant work."

Lets sing: "Will this still work to-mor-row..."

2006-01-27T00:29:00.000+02:00

... after this good old Doors' song: ..... Waiting for the sun Waiting, waiting, waiting, waiting, waiting, waiting, waiting, waiting Waiting for you to come along Waiting for you to hear my song Waiting for you to come along Waiting for you to tell me what went wrong This is the strangest life I've ever known [scream] .....

Changed strings in SRC680_M152

2006-01-23T21:39:00.000+02:00

There are some changes in module/file "filter .... xsltdialog" (changes in location comments). There is nothing to translate but .sdf needs update.

Kspread and OpenDocument

2006-01-22T19:29:00.000+02:00

According to koffice-devel list message Kspread now uses OpenDocument Spreadsheet as native file format.

testing updated planet

2006-01-21T20:23:00.000+02:00

Cool, seems like Planet is updated. I turned linebreaks in again, lets see, how it works. When there is no ">" in messages (excluding this), then its ok.

More about formatting

2006-01-19T21:13:00.000+02:00

Strange.
I looked at HTML-source of Eric's page and Pavel's page. Both of them use in original linebreaks in   format. Pavel's linebreaks are converted to  , Eric's linebreaks to  >?
I don't understand...

Formatting messages

2006-01-19T20:08:00.000+02:00

Attention to Blogger.com users, your posts may look a bit ugly. To fix this:
Go to Blogger dashboard and click "Change settings", then select "Settings - Formatting" tab and change field "Convert line breaks" to "No". Seems like planet.go-ooo does not understand break tags like " " (format that Blogger uses), when you want insert linebreak then write manually  .
(I'm not sure at all, that this message will be readable, let's see...)

Changed strings in SRC680_M151

2006-01-17T14:03:00.000+02:00

- in module sc (calc) - 3 strings (invalid descriptions of functions EVEN, ODD, RANK)
- in module officecfg - 5 x Fontwork Shape

Reporting bugs is not that easy

2006-01-16T14:24:00.000+02:00

Yesterday I suddenly remebered about KSpread bug (my comment 3), that prevents using xls-files in KOffice. So, lets check... Ah, still there. Ok, it's logical, when not reported than not fixed also. Hasso was about to write report, I needed sample files. As all non-ooo developers start whining, when sample files are created with oo.o (and to be sure, that it is not oo.o-s fault) I decided to produce xls-files with something else.
First: Gnumeric (sample file Book1.xls) - tried to write formula =A1*0,18 - impossible. (See bugreport). Finally switched to en_US, created file, result - my KSpread shows in formula cell parse error, Hasso's Kspread (latest snapshot) shows nothing, also in input field.
Second: Pocket Excel from my Smartphone. Thanks god, file creation was without problems (sample file Book2.xls), result - both my and Hasso's Kspread display empty cell instead of formula.
Conclusion: It is good to have OpenOffice.org Calc spreadsheet and be able to create and read 2-cell simple spreadsheet in my native locale (hm, at least under OpenSuSE, as others on other platforms could not reproduce behaviour of Gnumeric). ;)

More string changes before 2.0.2?

2006-01-14T10:48:00.000+02:00

I just remebered that fixing issues 53046 and 54231 will cause string changes in Calc, these issues are marked for 2.0.2 and are fixed in cws_dr43. This CWS is not yet merged. Maybe there are more such issues...

Friday, 13-th

2006-01-14T10:13:00.000+02:00

Now the Friday, 13-th is behind and nothing bad didn't happen, exept:
- my son's car engine cooler broke
- Estonian was not merged into 2.0.2 source, as downloading files from 'Documents and Files' section in OpenOffice.org website did not work (see http://www.openoffice.org/issues/show_bug.cgi?id=60458)
- all snow is gone :(

when something can go wrong, sure it goes...

2006-01-11T23:08:00.000+02:00

I'm just curious how many time more takes for me learning to read list messages till the very end.
Seems like I didn't notice that issues about merging translation into 2.0.2 must be assigned to Vladimir, filed as enchanchement etc.
Seems like in English there are too few words to be translation source language :). In Chart, there are chart titles and axes titles. Menu entry 'All Titles' is for both in general. But, in Estonian we cannot use the same word for axes titles and chart/legend/whatever titles. Maybe should I translate 'All Titles' like 'This and This'?
In Help index: spaces after semicolon are now truncated, so that column of first/second level keywords looks correct. But - space is truncated also in search term input line. When I select second level entry I see in input line something like this: 'illustrations;inserting'. I do not believe that not having space after semicolon is correct in any language.

2006-01-09T21:26:00.000+02:00

In SRC680_m149 Hunspell has finally replaced Myspell. This means a lot for many NL-teams, as now we have at least possibility to give our users spellchecking function, having reasonable quality. I'm glad too, that Estonian dictionary for Hunspell is now 'work-in-progress' and there are resources to finish it soon.

Updating translate-tools

2006-01-09T20:32:00.000+02:00

I don't want to paste all Pavel's blog entry here, only make one addition, how to migrate to latest translate-tools. At first, open the link above. Then read until words: "Create new (thus empty) temporary directory...". It's OK. When you have 100% translated, then proceed reading Pavel's blog. When not, then you should not unpack your gsi/sdf file, but create the new gsi/sdf file from old PO-s with new toolkit. (There is the difference. Old toolkit by default creates your language sdf-file so, that there is your-language-line even for untranslated entries, where untranslated string is replaced with English one. When you create po-s from half-translated sdf-file, created with old toolkit, you will have 100% translated strings, but a lot of them in English.) Next steps are OK. One suggestion more: - when you use prewritten scripts for generating po or sdf-files, don't forget to change PYTHONPATH to location, where translate-tools are installed now. This is one reason, I have started this blog at all... I migrated in september 2005 to new toolkit, and of course I did not remember anything, when Pavel asked me to proofread his blog entry (link above)...

Starting...

2006-01-09T20:06:00.000+02:00

As there are many things I must repeat every day several times, I'm trying to put these together and publish here. Maybe it helps a bit to save time.