Repository navigation
docs(reference): translate Inbox and Campaigns APIs to Russian and Portuguese (1MSG-113) - #18
Merged
Merged
Conversation
…rtuguese (1MSG-113) Adds inbox.ru.json, inbox.pt.json, campaigns.ru.json and campaigns.pt.json. Only summary and description texts differ from the English specs; paths, operationIds, tags, schemas and examples are unchanged, so method URLs stay the same. The reference README lists the new files and notes that the API sync does not update translations. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What
Russian and Portuguese versions of the Inbox and Campaigns API references:
reference/inbox.ru.json,reference/inbox.pt.json— 107 textsreference/campaigns.ru.json,reference/campaigns.pt.json— 228 textsOnly
summaryanddescriptionare translated: the API overviews, methods, parameters, response fields and the webhook sections. Everything else is identical to the English files. That covers paths,operationIds, tag names, schemas, enums, examples and code. The site pairs translated methods with the English ones by method and path, so method URLs do not change. The checks confirmed that the JSON structure matches the English spec and that every field name, code value, number and format survived.Platform menu labels such as
Settings → Developer → API Settingsstay in English.reference/README.mdnow lists the four files and explains how they relate to the sync.Keep in mind: the translations lag behind the API
inbox.jsonandcampaigns.jsonare regenerated by thebot/sync-specspull request after each API release, and the sync does not touch the translations:/ru/docsand/br/docsuntil it is translated.🤖 Generated with Claude Code