Open SachaG opened 4 months ago
I think for starters I'm going to do what you suggested and use our "regular" non-Tokyodev strings as fallbacks, so that only the strings specific to TokyoDev remain in the repo.
OK so going forward we will first load en-US and ja-JP locales from https://github.com/Devographics/locale-en-US and https://github.com/Devographics/locale-ja-JP; then load the same locales from this current repo; and merge everything down so that the TokyoDev strings take priority over the Devographics strings.
OK, I've added the files that need to be translated:
https://github.com/tokyodev-inc/tokyodev-devographics/tree/main/locales/locale-ja-JP
tdquestions.yml
: contains the strings for all questions. I didn't split them by survey because there's a lot of overlap. td2024.yml
: contains strings used by the 2024 survey specifically (such as the FAQ)tdresults.yml
: contains strings used by the published results for all surveystd2024.yml
: will also contains strings used by the 2024 results specificallytd2023.yml
: if we want to translate last year's results as wellI've passed td2024.yml
and tdquestions.yml
off for review. We need to make sure if anything gets changed in the interim in those keys, it gets flagged for review.
Yes, I'll make sure I make separate commits for any locale files to make that easier to track.
For consistency reasons with how other surveys work I'm going to rename tdquestions.yml
to tokyodev.yml
, but I'm not changing the contents.
Oh one thing to note is that there will probably be keys that need to be translated back in the main locale-ja-JP
repo used by all surveys (https://github.com/Devographics/locale-ja-JP), and not the TokyoDev-specific files.
Added a couple items to translate: