Thanks to those who downloaded the first trial version of my Splitter plug-in which sadly threw errors in Linux.

Trial 2: Version 01 of the plug-in.

If you would like to try this out, download the plug-in, extract it and place it in your user plug-ins folder.



Download the two custom font file attachments. Only the first (which, when de-compressed, exceeds the file size limit here) is zipped.
Create a suitable folder for this task and extract the first file and then place both files into your new test folder.





Instructions for using stitcher in next post...

It worked!
The output of the variables:

Instructions for Stitcher v 01

Start up Gimp and open the parent file Mama_Fusion

File>Open...

Navigate to your folder and find the file to open.

Call up the filter dialog using:

Filters>Custom Fonts>Constructing Tools>Custom Font File Stitcherv01...



The new option provides a means of viewing the filenames and paths used - but only if the filter succeeds!

If successful all 72 characters (the thumbnail below doesn't count the space character) of the original custom font should now be available in Gimp ready to be re-saved.

As before I would appreciate it if users could let me know if it works on non-Windows OS.

Thanks Nelo - boy you're quick off the mark!

OK, this time it worked under some conditions.
It works only if I opened the file without numbering first. (yes I'm dumb, but I'm ok with that )

The first try I opened the file called Mama_Fusion_1.xcf and got this error:


It adds an "_1" to the file name it is searching for, instead of reading/opening Mama_Fusion_1.xcf, it tries to open Mama_Fusion_1_1.xcf (2 times "_1")
Um... How to say it, I got another horrible thought
Maybe a add function to open all file-name-[x].xcf / file-name.xcf except the one file-name-[y].xcf / file-name.xcf which is already open?
I'm almost sure that I won't be the only one to do that dumb thing

Again thank you so much Skinnyhouse

Thanks for testing Patrice.

That error sounds good - that's what i would expect to happen. A little bit of code will check for that occurence in future and sort it out.

As for splitting the files apart in the first place - the Splitter plug-in already exists - you don't think I did it manually.

Thanks for the laughter, that was a good one