Skip to content

[INTERNAL] Document utf8 BOM handling for .properties files #1639

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
d3xter666 merged 1 commit into from
Oct 7, 2026
Merged

[INTERNAL] Document utf8 BOM handling for .properties files #1639

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/pages/Configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -204,6 +204,8 @@ If your project uses a different encoding for `*.properties` files, you need to

UI5 CLI will read the corresponding files of the project in the given encoding. Any non-ASCII characters will be replaced with the respective Unicode escape sequences. This allows you to deploy the resulting files to any environment, independent of how it expects `*.properties` files to be encoded. Please refer to [RFC 7](https://github.com/UI5/cli/blob/main/rfcs/0007-properties-file-encoding.md) for details.

If a `*.properties` file was accidentally saved with a leading UTF-8 Byte Order Mark (BOM), the BOM is removed during this process. Otherwise it would be escaped into a literal `\uFEFF` sequence at the start of the file, corrupting the first key.

## Custom Configuration

!!! info
Expand Down
Loading