No funded issue found.
Check out the
Issue Explorer Be the OSS Funding you wish to see in the world.
Looking to fund some work? You can submit a new Funded Issue
Workers Auto Approve
React i18n, with output usable for translators
Since the start this repo was developed with i18n in mind. It uses [react-i18next](https://react.i18next.com/) as a framework, with 99% of all strings wrapped in a translatable form, e.g https://github.com/polkadot-js/apps/blob/master/packages/app-accounts/src/Overview.tsx#L57
(In the above we are indicating 99%, since there are some floating string we def. missed - they should really be included as well, however not in the scope here)
Having strings translatable, without being extracted however does not quite help. In the same vein having strings extracted but without proper categorization to help along translators, also doesn't help. And this is the scope of this issue...
In short: we want to have the strings extracted (preferably via toolset) and ordered and made available in such a way that translators can actually perform their tasks without friction.
For background, this was the original issue logged - https://github.com/polkadot-js/apps/issues/1421 (We split this one out to give clarity to the requirements and attach a bounty to it)
Some initial work has been done in https://github.com/polkadot-js/apps/pull/1478
The end-result is promising, but we are sitting at step 1 - we have the data, but it is overwhelming. Rather instead of a list of a bunch of strings https://github.com/polkadot-js/apps/pull/1478/files#diff-b9def2b395fcf7945c9622f2afb43520R8 we would like something better.
- With the i18next or react-i18next toolsets, exact the translation strings (like attempted above)
- Unlike the above output, at the very least we would like this -
- (a) containing all the strings (the above does that)
- (b) categorized at the very least on a per-app basis (it could be more granular, but not up to component level, since translators would typically look at a single screen to see where things fit)
There really is no specific tools that "must be used" here. Rather, anything that meets the goals can be used - be it the tools used in the above attempt, any additional i18next extraction tools (discarding the above attempt) or a combination thereof with scripts. As long as the output is manageable for translation and can be used inside the UI.
Any additional comments/suggestions as to how to make it easy for the "end-user" (being the translator) would also be appreciated.
Setup your profile
Tell us a little about you:
No results found for
Type to search skills..
Required [[totalcharacter]] / 240
Are you currently looking for work?
[[ option.string ]]
Setup your profile
Our tools are based on the principles of earn (💰), learn (📖), and meet (💬).
Select the ones you are interested in. You can change it later in your settings.
I'm also an organization manager looking for a great community.
Enable your organization profile
Gitcoin products can help grow community around your brand. Create your tribe, events, and incentivize your community with bounties. Announce new and upcoming events using townsquare. Find top-quality hackers and fund them to work with you on a grant.
These are the organizations you own. If you don't see your organization here please be sure that information is public on your GitHub profile. Gitcoin will sync this information for you.
Select the products you are interested in:
Out of the box you will receive Tribes Lite for your organization. Please provide us with a contact email: