|
File Extensions |
.json |
|
API Extension |
json |
|
Import |
Yes |
|
Export |
Yes |
|
Plural forms support |
No |
|
Description support |
Yes |
|
Format options These options that can be specified when a file is uploaded and/or downloaded. Depending on the upload/download method (API, CLI, Repo sync etc.), they can be specified in query parameters |
No |
Google provides internationalization support for Chrome extensions. Localized strings for Chrome extensions are stored in a .JSON file often named messages.json. Chrome JSON files have a slightly different structure than .JSON files used for localization on other platforms. For Chrome JSON, strings that need translation are placed in the sub-key message nested under each unit key-value pair. A description may also be added to each key-value pair.
AI chatbots can be very effective at generating a list of keys from a .JSON file.
Code Sample
{
"boolean_key": {
"message": "--- true\n"
},
"empty_string_translation": {
"message": ""
},
"key_with_description": {
"message": "Check it! Key has a description! (In some formats)",
"description": "I'm a very important description for this key!"
},
"key_with_line-break": {
"message": "This translations contains\na line-break."
},
"nested.deeply.key": {
"message": " I'm nested deeply."
},
"nested.key": {
"message": "This key is nested inside a namespace."
},
"null_translation": {
"message": null
},
"sample_collection": {
"message": "---\n- first item\n- second item\n- third item\n"
},
"simple_key": {
"message": "I am a simple key with a simple message."
},
"unverified_key": {
"message": "Not yet verified waiting for it. (In some formats we also export this status)"
}
}