Some Vanilla/Turtle WoW client setups, especially when copied to or edited on Windows systems, can have trouble with non-ASCII characters in addon Lua files.
The Bars module contained a few non-ASCII characters in comments, and the Range Indicator simple marker used a UTF-8 bullet glyph.
This caused encoding/display issues after copying the addon to a Windows PC.
Expected behavior
Lua source files used by the addon should avoid unnecessary non-ASCII characters to maximize compatibility with older clients and Windows setups.
Actual behavior
modules/bars/bars.lua and modules/bars/range.lua contained non-ASCII characters.
Proposed fix
Replace non-ASCII characters with ASCII equivalents:
- remove UTF-8 symbols/accented characters from comments in
bars.lua
- replace the Range Indicator simple bullet marker with an ASCII
X
This keeps behavior simple and avoids encoding-related client issues.
Some Vanilla/Turtle WoW client setups, especially when copied to or edited on Windows systems, can have trouble with non-ASCII characters in addon Lua files.
The Bars module contained a few non-ASCII characters in comments, and the Range Indicator simple marker used a UTF-8 bullet glyph.
This caused encoding/display issues after copying the addon to a Windows PC.
Expected behavior
Lua source files used by the addon should avoid unnecessary non-ASCII characters to maximize compatibility with older clients and Windows setups.
Actual behavior
modules/bars/bars.luaandmodules/bars/range.luacontained non-ASCII characters.Proposed fix
Replace non-ASCII characters with ASCII equivalents:
bars.luaXThis keeps behavior simple and avoids encoding-related client issues.