<h1>Option Files in non utf-8 encoding are not portable</h1>
As pointed out on the clt-list, option files in non utf-8 encodings are not portable.
BWidget (up to version 1.9.9) (mis)uses the option data base for message catalogues and the files were originally encoded in ISO-Latin 1.
This breaks on systems with a system encoding of utf-8 like recent Linux systems.
Details are here: [https://core.tcl.tk/bwidget/info/6c91e43d76c2cc23]
<h1>Fixes breaking current BWidget</h1>
Christian Werner/Jan Nijtmans proposed a patch for tcl8.5.19/tcl8.6.5 which used the system encoding and uses utf-8 when a BOM is present, breaking encoding files in utf-8 without BOM (which worked so far).
Trunk: [16df5a3f], core-8-5-branch [ad879218]
Donald Port have done two background posts on what is happening on clt:
* Background: [http://code.activestate.com/lists/tcl-core/15353/]
* Bug itself: [http://code.activestate.com/lists/tcl-core/15354/]
Harald Oehlmann limited personal view [http://code.activestate.com/lists/tcl-core/15356/]
* Revert change on Tk8.5.19
* Use utf-8 only for Tk8.6.5
Jan Nijtmans implemented this for trunk [f42bec2656f3b663]