# Plugin error from diversity: 'latin-1' codec can't encode character '\\u03b2' (...)

**URL:** <https://forum.qiime2.org/t/plugin-error-from-diversity-latin-1-codec-cant-encode-character-u03b2/11779>\
**Category:** Technical Support\
**Tags:** diversity, core-metrics\
**Created:** [October 1, 2019, 7:43pm UTC](https://forum.qiime2.org/t/plugin-error-from-diversity-latin-1-codec-cant-encode-character-u03b2/11779 "2019-10-01T19:43:59Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![ebolyen](https://forum.qiime2.org/user_avatar/forum.qiime2.org/ebolyen/32/11_2.png) [@ebolyen](https://forum.qiime2.org/u/ebolyen)\
**Post date:** [October 2, 2019, 4:09pm UTC](https://forum.qiime2.org/t/plugin-error-from-diversity-latin-1-codec-cant-encode-character-u03b2/11779/3 "2019-10-02T16:09:02Z")

</div>

Hey @efratm!

I think this is the first time I've seen someone with the latin-1 encoding (which is weird as it used to be a _super_ common standard).

There's not necessarily any bad characters here, rather latin-1 just cannot express some symbols. What strikes me as odd is that QIIME 2 is attempting to use latin-1 at all. It looks like perhaps we did not specify utf-8 (which can encode _all_ characters) to our bibtex library, and so it must be using a default?

Where it is getting that default is less clear, I would guess that it's your environment configuration, so let's see if that's true:

```bash
env | grep "LC\|LANG\|LANGUAGE"

```

That command will tell us how your environment's locale is configured, and we can brainstorm from there.

---

_[View the full topic](https://forum.qiime2.org/t/plugin-error-from-diversity-latin-1-codec-cant-encode-character-u03b2/11779)._
