No way to differentiate be-1959acad and be-tarask for Belarusian

Asked by this account is no longer used

I there a way to differenciate different standards of the Belarusian language in Launchpad?

I want to explicitly mark my translation as Academic Belarusion (‘be-1959acad’ tag), to prevent it from being from being confused with the texts written in Classical Belarusian (‘be-tarask’). Is it possible?

Currently most projects in Launchpad seem to use Classical Belarusian under the ‘be’ tag, so if I were to add translations in Academic Belarusian, they would be inconsistent with the others.

Differences between the two standards are not merely orthographic, but also lexical. Some of the differences include:
* Academic orthography shows etymological palatisation (‘softening’), while Classical orthography shows assimilative palatisation (e.g. здарэнне/zdarennie — здарэньне/zdareńnie)
* Academic Belarusian prefers loanwords from Russian, while Classical Belarusian tends to borrow more from Polish and West-European languages (e.g. сімвал/simvał cf. Rus. символ/simvol — сымбаль/symbal cf. Polish symbol)

Both have a strict set of rules, and, in general, text in one standard will not be considered correct according to the other norm. So mixing these two is not a good idea.

Wikipedia, for instance, has 2 editions (be.wikipedia.org corresponds to ‘be-1959acad’, while be-x-old corresponds to ‘be-tarask’; in the past, be.wikipedia.org corresponded to ‘be-tarask’).

Question information

Language:
English Edit question
Status:
Answered
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
j.c.sackett (jcsackett) said :
#1

Launchpad only really has support for languages with ISO-639 language codes (specifically ISO-639-1 and ISO-639-3).

A be@1959acad variant could be added, but we'll need the plural form info for it (https://help.launchpad.net/Translations/PluralForms).

Before doing that though, it's worth considering if many people likely to make translations in 'be@1959acad' or use these translations, given the community has adopted 'be-tarask' for 'be' translations?

Can you help with this problem?

Provide an answer of your own, or ask this account is no longer used for more information if necessary.

To post a message you must log in.