xgqt / cpp-NickvisionTagger

An easy-to-use music tag (metadata) editor

Home Page:https://flathub.org/apps/details/org.nickvision.tagger

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Tagger

An easy-to-use music tag (metadata) editor

Features

  • Edit tags and album art of multiple files, even across subfolders, all at once
  • Support for multiple music file types (mp3, ogg, flac, wma, and wav)
  • Convert filenames to tags and tags to filenames with ease

Installation

Download on Flathub

Chat

Join our room

Screenshots

MainWindow OpenFolder AdvancedSearch TagEditing DarkMode

Translating

Everyone is welcome to translate this app into their native or known languages, so that the application is accessible to everyone.

To translate the app, fork the repository and clone it locally. Make sure that meson is installed. Run the commands in your shell while in the directory of repository:

meson build
cd build
meson compile org.nickvision.tagger-pot

Or, if you are using GNOME Builder, build the app and then run in the Builder's terminal:

flatpak run --command=sh org.gnome.Builder
cd _build
meson compile org.nickvision.tagger-pot

This would generate a NickvisionTagger/po/org.nickvision.tagger.pot file, now you can use this file to translate the strings into your target language. You may use Gtranslator or poedit if you do not know how to translate manually in text itself. After translating (either through tools or directly in text editor), make sure to include the required metadata on the top of translation file (see existing files in NickvisionTagger/po/ directory.)

One particular thing you should keep in mind is that some strings in this project are bifurcated into multiple strings to cater to responsiveness of the application, like:

msgid ""
"If checked, the currency symbol will be displayed on the right of a monetary "
"value."

You should use the same format for translated strings as well. But, because all languages do not have the same sentence structure, you may not need to follow this word-by-word, rather you should bifurcate the string in about the same ratio. (For examples, look into translations of languages which do not have a English-like structure in NickvisionTagger/po/)

Put your translated file in NickvisionTagger/po directory in format <LANG>.po where <LANG> is the language code.

Put the language code of your language in NickvisionTagger/po/LINGUAS (this file, as a convention, should remain in alphabetical order.)

Add information in NickvisionTagger/po/CREDITS.json so your name will appear in the app's About dialog:

"Jango Fett": {
    "lang": "Mandalorian",
    "email": "jango@galaxyfarfar.away"
}

If you made multiple translations, use an array to list all languages:

"C-3PO": {
    "lang": ["Ewokese", "Wookieespeak", "Jawaese"],
    "url": "https://free.droids"
}

To test your translation in GNOME Builder, press Ctrl+Alt+T to open a terminal inside the app's environment and then run:

LC_ALL=<LOCALE> /app/bin/org.nickvision.tagger

where <LOCALE> is your locale (e.g. it_IT.UTF-8.)

Commit these changes, and then create a pull request to the project.

As more strings may be added in the application in future, the following command needs to be ran to update all the .po files, which would add new strings to be translated without altering the already translated strings. But, because running this command would do this for all the languages, generally a maintainer would do that.

meson compile org.nickvision.tagger-update-po

Dependencies

Special Thanks

About

An easy-to-use music tag (metadata) editor

https://flathub.org/apps/details/org.nickvision.tagger

License:GNU General Public License v3.0


Languages

Language:C++ 98.5%Language:Meson 1.5%