Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiple entries: Allow specifying language for the original name and support translations to other languages #10

Open
riipah opened this issue Jan 13, 2015 · 0 comments
Labels
adding/editing entries Adding/Editing entries (artists, songs, albums, tags, song lists, events) complexity: high 7 to 30 days of work (or longer), consider splitting content: entry-languages Entry languages data-field feature request globalization Globalization, internationalization, locales, timezones priority: low Issues/Tasks that are not so important translation Translations to other languages UX/usability UX (User Experience): Methods for improving the usablitiy

Comments

@riipah
Copy link
Member

riipah commented Jan 13, 2015

Currently titles can only be translated to 4 "content language selection" presets: Non-English, Romanized, English and Undefined (used for aliases). There's demand to support translations into other languages as well, for example German and Russian, or a Japanese title could be translated into Chinese.

First step is to allow specifying the exact language for the "non-English" name. This could be done similar to lyrics: there's fixed fields for original name and Romanization, plus variable number of fields for translations. For entry titles, aliases should be kept separate from translations of the primary name.

I think it's best to start with mapping those new language options to the current content language selection. This would still allow only English translation to be sorted and displayed in listings, but it'd be an improvement compared to current state, and would prepare the way for further improvements.

  • Edit view: change current primary name editor to similar to lyrics. Original name, Romanized name, translations. Language can be selected (from dropdown) for original name and translations. Language options are identical to lyrics, including other/unknown.
    • Editing for aliases will remain as it is.
  • Song page: all translations and aliases, including original and Romanized will be shown. First name to be shown is chosen like it's done now.
  • Translations other than English will be treated like aliases for now. They cannot be used for sorting or as display name.

TODO: is there need to specify translations for aliases? This could be used to hide/show translations of aliases based on user's language setting. It would also enable varying artist name (with translations) per album/song (see VocaDB/community#68).

@riipah riipah added enhancement globalization Globalization, internationalization, locales, timezones labels Jan 13, 2015
@riipah riipah changed the title Support for entry translations to arbitrary cultures Allow specifying language for the original name and support for translations to other languages Sep 15, 2016
@riipah riipah changed the title Allow specifying language for the original name and support for translations to other languages Allow specifying language for the original name and support translations to other languages Sep 15, 2016
@riipah riipah added the complexity: high 7 to 30 days of work (or longer), consider splitting label Oct 26, 2017
@ycanardeau ycanardeau added this to the Backlog milestone Nov 19, 2020
@dset0x dset0x added the priority: low Issues/Tasks that are not so important label Jan 23, 2021
@andreoda andreoda added the translation Translations to other languages label Jan 30, 2021
@andreoda andreoda added UX/usability UX (User Experience): Methods for improving the usablitiy adding/editing entries Adding/Editing entries (artists, songs, albums, tags, song lists, events) labels Apr 21, 2023
@andreoda andreoda removed this from the Backlog milestone Apr 26, 2023
@andreoda andreoda added the content: entry-languages Entry languages data-field label Mar 6, 2024
@andreoda andreoda changed the title Allow specifying language for the original name and support translations to other languages Multiple entries: Allow specifying language for the original name and support translations to other languages Dec 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
adding/editing entries Adding/Editing entries (artists, songs, albums, tags, song lists, events) complexity: high 7 to 30 days of work (or longer), consider splitting content: entry-languages Entry languages data-field feature request globalization Globalization, internationalization, locales, timezones priority: low Issues/Tasks that are not so important translation Translations to other languages UX/usability UX (User Experience): Methods for improving the usablitiy
Projects
Development

No branches or pull requests

5 participants