Apache OpenOffice (AOO) Bugzilla – Issue 23268
FontWorks platform (in-)dependence
Last modified: 2013-07-30 02:14:30 UTC
I created a sxd document with OOo Draw for Windows, which contains a FontWorks object. When I opened the same sxd with OOo Draw for Linux, this FontWorks object did not work anymore - I even can not modify the FontWorks options. I'll post the file.
Created attachment 11800 [details] problem document
Sorry, cannot reproduce this. Are you shure the file was not in write-protected mode when opening it under linux? Can you attach a screenshot from your linux system opening the file? Thanks in advance.
Priority changed to 3.
Created attachment 11817 [details] screenshot of the problem case - opened r/w
Some additional information about my Linux system: Version: OOo 1.1.0 [645m19(Build:8693)] german binary package from de-project. Desktop: XFCE 4 (version 3.99.2) X11: Xfree86 4.3.0-r3 Linux: 2.4.20-gentoo-r6 Compiler Environment (OOo is not compiled on this machine!): Portage 2.0.49-r15 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r8, 2.4.20-gentoo-r6) ================================================================= System uname: 2.4.20-gentoo-r6 i586 Pentium MMX Gentoo Base System version 1.4.3.11 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-O3 -mcpu=pentium-mmx -march=pentium-mmx -funroll-loops -pipe" CHOST="i586-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /var/qmail/control /usr/share/config /usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-O3 -mcpu=pentium-mmx -march=pentium-mmx -funroll-loops -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="sandbox ccache" GENTOO_MIRRORS="ftp://trumpetti.atm.tut.fi/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 oss apm avi crypt cups encode foomaticdb gif gpm imlib jpeg libg++ libwww mad mikmod motif mpeg ncurses nls pdflib png quicktime slang spell truetype xml2 xv zlib gdbm berkdb readline svga java sdl tcpd pam ssl perl python oggvorbis opengl mozilla -alsa -qt -kde -arts -gnome dga dvd emacs imap ipv6 joystick maildir mule pda samba sse usb X -gtk gtk2 -xmms"
Reproduced on OOo 1.1.0, built from sources, running on Gentoo Linux. When the document is opened, there are a series of small markings in the approximate location of the FontWorks document. These dots are visible in the upper-right quadrant of the screenshot. However, upon doubleclicking on one of the dots, the text editor thing (sorry, don't know the real name) opened up, revealing the words "FREE your Documents!" in my default font. After changing the font (I used Bitstream Vera Sans, not that it matters), the FontWorks object displayed the letters in an arc, with a shadow the color of the dots visible in the screenshot, as I believe was intended. I suspect that the issue is a lack of font replacement for FontWorks objects, or something along those lines. It would be helpful to know more information; specifically, which font you used in Windows, if that font is available in your Linux environment, if doubleclicking on the object reveals the words, and if changing the font allows you to view the object as it was designed. Thanks.
Can be reproduced.
Reassigned to Armin. Please have a look.
> After changing the font (I used Bitstream Vera Sans, not that it matters) ... Used this font in Windows too, so it should be available in both environments. After double clicking on the object the 'text editor thing' appeared already in Bitstream Vera Sans. So I changed it to another font and then back to Bitstream Vera Sans. After that the FontWorks object displayed correctly! > I suspect that the issue is a lack of font replacement for FontWorks objects ... It doesn't look like a font replacement problem to me, because after saving and reloading the modified file the bug was back again. Can you confirm this too?
Confirmed, sort of, also on OOo 1.1.0, built from source, on Gentoo Linux. You're right; it does not, on second glance, to be a simple font replace object. Do the following: 1. Open the flying.sxd document. 2. Double-click on the approximate area of the FontWorks object. 3. Change the font of the text to any other font, then change it back. 4. Click away from the FontWorks object to deselect it. 5. Note how the FontWorks object is displayed correctly. 6. Save the document. 7. Close and reopen the document. 8. Note the renewed /absence/ of the FontWorks object. However, if you do the following: 1. Open the flying.sxd document. 2. Double-click on the approximate area of the FontWorks object. 3. Change the font of the text, but _do_ _not_ change it back. 4. Save, close, and reopen. 5. Note how the FontWorks object _is_ correctly displayed. 6. Repeat steps 2 and 3, changing the font back to the original font. 7. Save, close, and reopen. 8. Now the FontWorks object is correctly displayed in Bitstream Vera Sans. Weird, huh? This is another wild guess, with probably about the same level of accuracy as the first turned out to be, but perhaps the file format is subtly different between XP and Linux versions, a change rectified upon producing an alteration to the FontWorks object that must be saved. I'll try and do a diff of the underlying XML files in the SXW, and see what changes between the Vera Sans version that works and the one that doesn't.
AW: I am pretty sure there is no difference in the file formats between the plattforms. The last two cases just seem to show (in my opinion) that the file with which this problem happened was produced with an OOo version which had an error with saving fonts/matched fonts. If You continue to do tests (thanks for that, this is much appreciated) please take a look if You can produce files with that problem at all with a current OOO version. If not, that problem was identified and maybe fixed. Sometimes it is not possible to fix all produced in-between files at load time, especially with XML which does not contain a Five-Version info but only the DTD versioninfo (which does not change because of BugFixes nor due to the next slightly different build).
AW->srobertson: Please have a look concerning my last comment
I had tried repeatedly previously to reproduce the error, but I couldn't find anything. For some reason I didn't add a comment to that effect. There were a few subtle differences between the file that worked and the one that didn't (other than the fact that the relative location of all the DTDs and config files had changed from a windows path to a linux path), but I couldn't trace the problem down to one entity, nor could I reproduce faulty output on my version of OOo. Sorry I didn't comment sooner.
OpenOffice.org Issue Tracker - Feedback Request. The Issue you raised has the status 'New' pending further action, but has not been updated within the last 4 years. Please consider re-testing with one of the latest versions of OOo, as the problem(s) may have already been addressed. Either use the recent stable version: http://download.openoffice.org/index.html or consider trying the new OOo 3 BETA (still in testing): http://download.openoffice.org/3.0beta/ Please report back the outcome so this Issue may be Closed or Progressed as necessary - otherwise it may be Resolved as Invalid in the future. You may also wish to search for (and note) any duplicates of this Issue that may have advanced further by checking the Issue Tracker: http://www.openoffice.org/issues/query.cgi Many thanks, Andrew Cleaning-up and Closing old Issues as part of: ~ The Grand Bug Squash, pre v3 ~ http://marketing.openoffice.org/3.0/announcementbeta.html
Reset assignee on issues not touched by assignee in more than 2000 days.