Add/Remove RTL and LTR buttond to formating toolbar has no effect

users
#21

However, this is an LO list & LO devs work w/bugs.freedesktop.org
bugzilla. OOo is a completely different issue.
  Yes, I know that most of the code is similar/same, but if you want it
fixed in LO you'll need to file a bug as mentioned above.

Further, on your OOo bug, it's generally helpful if you provide the full
versionrc so that those devs know exactly which version of OOo you are
using & if you are using OOo standard, or a distro modified (aka
Ubuntu'ized) version. Easiest way is to provide the output of the
versionrc file for the version you are using (please do the same when
filing an LO bug).

#22

Sorry, forgot to add (for other folks on linux that may not know) how to
do that last:

$ locate versionrc
/opt/libreoffice/basis3.3/program/versionrc
/opt/libreoffice/program/versionrc
/opt/libreoffice/ure/bin/versionrc
/opt/libreoffice3/ure/bin/versionrc
/opt/ooo-dev/basis3.2/program/versionrc
/opt/ooo-dev/basis3.3/program/versionrc
/opt/ooo-dev/basis3.4/program/versionrc
/opt/ooo-dev/ure/bin/versionrc
/opt/ooo-dev3/program/versionrc
/opt/openoffice.org/basis3.2/program/versionrc
/opt/openoffice.org/ure/bin/versionrc
/opt/openoffice.org3/program/versionrc
/usr/lib/openoffice/basis3.2/program/versionrc
/usr/lib/openoffice/program/versionrc
/usr/lib/ure/bin/versionrc

I've multiple versions of OOo + LO installed. The one that I want in
this case is /opt/libreoffice/program/versionrc. So:

$ cat /opt/libreoffice/program/versionrc
[Version]
AllLanguages=en-US
buildid=330m18(Build:4)
ExtensionUpdateURL=http://updateexte.libreoffice.org/ExtensionUpdateService/check.Update
OOOBaseVersion=3.3
ProductBuildid=4
ProductMajor=330
ProductMinor=18
ProductSource=OOO330
UpdateID=LibreOffice_3_en-US
UpdateURL=
UpdateUserAgent=<PRODUCT> (${buildid}; ${_OS}; ${_ARCH};
BundledLanguages=${AllLanguages})

Copy & paste that into the report & then the devs can easily see which
version/build the report is about.

Similar for Windows users, only the file is 'version.ini'.

#23

Salam Noop,

thak you for your help!

ok i'll send mine to bugzilla

#24

What about looking at Help/About Openoffice.org or LibreOffice
and then copy/paste the info from the pop-up?

Here is my LO info

LibreOffice 3.3.0
OOO330m19 (Build:6)
tag libreoffice-3.3.0.4

Here is my OOo info

OpenOffice.org 3.2.1
OOO320m19 (Build:9505)
ooo-build 3.2.1.4, Ubuntu package 1:3.2.1-7ubuntu1

It this info enough?
LO is the RC4 build that was announced today[?].

#25

...

$ cat /opt/libreoffice/program/versionrc
[Version]
AllLanguages=en-US
buildid=330m18(Build:4)
ExtensionUpdateURL=http://updateexte.libreoffice.org/ExtensionUpdateService/check.Update
OOOBaseVersion=3.3
ProductBuildid=4
ProductMajor=330
ProductMinor=18
ProductSource=OOO330
UpdateID=LibreOffice_3_en-US
UpdateURL=
UpdateUserAgent=<PRODUCT> (${buildid}; ${_OS}; ${_ARCH};
BundledLanguages=${AllLanguages})

Copy& paste that into the report& then the devs can easily see which
version/build the report is about.

Similar for Windows users, only the file is 'version.ini'.

What about looking at Help/About Openoffice.org or LibreOffice
and then copy/paste the info from the pop-up?

Here is my LO info

LibreOffice 3.3.0
OOO330m19 (Build:6)
tag libreoffice-3.3.0.4

Here is my OOo info

OpenOffice.org 3.2.1
OOO320m19 (Build:9505)
ooo-build 3.2.1.4, Ubuntu package 1:3.2.1-7ubuntu1

It this info enough?
LO is the RC4 build that was announced today[?].

Yesterday.

I reckon so. Just noticed the versionrc on this machine is for RC2 - the
other machines are RC4 :slight_smile: I think I'll archive this version so that I
can compare against RC4.

#26

I normally do not run any RC versions, but since LibreOffice
does not have any full releases yet, I just started with RC3 and
then upgraded to RC4. When it finally go to 3.3.x, then I will
wait till the next version is out and not install an RC version.

OpenOffice.org is on RC10 right now, while LibreO is on RC4.
What I have been seeing in these threads lead me to believe
that the people are slower to put out a RC version, but also
may wait between RC version for more of the work to be done
and verified. Not having to justify your paycheck with Oracle
or other software company to "finish" your project in time and
under budget, lets people slow down and possibly do a better
job. I always tell people, when I was a mainframe programmer,
that I will get it done as quickly as I can do it correctly the first
time and not have to spend as much time fixing problems that
creep up during testing. I hope the current world of PC based
programming still hold to that instead of rush, rush, rush, to get
the job done as quickly as possible. I was/am a slow typist so
I could never rush a project and would rather do as much as I
could to get it right before I started typing it at my slow pace.
Actually learning coding with punch cards and teletype terminals
may have helped that idea along.

So, even though it would be nice to have a full release version
of LibreOffice to send my friends and former clients, I will wait
for the slow and steady process to finish. Should get a better
working product in the long run.

#27

amine amine wrote:

here it is on the bugs.freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=33356

In cases like this one, where you duplicate an upstream bug report, I'd
advise at least to put a link to the corresponding upstream bug, i.e.
http://www.openoffice.org/issues/show_bug.cgi?id=116559 in a comment.

Pending more efficient solutions still to be agreed upon, this will at
least guarantee that LibreOffice developers can check whether the bug
has been fixed upstream and be sure they are not wasting their time.

Regards,
  Andrea.

#28

webmaster wrote:

OpenOffice.org is on RC10 right now, while LibreO is on RC4.
What I have been seeing in these threads lead me to believe
that the people are slower to put out a RC version, but also
may wait between RC version for more of the work to be done

Actually I believe that the 3.3 release process should not be taken as a
reference at all, but LibreOffice is definitely not slower, it's faster;
it merely started the RC phase later. Here are the relevant RC dates:

2010-11-29 OpenOffice.org RC7
2010-12-05 LibreOffice 3.3.0 RC1
2010-12-17 OpenOffice.org RC8
2010-12-23 LibreOffice 3.3.0 RC2
2011-01-13 LibreOffice 3.3.0 RC3
2011-01-14 OpenOffice.org RC9
2011-01-20 LibreOffice 3.3.0 RC4
2011-01-21 OpenOffice.org RC10

so the average lifespan of a Release Candidate in this period was 18
days for OpenOffice.org and 15 days for LibreOffice. Then I should
repeat that the 3.3 release process was definitely not standard on
either side, so a comparison like this one will make more sense in
future releases.

Sources:
http://wiki.documentfoundation.org/Marketing/ReleaseDates
http://www.openoffice.org/servlets/SummarizeList?listName=releases&by=date

Regards,
  Andrea.

#29

What I wanted to imply, was that to me LibreO people are doing a
good job and not rushing a RC out when it is not ready. LibreO RC4
seems better than OOo's RC10. Might be me, but that is my opinion.
I have seen "show stoppers" with OOo's RCs but not one with LibreO
so far in its RC2, RC3, RC4. So I have no problem running/using LibreO
RC3 or 4 while I rarely will use an OOo RC anymore.

#30

Hi

I think Oracle have decided they are competing with LibreOffice but so far we
seem to be co-operating with them. It would be wise for us to
1. Beat them to the finish line.
2. Keep aware of what they are doing, odd stats can help sometimes
3. Keep going the way we have been, rapid growth and development in
infra-structure and support along with excellent coding development
4. Keep co-operating as long as they let us.

After initial release we wil, of course, keep developing in all areas so rushing
final release and getting it out there wouldn't hurt us. We don't have to worry
about corporate clients right now but they do. So a 2nd release in another
couple of months wouldn't hurt us but it's almost unthinkable for them.
Regards from
Tom :slight_smile:

#31

hi,

1. Beat them to the finish line.

no. Don't bother. LibreOffice needs to be (very) good, not be first-and-not-so-good.

2. Keep aware of what they are doing, odd stats can help sometimes

yes.

3. Keep going the way we have been, rapid growth and development in
infra-structure and support along with excellent coding development

yesssss !

4. Keep co-operating as long as they let us.

well...

After initial release we wil, of course, keep developing in all areas so rushing
final release and getting it out there wouldn't hurt us. We don't have to worry
about corporate clients right now but they do. So a 2nd release in another
couple of months wouldn't hurt us but it's almost unthinkable for them.

Just keep up with the good work! Never forget the libre software motto: "Release early, release often".

:slight_smile:

#32

I hate the corporate pressure to hurry up and get it done as
quickly as possible. I use to do mainframe programming
for a business that has that same mindset.

I do not know what will happen to OpenOffice.org's "quality"
of software and its usability with Oracle's pushing it. Too many
packages, in the past, have been turned into something not
as good when a large business took over the company that
owned and developed it. Some were useless for me after a
few years. I hope OOo does not go that way. I am almost
positive that LibreOffice will not go that route.

I started using OOo back when they did not have .doc support.
I loved it for Windows. A few years back I used OOo 99% of
the time and in Feb '10 I went full time to Ubuntu, so I went to
OOo. Now that Oracle owns OOo's name and such, I added
LibreOffice to me desktop. I use it as much as OOo now. I
may dump OOo, if it goes the way of a lot of software I
use to use.

I know I will be letting all my friends, family, and former clients
know about using LibreOffice as soon as a final release is out.
I also assume that OOo's extensions work with LibreO. That
way there will no problem with their favorite additions for OOo
to be included with LibreO installation.

#33

I would not bet on extensions working, try them out first to see.

#34

Are you suggesting that upstream (OOo) bugs are fixed independently in
LibreOffice? Or are you referring to LibreOffice specific bugs? For
that matter, is LibreOffice still pulling from OOo upstream? If so,
are bugs fixed in LibreOffice being submitted as patches to the OOo
bugtracker, or is it up to Oracle to come asking for them? I think
that it would be wise of LibreOffice to file the patches, and I am
willing to take that responsibility if needed.

#35

Hi :slight_smile:

Since my earlier message, in this thread, got taken out of context (by deleting
the emails that i was responding to) my message lost it's meaning.

Regards from
Tom :slight_smile:

#36

I agree with "Release early, release often" rather than the response to my
comment1 which contradicts that.

Regards from
Tom :slight_smile:

#37

Well... There's no contradiction, IMO. Or should I have made myself more clear. I meant: don't bother to beat "them" (whoever they can be), but LibreOffice just go your way at your own pace.

#38

...

116559 has been marked as a dupe of:
http://www.openoffice.org/issues/show_bug.cgi?id=54423
* Summary: Disable hidden icons in the "visible buttons" menu when the
Asian or CTL support is disabled
Opened: Sat Sep 10 03:49:00 +0000 2005
Target milestone: OOo Later

@amine: You might add a note to 33356 referencing ‘Upstream OOo Issue
54423 - http://www.openoffice.org/issues/show_bug.cgi?id=54423’.

#39

[...]

Hi Bradley,

Thank you for sharing that. A few days ago someone using slackware asked
about this on IRC but I don't use it so I couldn't help. When you share
again this kind of information would you mind including its source next
time ? I found the original blog post here if anyone needs it:
http://alien.slackbook.org/blog/release-candidate-four-of-libreoffice-3-3-0/

Are you a slackware user ? If you'd like to post about slackware
progress once in a while on this list I'd love to hear about it so we
can update the docs.

Again, thanks for sharing this.

Cheers,

#40

Salam,

Still not resolved with the Final release of today!

good luck !