alphatownsman commented 3 months ago

Language Support in NeoDB

Supported UI Languages

NeoDB supports these UI languages

English
Simplified Chinese
Traditional Chinese

User may specify one of them as their primary UI language, it applies to

UI text
display value for enum fields in catalog (e.g. genre)
post templates (e.g. "finished reading XYZ")
post language in ActivityPub message (to be implement later)

Supported Catalog Languages

Primarily based on IETF BCP 47 language tags, NeoDB supports commonly used macro languages in ISO 639-1 (e.g. en, jp) as main list, with a small set of additional subtags based on use case.

for the following categories, users may specify title and description in those macro languages, plus a small set of region subtags in ISO 3166-1, e.g. zh-hk

Work (book)
Movie
TV Show / Season
Game
Album
Performance

for the following categories, users may specify its main written language in those macro languages, plus a small set of script subtags is defined in ISO 15924, e.g. zh-hans

Edition (book)

for the following categories, users may specify its main spoken languagein those macro languages, plus a small set of script subtags is defined in ISO 639-3, e.g. nan, yue

Movie
TV Show / Season
Podcast
Performance

the following field/category should support multiple languages, but requires much larger change, and will be planned in the future

People

Language support in external sites

These sites supports a wide range of languages

TMDB
Steam
Apple Music

These sites supports title mostly in English, but may have alternative titles in multiple languages

IMDB
IGDB
BGG

These sites supports title in single language

Google
Goodreads
Bandcamp
Spotify
RSS

These sites supports mostly Chinese, but may have alternative titles in multiple languages

Douban
BooksTW
Bangumi

Configuration

NEODB_PREFERRED_LANGUAGES can be set in .env as a comma separated list of macro languages, default will be en,zh,jp,kr, its value will be used in a few ways:

the first language in this list that's among Supported UI Languages will be used as fallback when language is not detected from either user preference or HTTP header. if none of them is matched, default language will be en
when getting data from external site (e.g. TMDB), this value will be used to determine variants of metadata to query
when generating popular items (/discover), this value will be used as filter
when editing catalog item, these languages will be at the top of list

NEODB_LANGUAGE will be deprecated, and for backward compatibility, it will be used as NEODB_PREFERRED_LANGUAGES if NEODB_PREFERRED_LANGUAGES is not specified.

Note

the supported lists of languages and fields are far from extensive at the moment, we aim to stablize the implementation first, then gradually expand.

contribution for additional translations is very much welcomed.

Reference

https://en.wikipedia.org/wiki/IETF_language_tag

https://www.iana.org/assignments/language-subtag-registry/language-subtag-registry

wiki-me commented 3 months ago

Does this include filtering reviews in other languages the user don't read? that seems like a valuable feature. or at least having the option to auto translate them.