microsoft / microsoft/monaco-editor

[Bug] pt-BR translation is just a file full of nulls

Open
#5,127 1 comment 0 reactions 1 assignee View on GitHub

@hediet is already working on this.

Since Nov 24, 2025.

bug i18n
Dominant language
JavaScript
Stars
46.8k
Forks
4.1k
Avg merge
17h 58m
Merged PRs (30d)
1

Description

Reproducible in vscode.dev or in VS Code Desktop?
  • Not reproducible in vscode.dev or VS Code Desktop
Reproducible in the monaco editor playground?
Monaco Editor Playground Link

n/a

Monaco Editor Playground Code
n/a
Reproduction Steps

The localization instructions for Monaco say to load the appropriate nls script before the Monaco script, using a tag like:

<script src="path/to/monaco-editor/esm/nls.messages.de.js"></script>

However in the case of nls.messages.pt-br.js, I noticed the file is significantly smaller than all the others. Opening it shows the file is just full of null, e.g.:

globalThis._VSCODE_NLS_MESSAGES=[null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,
null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,
null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null
,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null...

Presumably something has gone wrong with the generation of this file.

Actual (Problematic) Behavior

No content in nls.messages.pt-br.js

Expected Behavior

Appropriate translations to be present in nls.messages.pt-br.js

Additional Context

Reproduces with v0.55.1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.