Custom Font Paragrapher for Gimp 2.10 Version 002

[skinnyhouse]

Custom_Font_Paragrapher_002.py

(73.95 KiB) Downloaded 77 times

This release removes the 500 character limit (before throwing an intentional error) from the text entered into the filter dialog.

It also adds an option to use the active (or most recent) existing path associated with the image as a template line guide for the text. It will attempt to fit the canvas size to fit new layers should it be needed.

dialog002.jpg (41.73 KiB) Viewed 2531 times

Here are some path example screenshots (I have made the existing active path visible for you to see).


First a sloping path:

SlopingPath_LineSpace0.jpg (59.88 KiB) Viewed 2531 times

A wavy path:

WavyPath_LineSpace0.jpg (39.12 KiB) Viewed 2531 times

Same path with line spacing set to -25:

WavyPath_LineSpace-25.jpg (39.9 KiB) Viewed 2531 times

Same path with line spacing set to 75:

WavyPath_LineSpace75.jpg (39.85 KiB) Viewed 2531 times

Plenty of room to experiment with paths and since each line of custom font text is kept on a separate layer you can select and move them about to your liking. This last example has the line spacing set to 200:

RoundPathTest.jpg (46.61 KiB) Viewed 2531 times

[Pat625]

Skinnyhouse,

I continue to have problems that may be because I am expecting something that is not there. With your first examples, how did you divide your lines to make paragraphs? I used the enter key to separate the lines of text by entering twice, but that did not work. I could not even separate the title from the rest of the text.

All of my typed lines are there, so the 500 limit has been fixed. I must be doing something obviously wrong.

Maybe I have two many lines for the page. I am still experimenting, but I wanted you to know that I appreciate all of your work. You are so great at what you are doing. Sorry to be such a PIA!
This is a practice page so you can see what is happening with me.

Max.Afternoon.jpg (109.94 KiB) Viewed 2494 times

[skinnyhouse]

Thank you Pat:

I knew what I had (not) done as soon as I saw your reply.
Thank goodness you were there to test it out properly - I really appreciate your input.

Fixed in version 003 and ready for you to re-test.