You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 25, 2018. It is now read-only.
In the last hangout of the intl wg we talked about "how to store & implement translations of error messages" and I felt like this issue is the perfect to prepare a guide on "how to write a package with i18n support" with Node.js being the first adopter of the best-practices. Now we have been wondering where to put those suggestions. Of course we could just place a markdown file in the intl-repo but then it might fall out of any translation work done.
Where would you put this sort of information?
The text was updated successfully, but these errors were encountered:
Closing as this repository is dormant and likely to be archived soon. If this is still an issue, feel free to open it as an issue on the main node repository.
Hello Docs team 👋
In the last hangout of the intl wg we talked about "how to store & implement translations of error messages" and I felt like this issue is the perfect to prepare a guide on "how to write a package with i18n support" with Node.js being the first adopter of the best-practices. Now we have been wondering where to put those suggestions. Of course we could just place a markdown file in the intl-repo but then it might fall out of any translation work done.
Where would you put this sort of information?
The text was updated successfully, but these errors were encountered: