A bug that could be a stopper for the L10N community

l10n
#1

Hello,

I already mentioned this bug some time ago on this list, I think:
http://qa.openoffice.org/issues/show_bug.cgi?id=58014
It is quite relevant for L10N teams and international users, even more
for users that have spell-checking, thesaurus and grammar needs in the
languages of their preference. It is present in OOo for a long time,
but there was no will to squash it.
Is it possible the L10N list would nominate this bug as a stopper for
LO3.4 or 3.3.2 or whichever version of LO?

Thanks, m.

#2

Hi *,

I already mentioned this bug some time ago on this list, I think:

It helps to at least mention what you're talking about in the subject.
Please choose a more telling subject next time.

http://qa.openoffice.org/issues/show_bug.cgi?id=58014
It is quite relevant for L10N teams and international users, even more
for users that have spell-checking, thesaurus and grammar needs in the
languages of their preference. It is present in OOo for a long time,
but there was no will to squash it.

There is no easy fix for this, due to the way it works on windows.
There are static dummy-document that are then in turn copied to the
location where you invoke the contextmenu→New function.

So LO/OOo could only fix it by recognizing on open that it is a
"shellnew" document and then replace it by itself using a document
based on the default template.
This is no problem if only OOo/LO is used to modify the documents, but
of course when other applications are used to edit the documents,
they'd ignore that property and then you risk that LO/OOo will throw
away the existing changes when not checking for modifications, etc.

Is it possible the L10N list would nominate this bug as a stopper for
LO3.4 or 3.3.2 or whichever version of LO?

Well, without a proposed fix....

ciao
Christian

#3

Thanks for your free lesson, but there is also something called "suspense":
http://en.wikipedia.org/wiki/Suspense

Lp, m.

#4

No, it is a matter of attitude (my post is the most important, so
everybody must read it). Many people on this list don't have just this
list subscribed, but easily receive hundred messages a day. Not using
a telling summary is either stealing their time, or just taking the
risk of not being read at all.

ciao
Christian

#5

Hi all,

Hi *,

I already mentioned this bug some time ago on this list, I think:

It helps to at least mention what you're talking about in the subject.
Please choose a more telling subject next time.

http://qa.openoffice.org/issues/show_bug.cgi?id=58014
It is quite relevant for L10N teams and international users, even more
for users that have spell-checking, thesaurus and grammar needs in the
languages of their preference. It is present in OOo for a long time,
but there was no will to squash it.

There is no easy fix for this, due to the way it works on windows.
There are static dummy-document that are then in turn copied to the
location where you invoke the contextmenu→New function.

So LO/OOo could only fix it by recognizing on open that it is a
"shellnew" document and then replace it by itself using a document
based on the default template.
This is no problem if only OOo/LO is used to modify the documents, but
of course when other applications are used to edit the documents,
they'd ignore that property and then you risk that LO/OOo will throw
away the existing changes when not checking for modifications, etc.

Thanks for your analysis Christian.

Is it possible the L10N list would nominate this bug as a stopper for
LO3.4 or 3.3.2 or whichever version of LO?

Well, without a proposed fix....

I agree on that that couldn't be a stopper, however there is a lot of duplicates on the issue, so it shows that it is often meet by a certain population of users.
What I wanted to do is open the bug on our own tracker to have it in our radar and ask Fridrich to have a look at it.

Kind regards
Sophie

#6

Hi,

2011.02.07 17:00, Sophie Gautier rašė:

http://qa.openoffice.org/issues/show_bug.cgi?id=58014
It is quite relevant for L10N teams and international users, even more
for users that have spell-checking, thesaurus and grammar needs in the
languages of their preference. It is present in OOo for a long time,
but there was no will to squash it.

There is no easy fix for this, due to the way it works on windows.
There are static dummy-document that are then in turn copied to the
location where you invoke the contextmenu→New function.

So LO/OOo could only fix it by recognizing on open that it is a
"shellnew" document and then replace it by itself using a document
based on the default template.
This is no problem if only OOo/LO is used to modify the documents, but
of course when other applications are used to edit the documents,
they'd ignore that property and then you risk that LO/OOo will throw
away the existing changes when not checking for modifications, etc.

Thanks for your analysis Christian.

Is it possible the L10N list would nominate this bug as a stopper for
LO3.4 or 3.3.2 or whichever version of LO?

Well, without a proposed fix....

I agree on that that couldn't be a stopper, however there is a lot of duplicates on the issue, so it shows that it is often meet by a certain population of users.
What I wanted to do is open the bug on our own tracker to have it in our radar and ask Fridrich to have a look at it.

Here's a possible solution:

step 1) don't put the files into the ShellNew folder. Quick googling reveals, that entries can be added to the New File menu using the registry instead of the template file. In that case, an empty file is being created.
step 2) alter LibO's behaviour: when it's given an empty (0-byte) file to open, it should initialize it using the default template instead of doing what it does now. And here's what it does:
   * Writer presents a transcode dialog (which makes absolutely no sense since the amount of data to transcode is 0)
   * Math creates a valid archive instead of the file, but the archive totally empty, and Math's UI is not shown. It looks like Math simply quits
   * I haven't checked other applications. By the way, I gave Math as an example just because we don't provide a template for it, so it was quite easy to check quickly

Another option would be to suggest the user to change the document language if no language is set for a document. But that would be quite annoying...

Rimas