Unicode support needed

[Colin Winning]

dbversion needs to be able to support unicode files - whether this is through an indicator in database.xml or some other means.

[Colin Winning (colinwinning)]

When reading the file stream it uses Encoding.Default. Ideally the code would be smart enough to work out that it was a unicode file that it was reading and change the character encoding used but I think a more practical way of doing this would be to have an extra attribute in the database.xml file e.g. encoding="Encoding.Unicode" that would indicate which encoding to use when reading. This would default to Encoding.Default if no attribute was present.

[Adam Connelly (adam-rpconnelly)]

That sounds good. The only thing I'd add is it might be worth adding a
property so that you can default the encoding at the application or
archive level. That way if you only have one Unicode file you can
specify it against the task, but if you know all your files are
Unicode you can specify it once in the archive properties.

On 29 Sep 2011, at 12:47, Colin Winning <email address hidden> wrote:

> When reading the file stream it uses Encoding.Default. Ideally the code
> would be smart enough to work out that it was a unicode file that it was
> reading and change the character encoding used but I think a more
> practical way of doing this would be to have an extra attribute in the
> database.xml file e.g. encoding="Encoding.Unicode" that would indicate
> which encoding to use when reading. This would default to
> Encoding.Default if no attribute was present.
>
> --
> You received this bug notification because you are subscribed to DB
> Version.
> https://bugs.launchpad.net/bugs/855418
>
> Title:
> Unicode support needed
>
> Status in DB Version:
> New
>
> Bug description:
> dbversion needs to be able to support unicode files - whether this is
> through an indicator in database.xml or some other means.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/dbversion/+bug/855418/+subscriptions