Skip to main content
13-Aquamarine
July 20, 2026
Question

Arbortext Editor 7.1 - File encoding changes from Windows-1252 to UTF-8 after saving SGML files

  • July 20, 2026
  • 2 replies
  • 55 views

Hello,

We are experiencing unexpected behavior with Arbortext Editor 7.1 regarding the encoding of SGML files.

Issue description:

1. We open an existing SGML file in Arbortext Editor.
2. The file encoding is ANSI Windows-1252 (verified using Notepad++).
3. After opening the file in Arbortext Editor and saving it (even without any content changes), the file encoding is automatically changed.
4. The saved file is now encoded in UTF-8 (verified using Notepad++).

Question:

Is there a parameter or configuration setting in Arbortext Editor 7.1 that defines the default encoding used when saving SGML files?

Our expectation is that the original encoding (Windows-1252) should be preserved when saving an existing file, unless an explicit conversion to UTF-8 is requested.

We have reviewed the Arbortext preferences but could not find any setting that controls the default encoding used during file saving.

Could you please advise on:

- whether there is a preference or configuration parameter to control the save encoding;
- whether it is possible to force Arbortext Editor to preserve the original file encoding when saving SGML documents;
- whether an ACL customization (for example, through `init.acl` or another configuration file) is required to enforce a specific encoding.

Environment information:

- Product: Arbortext Editor
- Version: 7.1
- Document type: SGML
- Original encoding: Windows-1252 (ANSI)
- Encoding after saving: UTF-8

Thank you in advance for your assistance.

Best regards,

2 replies

Catalina
Community Moderator
August 7, 2026

Hi ​@dgopois 
 
Thank you for your question.  
 
Your post appears well documented but has not yet received any response. I am replying to raise awareness. Hopefully, another community member will be able to help. 
 

Thanks, 

Catalina | PTC Community Moderator
18-Opal
August 25, 2026

Do you have any customizations? If so, do any of them modify the doc save callback, e.g.

doc_add_callback(0, "save", "some_custom_save_function")

If so, check to make sure the save callback isn’t explicitly setting the encoding when it calls the save() function.

Based on the documentation, it looks like it should preserve the encoding for an SGML file, unless you override it or save it as XML.