which translations to maintain? #3460
Replies: 2 comments 14 replies
-
I think so. When new Core users come online, they'll notice their language isn't fully supported and potentially come to help. This maybe isn't ideal, but it might do better at encouraging participation than not having the language supported at all.
I think it works okay but it's not super accessible, and it's my belief that accessibility is at the root of participation. On that note, I was thinking about this recently and decided to reach out to Transifex to see what it would cost to use their service. This is the response I was given:
|
Beta Was this translation helpful? Give feedback.
-
None, because updates are scripted. The reason for removing untranslated dialects is because it is confusing.
I'm neutral on this.
I don't mind moving to transifex if translators believe that that gives a better experience.
I feel that we cannot include (b) here, because maybe there aren't many users because there is no complete translation. So I think that it's better to make decisions based on how large the total population is we can reach with a translation. |
Beta Was this translation helpful? Give feedback.
-
From a quick look through src/qt/locale, many languages we currently have "support" for are 50-90% untranslated. I have several general questions:
(I have been checking using https://what-is-dogecoin.com/nodes/ but don't know how accurate it is)
Beta Was this translation helpful? Give feedback.
All reactions