Hello,

currently Beancount has some support for using encodings different from
UTF-8 for its input files. This functionality is however limited to
string literals and to the use of encodings that encode the ASCII subset
in the same way as the ASCII encoding (or to the use of some custom tool
to forge files where different encodings are used for different parts).

For reasons described here
https://github.com/beancount/beancount/issues/504 I think that this
functionality in his current form has little to no use and I am
proposing to remove it.

As far as I can tell, this feature is not exposed by the interface of
the Beancount tools, thus I think it is very unlikely that someone is
using it.

However, before implementing the changes described in the issue tracker,
I would like to make sure that no one is making use of this feature.

Thank you.

Best,
Dan

-- 
You received this message because you are subscribed to the Google Groups 
"Beancount" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/cbde3568-e049-8df3-cb83-e09e520f5053%40grinta.net.

Reply via email to