GNOME Bugzilla – Bug 744715
Text layout in GIMP is different to text layout in PDF export
Last modified: 2017-10-31 23:37:34 UTC
Created attachment 297104 [details] that's the textbox in gimp Hi everybody, I really appreciate using the gimp, thank you for your continuous work on it. I've had the following bug for a few times now: 1) new document, create a textbox. 2) write some text in it, in one line. The last word should be on the second line, with automatic linebreak. 3) export it as a pdf 4) the last word jumps back to the first line I'm not quite sure if it is a duplicate of this bug: https://bugzilla.gnome.org/show_bug.cgi?id=681895 Let me know if you need more information.
Created attachment 297105 [details] that's the text in the pdf export
Is this really 2.8.2? If so, please upgrade to 2.8.14 and report back.
I tried it on 2.8.14, and I get the same output in the pdf.
Created attachment 297354 [details] This is an example file, tested on gimp 2.8.14 under debian and windows
One thing I noticed that causes differences between GIMP core and the pdf plug-in is that the plug-in does not use fonts installed in a personal directory unless I manually add a file ~/.config/fontconfig/fonts.conf listing the personal font dirs, like: <?xml version="1.0"?> <!DOCTYPE fontconfig SYSTEM "fonts.dtd"> <fontconfig> <dir>/home/massimo/.gimp-2.8/fonts</dir> <dir>/home/massimo/.config/GIMP/2.9/fonts</dir> </fontconfig> otherwise the plug-in uses a fallback font that is similar, but different from that used on canvas. Nonetheless it is possible that the plug-in does not repeat exactly all the steps that GIMP core executes and this results in different logical extents with different line breaks.
Hi neto, I was having a similar issue with 2.8.6 today, updated to 2.8.22 and it's now exporting text to pdf as expected. Cheers, Dave
This could be a duplicate of bug 681895, I guess.
Hi Dave and Michael, Today I tried it with gimp 2.8.22 under linuxmint and windows, and it exported text to pdf as expected too! Thanks for pointing it out! So I guess it's resolved? (it is for me at least) And yes, maybe it was a duplicate of bug 681895 after all? neto
Let's assume it is. Thanks for taking the time to report this. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed in the code repository. *** This bug has been marked as a duplicate of bug 681895 ***