For example, when using a font like OpenDyslexia which has a very
large line spacing, the text gets shrunk since the overall bitmap
is too big for the space on the buttons (compared to the contents).
Cropping the whitespace will allow the text to remain larger.
WIP - The method of cropping isn't great. Text with descenders
appear higher than text without, causing terrible alignment.
So for now, the new `crop_surface()` code is not being used.
Also, replace some "#ifdef DEBUG printf(...) #endif" with
a simple "DEBUG_PRINTF(...)". And other minor tweaks.
Avoid reading outside of the bounds of the `touched[]` array,
to help prevent crashes.
h/t Miyagi Andel for reporting,
Shin-ichi TOYAMA for pinpointing the issue,
and Pere Pujal i Carabantes for providing a solution
Closes https://sourceforge.net/p/tuxpaint/bugs/269
These strings have been around a long time, and are only now
being utilized. Their purpose is for translators to provide
some characters which their language uses, so Tux Paint can
score fonts (and raise them to the top of the list in the
Text and Label tools) higher when they support those characters.
Many translators either left the strings as-is (e.g., "<9>spare-9b"),
or translated them literally (e.g., "<9>yedek-9b" & "<1>додаткова-1a"),
so removed those (replacing with `msgstr ""`).
Also, add other social media accounts to list of places to
announce Tux Paint in RELEASE docs.
Also, list a ton more options missing from default example config file
"src/tuxpaint.conf"
Ensuring that commentary about what font-scoring strings like
"oO" and ",.?!" are for make their way to the POT and PO files.
Also, adding some Hiragana to some of these strings in ja.po
(and updating some (c) dates in its comments).
Previously Pango loaded system-supplied fonts instead, which could lead
to fonts not rendering in a human-readable text. This change fixes
https://sourceforge.net/p/tuxpaint/bugs/265/
Each brush's initial spacing (calculated, or loaded
from .dat file) is recorded. When the spacing UI
is used to select a close, but not-precisely-the-same,
spacing option, the default is chosen ("nudged" to it).
h/t Pere for pointing this out (e.g., "aa_round_seethru_05.png")
Also, meter's lowest value has a sliver dark blue.
First time in a while. Appears indentation has caused some
comments to be lost. Need to sort that out :-/
e.g.
// Description of an octagon
gettext_noop("An octagon has eight equal sides."),
gettext_noop("An octagon has eight equal sides."),
still works, but
// Description of a rhombus
gettext_noop
("A rhombus has four equal sides, and opposite sides are parallel."),
gettext_noop
("A rhombus has four equal sides, and opposite sides are parallel."),
has lost the comment in the POT & PO files. >:-(
Apple keyboards have only a "Delete" key (which acts as Backspace),
so contortions with Fn key required to access the keysym I was
using for eraser quick access. h/t Mark Kim for pointing it out.
Because of this use of a printable glyph key, and to solve the
issue of on screen keyboard and in-progress text input getting
clobbered while accessing eraser, preventing access to the
quick eraser when either Text or Label tool are selected.
