String changes in SRC_m154

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

Success stories

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

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

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

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

testing updated planet

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

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

Formatting messages

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 "<br />" (format that Blogger uses), when you want insert linebreak then write manually <br>.
(I'm not sure at all, that this message will be readable, let's see...)

Changed strings in SRC680_M151

- 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

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?

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

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

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.

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

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

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.