On 7/21/07, Lior Kaplan <[EMAIL PROTECTED]> wrote:
Hi,
Could you take a look at bug #427996 ?
Maybe you'll have any idea, why does our users get different font
variants in each program (oo.org, gedit, kde font isntaller).
Thanks.
This has been reported in bug 426125 (and 415432), which is mi
i wrote several kinds multiple line paragraphs inside "text box" and none was
hiding any lines. all lines were always visible and i could not even resize
the text box to hide part of the text.
so i guess it fixed and we could close it down.
(unless, i didn't understand what this issue was in the
how can i tell what display setting are used for fonts in OO ?
btw.
i use KDE, so i guess OO should read KDE's font setting ?
(when it's started from KDE)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
i've tested this one with different fonts. all works fine :-)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
i've tested several formats and styles on a hole paragraph and also when
starting a paragraph with a pre-selected style.
saving and re-opening the documents, all formating is displayed correctly :-)
especially when OO warns that saving with RTF may cause formating lose.
--
To UNSUBSCRIBE, em
i voted for this one on OO.org main site, hope it helps :-)
link: http://qa.openoffice.org/issues/show_bug.cgi?id=49564
(maybe it's easy to fix it without asking OO.org ?)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: openoffice.org
Version: 2.2.1-5
Severity: normal
I noticed that openoffice gets default paper size for printers from
/etc/papersize only if libpaper-utils is installed. spadmin, even if run
as root, doesn't change the default paper size. I tried to edit
/etc/openoffice/psprint.conf direct
i've added a new user "adduser foo" (as suggested)
logged in, (default was GNOME desktop) open Impress
inserted a video (avi file) with no problem :-) it played.
i also check several other videos with different encoding
methods, all worked fine.
BUT, a new bug surfaced...
the video was playing in
Your message dated Sun, 22 Jul 2007 13:57:51 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing obsolete bug
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibilit
Your message dated Sun, 22 Jul 2007 13:31:32 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing obsolete bugs
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibili
Your message dated Sun, 22 Jul 2007 13:31:32 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing obsolete bugs
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibili
Your message dated Sun, 22 Jul 2007 13:31:32 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing obsolete bugs
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibili
Your message dated Sun, 22 Jul 2007 13:31:32 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing obsolete bugs
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibili
Your message dated Sun, 22 Jul 2007 13:31:32 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing obsolete bugs
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibili
Your message dated Sun, 22 Jul 2007 13:31:32 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing obsolete bugs
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibili
Your message dated Sun, 22 Jul 2007 13:31:32 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing obsolete bugs
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibili
Your message dated Sun, 22 Jul 2007 13:31:32 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing obsolete bugs
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibili
Your message dated Sun, 22 Jul 2007 13:31:32 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing obsolete bugs
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibili
Your message dated Sun, 22 Jul 2007 13:31:32 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing obsolete bugs
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibili
Your message dated Sun, 22 Jul 2007 13:31:32 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing obsolete bugs
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibili
Your message dated Sun, 22 Jul 2007 13:31:32 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing obsolete bugs
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibili
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
ooqstart | 0.8.3-10 | source
ooqstart-gnome | 0.8.3-10 | i386, sparc
ooqstart-gnome | 0.8.3-10+b1 | powerpc
Note that the package(s) have simply been removed from the tag
database an
Your message dated Sun, 22 Jul 2007 12:55:04 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing obsolete bugs
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibili
Your message dated Sun, 22 Jul 2007 12:55:04 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing obsolete bugs
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibili
Your message dated Sun, 22 Jul 2007 12:55:04 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing obsolete bugs
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibili
Your message dated Sun, 22 Jul 2007 12:55:04 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing obsolete bugs
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibili
Your message dated Sun, 22 Jul 2007 12:55:04 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing obsolete bugs
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibili
Your message dated Sun, 22 Jul 2007 12:55:04 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing obsolete bugs
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibili
Your message dated Sun, 22 Jul 2007 12:55:04 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing obsolete bugs
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibili
Your message dated Sun, 22 Jul 2007 12:55:04 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing obsolete bugs
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibili
Your message dated Sun, 22 Jul 2007 12:55:04 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing obsolete bugs
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibili
Your message dated Sun, 22 Jul 2007 12:55:04 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing obsolete bugs
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibili
Your message dated Sun, 22 Jul 2007 12:55:04 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing obsolete bugs
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibili
revno: 797
committer: Rene Engelhard <[EMAIL PROTECTED]>
branch nick: debian
timestamp: Sun 2007-07-22 12:28:46 +0200
message:
fix/improve splash/about install
removed:
brabout.bmp.uu
brintro.bmp.uu
added:
scripts/fix_image_rgb
mo
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
oooqs |2.0.3-8 | source
oooqs-kde |2.0.3-8 | i386, powerpc, sparc
Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the
revno: 786
committer: Rene Engelhard <[EMAIL PROTECTED]>
branch nick: debian
timestamp: Sun 2007-07-22 12:17:11 +0200
message:
merge löibc*-dbg suggestion from 2.3 branch
modified:
changelog
rules
=== modified file 'changelog'
--- a
revno: 785
committer: Rene Engelhard <[EMAIL PROTECTED]>
branch nick: debian
timestamp: Sun 2007-07-22 12:14:10 +0200
message:
merge etch backport fixces from 2.3 branch
modified:
changelog
rules
=== modified file 'changelog'
--- a/
revno: 796
committer: Rene Engelhard <[EMAIL PROTECTED]>
branch nick: experimental
timestamp: Sun 2007-07-22 12:12:44 +0200
message:
typo
modified:
rules
=== modified file 'rules'
--- a/rules 2007-07-22 09:42:24 +
+++ b/rules
revno: 795
committer: Rene Engelhard <[EMAIL PROTECTED]>
branch nick: experimental
timestamp: Sun 2007-07-22 11:42:24 +0200
message:
etch backport fixes
modified:
changelog
rules
=== modified file 'changelog'
--- a/changelog 2007-07
39 matches
Mail list logo
