# Odkmeta: “column header type not found”

**URL:** <https://forum.getodk.org/t/odkmeta-column-header-type-not-found/10617>\
**Category:** Support\
**Tags:** odk-meta\
**Created:** [August 31, 2017, 7:00am UTC](https://forum.getodk.org/t/odkmeta-column-header-type-not-found/10617 "2017-08-31T07:00:00Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Matthew\_White](https://getodk.b-cdn.net/user_avatar/forum.getodk.org/matthew_white/32/1654_2.png) [@Matthew\_White](https://forum.getodk.org/u/Matthew_White)\
**Post date:** [September 2, 2017, 6:53pm UTC](https://forum.getodk.org/t/odkmeta-column-header-type-not-found/10617/4 "2017-09-02T18:53:28Z")

</div>

@Amanda_Berman, it looks like `survey.csv` and `choices.csv` are encoded as Unicode (specifically UTF-8).

Stata 14+ supports Unicode. However, `odkmeta` was written to be compatible with Stata 11, and it does not currently support Unicode. We may add Unicode support in the future, but for now, I recommend exporting your CSV files as ASCII instead.

From a first glance, it looks like the one character in your XLSForm to watch out for is `’`, the right single quote, which doesn't appear in all eight-bit extended ASCII encodings. As long as that character only appears in labels, the simplest solution is probably just to replace it with the straight single quote `'` before exporting. The presence of the right single quote may be why the CSV was exported as Unicode in the first place.

I'll create a GitHub issue noting that we should consider adding Unicode support to `odkmeta` or at least better documentation.

---

_[View the full topic](https://forum.getodk.org/t/odkmeta-column-header-type-not-found/10617)._
