Skip to content

Conversation

EL-File4138
Copy link
Contributor

This fix #215.

It passed an out-of-band build/packaging session on Fedora Copr.

@arch1t3cht
Copy link
Member

Could you also cherry-pick the two other desktop/appdata-related commits from https://github.com/arch1t3cht/Aegisub/pull/52/commits and remove the CherryPick: prefix? Then I can merge (once the CI runs through).

@EL-File4138
Copy link
Contributor Author

Did a bit of force push to correct past commit state, hope that does not mess around the history. Also corrected the metadata template.
I think the i18n module is still not working for metadata translation, but to be honest the pot file hasn't been properly updated for years. I think this should be left for a complete i18n update while collaborating on all the new translation efforts. For now, a quick fix as such should suffice.

a91c4f7 switched processing of the
desktop file from intltool to gettext-backed i18n.merge_file and dropped
leading underscores which used to be processed by intltool.

However, this commit omitted dropping the underscore from Keywords,
resulting in this field being stripped from the installed version.

Furthermore, make_pot.sh was broken since it too relied on the
underscore meaning POT regeneration will now remove the desktop files
strings from translation files.
Since it was not added to po/POTFILES meson’s native aegisub-pot target
also doesn't add desktop file strings to the translation pool. Though,
this target still misses a lot of other strings as well and shouldn't be
used yet anyway.

This commit removes leftover underscores and reintegrates desktop file
strings into both make_pot.sh. Integration into aegisub-pot is done in a
follow-up commit.
meson’s i18n module get’s confused by .template and fails
to extract translatable strings, thus rename to in.in.

Note: while this slightly improves the situation, meson’s aegisub-pot
target is still missing many strings. make_pot.sh should be used.
@arch1t3cht
Copy link
Member

Your rebase had a merge conflict marker in it that was then again wiped by the first renaming commit, so I re-cherry-picked things and force pushed.

meson's i18n module is definitely still not complete, yes, but that can be fixed some other time.

@arch1t3cht arch1t3cht force-pushed the appdata-fix branch 2 times, most recently from e25e87a to 9d89a7c Compare December 20, 2024 20:20
TheOneric and others added 2 commits December 20, 2024 21:21
It used to be genrated and installed by the old custom build system,
but apparently got lost in switching to meson.

Rename to .in.in instead of .template.in, since i18n otherwise gets
utterly confused failing to recognise the file type and both erroring
out with "no ITS rules found" during merge_file and failing to extract
any translatable strings.
Also drop underscores which were previously processed by intltool.

This doesn't yet automatically replace the release version and date
in the appdata file, but neither did the old build.

Note: while this slightly improves the situation, meson’s aegisub-pot
target is still missing many strings. make_pot.sh should be used.
This aligns with the specification change of AppData metadata.
This together with two cherry-picked  commit (2716cf1, 932b04d) should resolve TypesettingTools#215.
@EL-File4138
Copy link
Contributor Author

Understood, do you think it's ready to be merged now?

@arch1t3cht arch1t3cht merged commit 3a07376 into TypesettingTools:master Dec 21, 2024
5 checks passed
@EL-File4138 EL-File4138 deleted the appdata-fix branch December 22, 2024 05:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Packaging: Lacking of AppData.xml file installation
3 participants