International considerations
Stay organized with collections
Save and categorize content based on your preferences.
In non-English-speaking locales, there might be more than one local language. In
your feeds, though, we require at least two languages: the primary language(s)
spoken in that location, referred to here as "the local language," and English.
We ask for English for the following reasons:
- It's likely that a number of people in that country also speak English.
- Many of our internal systems are designed in English. If the feeds are in
English as well, this makes it easier for us to troubleshoot and debug.
For example, the primary language in Japan is Japanese, so we require the data
in Japanese and with English translations. However, if a candidate or party
doesn't have official names in English (or the local language), don't add your
own English (or local language) translations. We only accept official names both
in English and the local language.
In countries where there are multiple local languages, we need at least the
primary local language first. If the official names are available in any
additional languages, you can then provide those names.
Content in English
All single-string Name
fields, such as Party
, need to be in English. All
InternationalizedText
fields need to include a Text
instance with an English
language translation or transliteration. These include, but aren't limited to,
the names for the following entities:
Contests
Office
and ReportingUnit
Party
and Coalition
Person
and Candidate
Exceptions
Abbreviations, when allowed or required, must be abbreviated in the local
language. For example, the Worker's Party in Brazil would have Name
values in
English and Portuguese, but the InternationalizedAbbreviation
field would be
set to PT
, for "Partido dos Trabalhadores."
Local language content
When available provide translations for InternationalizedText
fields,
including but not limited to names, in the local language. Additional notes are
included for each entity.
Election
and Contest
- Translate these, but see the election contest and event naming
guidelines. The expectation is that names of contests and events use
language and terminology that people from that country would expect to
see, for example Lok Sabha election as opposed to Lower House election.
- Ballot measure contests have their special rules highlighted separately.
GpUnit
Party
and Coalition
- For party names, do what makes sense for speakers of the language
regarding translation and transliteration. For example "Indian national
congress" should be translated to Hindi as "भारतीय राष्ट्रिय काङ्ग्रेस"
. Whereas "Bharatiya Janata Party" should be transliterated in Hindi as
"भारतीय जनता पार्टी".
- For party abbreviations or aliases, if it makes sense to someone who
lives in the country and whose first language then it is fine to include
these in multiple languages.
Person
- Don't include local translations of candidate names or the names of
other people unless those translations represent a transliteration into
a different character set. For example, for Japanese Prime Minister
Shinzo Abe, include the
Person
FullName
element like the following:
<FullName>
<Text language="en">Shinzo Abe</Text>
<Text language="ja">安倍晋三</Text>
</FullName>
- Additionally names of people should be included in all expected
languages for a given country. In practice this means that it is
expected that names may be repeated, for example:
<FullName>
<Text language="en">Jeroen van Wijngaarden</Text>
<Text language="nl">Jeroen van Wijngaarden</Text>
</FullName>
Office
- Translate names of offices, but again use official sources if a name is
available in multiple languages. For example "Member of Lok Sabha"
instead of "Member of Lower House".
BallotMeasureContest
- Text fields for ballot measures and referenda, including titles,
shouldn't be translated as the text has a legal meaning. If this results
in not being able to deliver English that is fine.
- If there are officially available translations they should be included.
LanguageStrings
Language strings are used in
InternationalizedText
and
InternationalizedUri
to
indicate the language of a text or URI.
Attributes
The following table describes the attributes for LanguageString
:
Attribute |
Required? |
Type |
Description |
language |
Required |
language |
Identifies the language. Values for language come from
ISO 639, see the
Wikipedia page for
more detail. Some examples include the following:
en : English
fr : French
es : Spanish
zh : Chinese
ja : Japanese
ko : Korean
|
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-05-13 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-05-13 UTC."],[[["\u003cp\u003eElection data feeds require content in English and the primary local language(s) to support both international users and internal system processes.\u003c/p\u003e\n"],["\u003cp\u003eOfficial names for entities like contests, offices, parties, and candidates must be provided in both English and the local language, without custom translations.\u003c/p\u003e\n"],["\u003cp\u003eWhile abbreviations should be in the local language, single-string name fields and internationalized text fields require English translations or transliterations.\u003c/p\u003e\n"],["\u003cp\u003eLocal language content is encouraged for most entities, prioritizing familiar terminology over literal translations, but ballot measure texts should generally remain untranslated due to their legal significance.\u003c/p\u003e\n"],["\u003cp\u003eCandidate and person names should include transliterations into different character sets if available but avoid local translations unless they represent such transliterations.\u003c/p\u003e\n"]]],[],null,["# International considerations\n\nIn non-English-speaking locales, there might be more than one local language. In\nyour feeds, though, we require at least two languages: the primary language(s)\nspoken in that location, referred to here as \"the local language,\" and English.\nWe ask for English for the following reasons:\n\n- It's likely that a number of people in that country also speak English.\n- Many of our internal systems are designed in English. If the feeds are in English as well, this makes it easier for us to troubleshoot and debug.\n\nFor example, the primary language in Japan is Japanese, so we require the data\nin Japanese and with English translations. However, if a candidate or party\ndoesn't have official names in English (or the local language), don't add your\nown English (or local language) translations. We only accept official names both\nin English and the local language.\n\nIn countries where there are multiple local languages, we need at least the\nprimary local language first. If the official names are available in any\nadditional languages, you can then provide those names.\n\nContent in English\n------------------\n\nAll single-string `Name` fields, such as `Party`, need to be in English. All\n`InternationalizedText` fields need to include a `Text` instance with an English\nlanguage translation or transliteration. These include, but aren't limited to,\nthe names for the following entities:\n\n- `Contests`\n- `Office` and `ReportingUnit`\n- `Party` and `Coalition`\n- `Person` and `Candidate`\n\nExceptions\n----------\n\nAbbreviations, when allowed or required, must be abbreviated in the local\nlanguage. For example, the Worker's Party in Brazil would have `Name` values in\nEnglish and Portuguese, but the `InternationalizedAbbreviation` field would be\nset to `PT`, for \"Partido dos Trabalhadores.\"\n\nLocal language content\n----------------------\n\nWhen available provide translations for `InternationalizedText` fields,\nincluding but not limited to names, in the local language. Additional notes are\nincluded for each entity.\n\n- `Election` and `Contest`\n\n - Translate these, but see the election contest and event naming guidelines. The expectation is that names of contests and events use language and terminology that people from that country would expect to see, for example Lok Sabha election as opposed to Lower House election.\n - Ballot measure contests have their special rules highlighted separately.\n- `GpUnit`\n\n- `Party` and `Coalition`\n\n - For party names, do what makes sense for speakers of the language regarding translation and transliteration. For example \"Indian national congress\" should be translated to Hindi as \"भारतीय राष्ट्रिय काङ्ग्रेस\" . Whereas \"Bharatiya Janata Party\" should be transliterated in Hindi as \"भारतीय जनता पार्टी\".\n - For party abbreviations or aliases, if it makes sense to someone who lives in the country and whose first language then it is fine to include these in multiple languages.\n- `Person`\n\n - Don't include local translations of candidate names or the names of other people unless those translations represent a transliteration into a different character set. For example, for Japanese Prime Minister Shinzo Abe, include the `Person` `FullName` element like the following:\n\n \u003cFullName\u003e\n \u003cText language=\"en\"\u003eShinzo Abe\u003c/Text\u003e\n \u003cText language=\"ja\"\u003e安倍晋三\u003c/Text\u003e\n \u003c/FullName\u003e\n\n - Additionally names of people should be included in all expected languages for a given country. In practice this means that it is expected that names may be repeated, for example:\n\n \u003cFullName\u003e\n \u003cText language=\"en\"\u003eJeroen van Wijngaarden\u003c/Text\u003e\n \u003cText language=\"nl\"\u003eJeroen van Wijngaarden\u003c/Text\u003e\n \u003c/FullName\u003e\n\n- `Office`\n\n - Translate names of offices, but again use official sources if a name is available in multiple languages. For example \"Member of Lok Sabha\" instead of \"Member of Lower House\".\n- `BallotMeasureContest`\n\n - Text fields for ballot measures and referenda, including titles, shouldn't be translated as the text has a legal meaning. If this results in not being able to deliver English that is fine.\n - If there are officially available translations they should be included.\n\nLanguageStrings\n---------------\n\nLanguage strings are used in\n[`InternationalizedText`](/civics-data/reference/internationalized-text) and\n[`InternationalizedUri`](/civics-data/reference/internationalized-uri) to\nindicate the language of a text or URI.\n\n### Attributes\n\nThe following table describes the attributes for `LanguageString`:\n\n| Attribute | Required? | Type | Description |\n|------------|-----------|------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| `language` | Required | `language` | Identifies the language. Values for `language` come from ISO 639, see the [Wikipedia page](https://en.wikipedia.org/wiki/ISO_639) for more detail. Some examples include the following: - `en`: English - `fr`: French - `es`: Spanish - `zh`: Chinese - `ja`: Japanese - `ko`: Korean |"]]