AdvPL UTF-8 to CP1252 Converter

What it does

When your agent uses it

• Right after an agent generates or edits a .prw or .tlpp file
• Fixing garbled accented characters when Protheus compiles a source file
• Converting a batch of AdvPL files to Windows-1252 before compilation

Example prompts

• “Convert src/orders.tlpp to CP1252 now that the endpoint is generated.”
• “Our Protheus build shows garbled characters in the new .prw files. Fix the file encoding.”
• “Convert every AdvPL file I changed today to Windows-1252 and verify the result.”

Requirements

• Bash with `iconv` on Linux or macOS, or PowerShell on Windows

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

1. 1ALWAYS use the provided scripts — NEVER attempt manual encoding conversion (e.g., Python, Node.js, or copying content to a new file).
2. 2Conversion is IN-PLACE — The script replaces the original file. The filename and extension do NOT change. A .tlpp file stays .tlpp, a .prw…
3. 3NEVER create files with .cp1252 extension — There is no such convention. Files keep their original extension (.prw, .prg, .tlpp, .prx…
4. 4NEVER create backup copies or duplicate files — No .bak, .orig, .utf8, .old, or any other copy. Only the converted file must exist.
5. 5NEVER rename files during conversion — The filename must remain exactly the same before and after conversion.
6. 6VERIFY after conversion — Run file --mime-encoding (Linux/macOS) to confirm the result is iso-8859-1 or unknown-8bit, NOT utf-8.
7. 7ONE final state — After this skill runs, only the original file (now CP1252-encoded) must exist. Zero temporary files, zero copies, zero…

What it can do on your machine

Read from SKILL.md and the folder at commit 3908e4e. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Ships 2 files in scripts/ (Batch and Shell), which the agent can run.

  Shell commands in SKILL.md call:

  • bash

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  Links to these hosts (documentation or services it may open):

  • tdn.totvs.com

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

AdvPL UTF-8 to CP1252 Converter loads about 2.6k tokens when it runs. Until then it costs about 127 tokens; SKILL.md has 982 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~127

When it runs · the whole SKILL.md, loaded when a task matches

~2.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from totvs/engpro-advpl-tlpp-skills at commit 3908e4e, republished under its MIT licence (© totvs). 982 words, ~2,578 tokens.

name

utf8-to-cp1252-conversion

description

Convert AdvPL/TLPP source files from UTF-8 encoding to Windows-1252 (CP1252) after code generation. The Protheus compiler only supports CP1252 encoded files — any source created or modified by an AI agent will be in UTF-8 and must be converted before compilation. Use when user says 'convert encoding', 'fix encoding', 'convert to CP1252', 'convert to Windows-1252', 'encoding conversion', 'fix file encoding', or after any code generation skill creates .prw/.prg/.tlpp/.prx files.

license

MIT

metadata.domain

Protheus

metadata.maintainer

Customizações ADVPL/TLPP

metadata.author

Thalion Starforge

metadata.version

4.1.0

metadata.category

Code Quality and Review

bash scripts/convert-encoding.sh path/to/source.tlpp

bash scripts/convert-encoding.sh file1.prw file2.prg file3.tlpp

bash scripts/convert-encoding.sh -r path/to/src/

bash scripts/convert-encoding.sh --dry-run -r path/to/src/

scripts\convert-encoding.bat path\to\source.tlpp

scripts\convert-encoding.bat file1.prw file2.prg file3.tlpp

scripts\convert-encoding.bat /r path\to\src\

scripts\convert-encoding.bat /dryrun /r path\to\src\

1. Agent generates/modifies .prw/.prg/.tlpp/.prx files (UTF-8 — default encoding from AI)
2. Agent runs the conversion script on the generated files (IN-PLACE, same filename)
3. Agent verifies encoding with: file --mime-encoding <file>
4. RESULT: Only the original file exists, now encoded in CP1252 — NO extra files

# Linux/macOS:
bash skills/advpl-tlpp/utf8-to-cp1252-conversion/scripts/convert-encoding.sh \
  src/MyModule.prw

# Windows (CMD):
scripts\convert-encoding.bat src\MyModule.prw

# Linux/macOS:
bash skills/advpl-tlpp/utf8-to-cp1252-conversion/scripts/convert-encoding.sh -r migrated/

# Windows (CMD):
scripts\convert-encoding.bat /r migrated\

file --mime-encoding source.tlpp
# Expected: iso-8859-1 or unknown-8bit (CP1252 is a superset of ISO-8859-1)
# NOT expected: utf-8

powershell -NoProfile -Command "$bytes=[IO.File]::ReadAllBytes('source.tlpp'); $u=[Text.UTF8Encoding]::new($false,$true); try{$u.GetString($bytes); Write-Host 'WARNING: File is still UTF-8'}catch{Write-Host 'OK: File is not UTF-8 (likely CP1252)'}"

© totvs, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (scripts) in skills/advpl-tlpp/utf8-to-cp1252-conversion of totvs/engpro-advpl-tlpp-skills.

• SKILL.md
• scripts/convert-encoding.bat
• scripts/convert-encoding.sh

Open the folder on GitHubat commit 3908e4e