Most of the `i18n` boilerplate was there, but the app still needed to
know what domain to look for. This must happen after initialization of
the `GtkBuilder` and before loading the glade file.
The domain is simply the `mo` file packaged with the app and usually
located under:
```
/usr/share/locale/$LANG/LC_MESSAGES/$APP.mo
```
Once again thanks to @maximbaz for pointing it out.
Closes#92
We need to verify the sources from github match our local content.
We do this by building our own version of the git release (using `git
archive`) and checking the SHA-256 checksums against the local and
remote.
After that it's safe to sign the remote `tar.gz` and upload the
signature file to the release.
One caveat is that if Github upates their git release commmand, this
script will break. We'll worry about it when that happens.
This drops support for `zip` signature. I wish there was a way to
prevent the zip source code when doing a new release.
Closes#90
Compute maximum width and height of area container based on monitor size
and fix image ratio based on appropriate values.
Note that this will lower the resolution of the final image.
Closes#56
UTF-8 characters are now handled porperly. Also re-worked some helper
functions with UTF-8 in mind.
I secretly no real C developers will look at this. I might have to ask
for witness protection.
Closes#43
../src/config.c:119:11: error: format specifies type 'long' but the argument has type 'guint64' (aka 'unsigned long long') [-Werror,-Wformat]
line_size);
^~~~~~~~~
/usr/local/include/glib-2.0/glib/gmessages.h:339:32: note: expanded from macro 'g_warning'
__VA_ARGS__)
^~~~~~~~~~~
../src/config.c:136:11: error: format specifies type 'long' but the argument has type 'guint64' (aka 'unsigned long long') [-Werror,-Wformat]
text_size);
^~~~~~~~~
/usr/local/include/glib-2.0/glib/gmessages.h:339:32: note: expanded from macro 'g_warning'
__VA_ARGS__)
^~~~~~~~~~~
2 errors generated.
