translation guidelines and gitlocalize

[aspina7]

rOpenSci have produced guidelines around how they to localisation and translation might be worth taking a look and producing similar documentation for this our new infrastructure

[aspina7]

As can see in the readme of this package they also create a tracker of completion using gitlocalize - which may be worth looking at

[aspina7]

also crosslinking to this #124 on the {i18n} package - which I dont think will be necessary anymore

[aspina7]

and these R4EPI/sitrep#314 on #129 cleaning up how we store and translate datasets

[aspina7]

as well as considering how we should do this for package websites R4EPI/sitrep#312

[ntluong95]

@aspina7 @nsbatra I just had a quick look on links you sent, I think the guideline document in the first comment recommending to use {babeldown} and {babelquarto} package, things we are using. The gitlocalize looks interesting and can be investigated later

[aspina7]

yes @ntluong95 - I was just saying that we should plan to have one document on github (e.g. a wiki or a readme) or website.
In this document we explain the whole workflow of translations for websites(books / case studies), courses/tutorials and datasets.
This would be done in the same style as ropensci document linked above.

[ntluong95]

I see your point @aspina7. Could be a wiki or readme as the easiest option. Will keep it open to work in the near future