frd said 
I see, the upscaling might have been what made it look fuzzy to me.
So it's doable?
TonyN said 
Hello. The invitation to the server is no longer valid. Was it active for a limited time, or is the server no longer in existence?
Maybe someone forgot to make the invite link infinite?
frd said 
The 800x480 image is using a jpeg as the background so it wouldn't be accepted as is. Also, when submitting something as an update, you only need to submit the files that you want to update. If the rest doesn't change, then it will remain the same.
Ironically, that image never involved JPEG. I hate JPEG (and lossy image compression as a whole, so stuff like WEBP, HEIC, AVIF, and such count too) with a passion.
The border was originally drawn at 400x240 PNG, and I used 2xPSNR to upscale it. The only way JPEG would be involved would be if what I layered to make the 400x240 border had been made from JPEG space images, and I have no way to verify this.
The PSNR series of upscalers are actually quite powerful. Turns out, they make a 16x scaler, which can take something 400x240 and scale it to 6400x3840. It actually proved useful in one of my digital artworks (
https://stgiga.sourceforge.io/8KstgigaAssetsGalaxyBrain.png for the curious).
Thanks for the clarification on uploads though. It was helpful.
Two questions: Firstly, does a PNG image that is 800x480 (namely
https://stgiga.github.io/UnifontEX/UFEXsocial.png which is made from the current illustration inserted into a 2x-upscaled border of mine, and it *just* fits the 800px maximum width, and I use it as the banner for UnifontEX on certain sites) work as an illustration, and B: when issuing an illustration update, will the TTF get erased if it isn't specified?
Also I'm not going to test this third thing, but I DID make a zip file (
https://UnifontEX.sourceforge.io/UnifontEX.zip for those curious) of ALL formats offered (including macOS DFONT and PostScript Type 42, as well as ALL webfont formats, and more), but the file size is 99MiB (hence why I'm not going to test it). I'm morbidly curious what would happen if THAT were uploaded, but I don't think I want to find out.
My apologies for all the questions.
I'm a bit concerned at the lack of an update, but I know it's almost Christmas. I mean, extra Unicode *is* a good gift honestly.
On December 12th, 2024, I was magically able to get UnifontEX to support Unicode 15.1's additional Ideographic Description Characters, and I've issued it as an update. I'm hoping it gets approved. I feel like a Unicode version bump is a GOOD thing. Both the last update here and this one were *significant* updates.
Edited 2 times. Last edit on Dec 14, 2024 at 09:22 by stgiga
So, I submitted my font quite literally a year ago and it finally got accepted. This is good news. However I updated it after, and the latest version of the TrueType is from February 2nd, 2024 (I had also found out that I started the font in 2014, as opposed to my original estimate). I have submitted THAT version as an update to the original upload, and I'm writing this just in case anyone is wondering why I issued an update so soon after it got added. Hopefully the update goes well.
As for what has changed? Well, the changes between the September 12th, 2023 and February 2nd, 2024 builds are that there are several new tables present. BASE, MATH, JSTF, and VDMX. All of these help renderers, and adding them wasn't originally possible until I tried the same method in December 2023 and magically, the BASE, MATH, and JSTF tables successfully generated when they hadn't worked prior on the same editor, but NOT the same computer I had until October 2023. So in December 2023, I published the BASE, MATH, and JSTF table version, and thought *that* was the end. I ended up running CacheTT on the font for the sake of leaving no stone unturned, and that added the VDMX table (it can also add LTSH and hdmx tables, but it didn't want to include them, and this later proved to be a good thing due to Android 14 reasons.)
These four extra tables do not significantly hike the font size the same way instructions, embedded bitmaps, or embedded SVG are known to do.
I also populated the "Sample Text" field in the name table with a line (One font to rule them all!) that was in my older 2018 drafts of the font.
Also, since September 2023, I proceeded to release the font in MANY formats beyond TrueType. From web formats to legacy formats to niche formats, and sometimes formats that are all of these.
They're on the linked Github Pages site (though with the deprecation of .io domains, the URL may change, and for certain reasons I may be unable to change it on Dafont). I very recently made the site prettier, though it's also much longer now. Importantly, it is self-demonstrating, meaning the page font is UnifontEX now, and there is a section that shows off some VERY special characters. I'd wanted to do that for a full year and only recently achieved it.
A LOT has gone on since I originally uploaded UnifontEX here, and I hope that the update goes well.
Also I know that Dafont does not support anything other than TrueType, and that uploading the 99MiB all-formats-in-one Zip file would be a bad idea, so to avoid problems I elected not to do it. Even if it would make the link rot problem go away.
Edited on Nov 18, 2024 at 06:53 by stgiga
All times are CEST. The time is now 01:55