Found some issues with output size when padding required, just re-implemented both functions from scratch.

Note that returned output size considers the NULL terminator as an additional byte.

corrected coding conventions.

Bug Fix Update
Code to Ignore Hovering Inputs Completely

It is called on window minification and setting internal width/height to 0, that can break things

- All `char *` refer to text strings
- All `unsigned char *` refer to generic byte arrays

Make the default font loader early out if we have already loaded parts of it, so we don't leak memory

I believe it makes sense to only do this when there are no known
touch points. I am not even sure if this should be done at all.

See https://github.com/raysan5/raylib/issues/4872 for more information.

Restore window currently says it sets the window state to:

   "not minimized/maximized"

However, if a window is maximized and then minimized, it's typical that
it would restore back to being maximized, which is what seems to happen
from my testing. I've reworded the description to better reflect
this behavior.

raylib app crashing when started and a gamepad is already connected to the PC (even if the gamepad is not used in the app). I only tested this with a gamepad that has a layout which is not recognized. Using SDL3 as backend.