After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 732913 - "Text to path" not working properly
"Text to path" not working properly
Status: RESOLVED DUPLICATE of bug 676413
Product: GIMP
Classification: Other
Component: General
2.8.2
Other Linux
: Normal minor
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2014-07-08 17:39 UTC by eng442
Modified: 2014-07-08 17:42 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Screenshot depicting the issue (873.72 KB, image/png)
2014-07-08 17:39 UTC, eng442
Details

Description eng442 2014-07-08 17:39:09 UTC
Created attachment 280178 [details]
Screenshot depicting the issue

Creating a text and then selecting "Text to path" doesn't always send the actual text to path (noticeable using "Select from path"). It sometimes sends only part of the text, sometimes cutting a word in two, sometimes failing at a new line. Only tested it with short texts. Example picture attached.

No error messages were issued (started gimp from terminal with the "--verbose" flag, no messages there when the actions described above were performed).

"gimp --version --verbose" output

GNU Image Manipulation Program version 2.8.2
git-describe: GIMP_2_8_0-194-ga42a02e

using GEGL version 0.2.0 (compiled against version 0.2.0)
using GLib version 2.32.4 (compiled against version 2.32.4)
using GdkPixbuf version 2.26.1 (compiled against version 2.26.1)
using GTK+ version 2.24.10 (compiled against version 2.24.10)
using Pango version 1.30.0 (compiled against version 1.30.0)
using Fontconfig version 2.9.0 (compiled against version 2.9.0)
using Cairo version 1.12.2 (compiled against version 1.12.2)

(from Debian Wheezy)
Comment 1 eng442 2014-07-08 17:42:56 UTC
Sorry, found a duplicate with more research. Seems to have been fixed in newer versions.

*** This bug has been marked as a duplicate of bug 676413 ***