Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
I'm creating the new language translation file for Western Armenian, which is totally different from Eastern Armenian and more than 6 mln people are writing and speaking it. After the first commit, I'll add/edit to have the ful translation
Resolves
Proposed Changes
Describe what this Pull Request does
Checklist for updating translations
There are two situations in which we create manual PRs to update translations:
1. Updating translations manually
> npm run pull:editor> npm run pull:www> npm run testeditor/<resource>/<lang code>.jsonAdding a language
Edit
src/supported-locales.mjs:localesconstrtlLocalesCheck if the new language uses a country code
src/supported-locales.mjs:localeMap. Format is'<W3C HTML browser locale string>': '<Transifex ICU locale string>'.tx/config:lang_maplist. Format is<Transifex ICU locale string>:<W3C HTML browser locale string>txcli;.tx/configwill eventually be deprecatedEdit
src/index.js:localeDataarrayCheck if locale is in
react-intlreact-intl:src/supported-locales.mjs:customLocales, add entry with parent set to areact-intllocalesrc/index.js:localeData, add entry for parent localeUpdate translations per the "Updating translations" section above
Confirm that we see changes to:
src/supported-locales.mjssrc/index.js.tx/config(if language needed a new locale)editor/<resource>/<lang code>.jsonBump minor version number in
package.jsonAdd language po files to scratchr2_translations
scratchr2_translations/legacywithtx pull -l <locale>and check in changesAdd language to scratchr2 settings
settings/base.pywith the new languageAfter scratch-l10n update is published:
package.json, update the version of the scratch-l10n dependency to the version number you used aboveBlockly.ScratchMsgs.locales["<LOCALE CODE>"]is added tomsg/scratch_msgs.js