Friday, November 03, 2006

Changed strings in m191

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

Friday, October 20, 2006

Changed strings in m189

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

Monday, October 16, 2006

broken linebreaks from blogger-beta

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

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

Tuesday, October 10, 2006

Translating openSUSE

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

Wednesday, August 09, 2006

new strings in m181

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.

Thursday, July 27, 2006

Changed strings in m179

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

Sunday, July 23, 2006

changed strings in M178

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)

Wednesday, May 10, 2006

Changed strings in m168

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

Tuesday, May 02, 2006

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

Tuesday, April 11, 2006

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

Thursday, March 30, 2006

String changes in m162

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

Friday, March 24, 2006

String changes in m161

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

Friday, March 17, 2006

String changes in m160

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

Saturday, March 11, 2006

Test posting

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

String changes in m159

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 :-)))"

Thursday, March 02, 2006

String changes in SRC_m158

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

Monday, February 13, 2006

String changes in OOB680_m1

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

Thursday, February 09, 2006

Changed strings in SRC680_M156

3 changed strings in module *wizard*.

Monday, January 30, 2006

String changes in SRC_m154

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

Friday, January 27, 2006

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

Monday, January 23, 2006

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.

Sunday, January 22, 2006

Kspread and OpenDocument

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

Saturday, January 21, 2006

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.

Thursday, January 19, 2006

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

Tuesday, January 17, 2006

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

Monday, January 16, 2006

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

Saturday, January 14, 2006

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 :(

Wednesday, January 11, 2006

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.

Monday, January 09, 2006

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.