I was wondering the same thing.
It looks like transifex supports regional subtags, but unless I missed seeing them, not script (eg. cyrillic / latin) or variant (eg. de-DE-1901) subtags.
http://www.rfc-editor.org/rfc/bcp/bcp47.txt
Maybe it’s only because nobody has done any yet?
according to the given rfc the following tags would be correct?
de-formal
de-informalMy question is does transifex support that?
We usually get rule information from unicode.org.
When we add support for a language we follow the BCP47 standard. The multiple language locales are based on region subtags.
Seeing “based on region subtags” doesn’t look hopeful (if it means only). But maybe the CLDR means there’s a chance.
Do you see “formal / informal” anywhere in that?
I don’t think so. I couldn’t find anything in the language settings of my Transifex test project that relates to language variations. This is all there is when I’m searching for German:
Yes, that’s what I see when I look around, some language-region translations but not any language-script etc. translations. (with maybe Chinese being an exception?)
@meglio
During your travels in web land have you found a way to specify cyrillic vs. latin?
Sorry I don’t understand the question. May you reformulate in other words please?
From what I see in transifex, language-region translations are supported. eg.
Portuguese (Portugal)
Portuguese (Brazil)
Spanish (Argentina)
Spanish (Latin America)
Spanish (Ecuador)
Spanish (Mexico)
Spanish (Spain)
But I don’t see anything like
Ukraine (Latin)
Ukraine (Cyrillic)
or
German (Formal)
German (Informal)
I noticed that your forum uses Cyrillic so I was wondering if you knew of a way to have a choice as to which variant to use.
Thanks for such a detailed explanation. Now I see what you mean 
The answer is NO - Ukrainian and Russian are single languages with no variations available there.
There are of course cases with huge regional differences, but those have never been formalized.
The number of percentage of world’s population speaking Ukrainian or Russian is declining, so I don’t think such a sectioning will ever happen.
语言的正式/非正式变体在具有T-V区分的语言（如德语或匈牙利语）中非常重要。使用与受众不匹配的变体会疏远他们；如果 Discourse 所属的网站使用了另一种选项，情况会更糟。看起来，自从这次对话发生以来，Discourse 已从 Transifex 切换到 Crowdin，所以现在处理起来可能更容易了？
关于语言名称，符合标准的做法是使用BCP-47 专用子标签，例如 de_DE-x-formal。我看到德语现在有一个插件，但这似乎是一种非常 hacky 的方法，我希望能看到一种更简洁的方法（我个人有兴趣拥有一个非正式的匈牙利语变体）。
与此同时，Discourse 已迁移到 Crowdin 来处理界面语言翻译。我找不到任何关于正式和非正式变体的参考，但他们确实有区域变体。我想知道这些区域变体是由系统固定的，还是项目管理员可以创建新的。如果管理员可以，那么就可以创建例如匈牙利语（非正式）。该软件甚至可以在变体之间自动填充未翻译的字符串，因此翻译人员只需专注于正式和非正式版本不同的句子。
如果这个过程在技术上可行，那么创建正式/非正式变体就可以遵循与请求新语言相同的流程。
作为一种具有正式和非正式版本的多种语言的使用者，我同意这里所有请求此功能的人（免责声明：@Tgr 和我来自同一个项目）。找到英语的等价物很难，但想象一下，Discourse 界面会以伊丽莎白女王宫廷仆人的语气和语域来称呼每个人。
当前“流程”令人烦恼的是，没有通用的标准。不同的语言被翻译成正式或非正式，取决于第一个翻译者在开始翻译时决定做什么。