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 706602 - Layers -> Text To Path Misses letters
Layers -> Text To Path Misses letters
Status: RESOLVED DUPLICATE of bug 676413
Product: GIMP
Classification: Other
Component: Tools
2.8.2
Other Mac OS
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2013-08-22 18:04 UTC by walkeraj@gmail.com
Modified: 2013-08-22 18:21 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Example of missing path pieces. (181.58 KB, image/png)
2013-08-22 18:04 UTC, walkeraj@gmail.com
Details

Description walkeraj@gmail.com 2013-08-22 18:04:11 UTC
Created attachment 252778 [details]
Example of missing path pieces.

Recently, while trying to do meme-style outlined text using the Layers -> Text To Path tool, I discovered the feature was missing letters.  Apologies in advance for the mild profanity in the picture but, unfortunately, I was unable to narrow down the exact case under which it occurs (believe me, I tried words like "BAG" and "WALL" on their own, but it seemed to work in those cases).

In the screenshot, you can clearly see the two separate text layers, the paths they generated, and the transparent layer I used the stroke tool on.  Hopefully this will be enough to re-create the bug.

Again, sorry for the text, but my attempts to be more specific met with failure (or success of the stroking, depending on how you look at it).
Comment 1 Michael Schumacher 2013-08-22 18:21:07 UTC
Thanks for taking the time to report this bug.
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. It should be solved in the next software version. You may want to check for a software upgrade.

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