A graphical Program to create and edit AppStream files
Go to file
JakobDev 0a7747a899
ci/woodpecker/tag/sourceforge-deploy Pipeline failed Details
ci/woodpecker/tag/pypi-deploy Pipeline failed Details
Update to Version 7.1
2023-09-14 12:19:04 +02:00
.github/workflows Fix missing renames 2023-03-13 11:16:25 +01:00
.woodpecker Update to Version 7.1 2023-09-14 12:19:04 +02:00
deploy Update to Version 7.1 2023-09-14 12:19:04 +02:00
jdAppStreamEdit Update to Version 7.1 2023-09-14 12:19:04 +02:00
screenshots Update Screenshots 2023-03-10 16:24:36 +01:00
tools Rework About Dialog 2023-05-31 14:19:07 +02:00
.editorconfig Add more settings for saving file 2023-03-09 11:35:14 +01:00
.gitattributes Fix typo in .gitattributes 2023-05-31 14:36:10 +02:00
.gitignore Add Windows Installer 2023-05-31 12:16:57 +02:00
BuildBackend.py Compile all .ui files and switch to pyproject.toml 2023-03-10 10:13:44 +01:00
CONTRIBUTING.md Update Links 2023-03-10 10:49:24 +01:00
LICENSE Update LICENSE 2023-03-09 16:50:05 +01:00
MANIFEST.in Compile all .ui files and switch to pyproject.toml 2023-03-10 10:13:44 +01:00
README.md Add Link to Sourceforge to Readme 2023-06-01 10:36:18 +02:00
install-unix-datafiles.py Try to integrate Unix datafiles into Weblate 2023-03-17 10:10:37 +01:00
jdAppStreamEdit.py Add Windows Installer 2023-05-31 12:16:57 +02:00
jdAppStreamEditExternalReleases.py Change Name to jdAppStreamEdit (Part 1) 2023-03-09 16:41:05 +01:00
pyproject.toml Prepare new Release 2023-05-31 15:08:30 +02:00
requirements.txt Add requirements.txt 2023-05-31 12:54:25 +02:00



A graphical Program to create and edit AppStream files


jdAppStreamEdit (previously known as jdAppdataEdit) allows you to easily create and edit AppStream (.appdata.xml or .metainfo.xml) files for your Application.


  • Easy to use
  • Full support for the Open Age Rating System (OARS)
  • The AppStream files are fully translatable
  • Releases can be imported from GitHub, GitLab, Gitea, Git Repos and NEWS files
  • You can view a preview in Gnome Software
  • You can use a existing .desktop file as template
  • Plugins



You can get jdAppStreamEdit from Flathub


Arch Users can get jdAppStreamEdit from the AUR


You can get Windows and AppImage Builds from Sourceforge


You can install jdAppStreamEdit from PyPI using pip:

pip install jdAppStreamEdit

Using this Method, it will not include a Desktop Entry or any other Data file, so you need to run jdAppStreamEdit from the Command Line. Use this only, when nothing else works.

From source

This is only for experienced Users and someone, who wants to package jdAppStreamEdit for a Distro. jdAppStreamEdit should be installed as a Python package. You can use pip or any other tool that can handle Python packages. You need to have lrelease installed to build the Package. After that, you should run install-unix-datafiles.py which wil install things like the Desktop Entry or the Icon in the correct place. It defaults to /usr, but you can change it with the --prefix argument. It also applies the translation to this files. You need gettext installed to run install-unix-datafiles.py.

Here's a example of installing jdAppStreamEdit into /usr/local:

sudo pip install --prefix /usr/local .
sudo ./install-unix-datafiles.py --prefix /usr/local


You can help translating jdAppStreamEdit on Codeberg Translate


jdAppStreamEdit is written in Python and uses PyQt6 as GUI toolkit. You should have some experience in both. You can run jdAppStreamEdit.pyto start jdAppStreamEdit from source and test your local changes. It ships with a few scripts in the tools directory that you need to develop.


This is the most important script. It will take all .ui files in jdAppStreamEdit/ui and compiles it to a Python class and stores it in jdAppStreamEdit/ui_compiled. Without running this script first, you can't start jdAppStreamEdit. You need to rerun it every time you changed or added a .ui file.


This script takes all .ts files and compiles it to .qm files. The .ts files are containing the translation source and are being used during the translation process. The .qm contains the compiled translation and are being used by the Program. You need to compile a .ts file to a .qm file to see the translations in the Program.


This regenerates the .ts files. You need to run it, when you changed something in the source code. The .ts files are contains the line in the source, where the string to translate appears, so make sure you run it even when you don't changed a translatable string, so the location is correct.


This regenerates the translation files in deploy/translations. these files contains the translations for the Desktop Entry and the AppStream File. It uses gettext, as it is hard to translate this using Qt. These files just exists to integrate the translation with Weblate, because Weblate can't translate the Desktop Entry and the AppStream file. Make sure you run this when you edited one of these files. YOu need to have gettext installed to use it.


This uses git to get a list of all Translators and writes it to jdAppStreamEdit/data/translators.json. This is used to display the translators in the About Dialog. You need git to run this script.


This read the Changelog from deploy/page.codeberg.JakobDev.jdAppStreamEdit.metainfo.xml, converts it to HTML and writes it to jdAppStreamEdit/data/changelog.html. This is used to display the Changelog in the About Dialog. You need appstream-python to be installed to use this script.