Fredrik Ehnbom

Nothing, the gstreamer API isn't used.

It's just using Go native [utf8 string](http://golang.org/ref/spec#String_literals) and [[]rune literals](http://golang.org/ref/spec#Rune_literals). Other encodings would have to be converted to/from the Go native format upon load and save. IIRC there's currently no...

Or if you were hoping to be able to work directly in an encoded format ([mmap](http://en.wikipedia.org/wiki/Mmap)-ed files comes to mind), you'd have to implement a [InnerBufferInterface](http://godoc.org/github.com/limetext/text#InnerBufferInterface) dealing with that.

> Go native strings are utf8, but rune[]s are utf32... To be really neutral to all encodings, utf32 seems like an ideal.. Type conversion from/to `string` and `[]rune` is [built...

> But from the point of view of LimeText, the in-memory representation of the content of a text file is what I'm trying to understand... Is it UTF-8 or []rune?...

Not sure why DLLs are mentioned. If they were considered, why not just use gconv?

And for reference, https://github.com/qiniu/iconv enables one such approach

Also looks like there are some [pure go interfaces](https://godoc.org/golang.org/x/text/encoding) and [concrete implementations](https://github.com/golang/text/tree/master/encoding) in the [golang.org/x/text](https://godoc.org/golang.org/x/text/encoding) package. Nice!

I'd suggest you create a github repo with your encoding and make it satisfy the https://godoc.org/golang.org/x/text/encoding#Encoding. For hooking into lime, we'd need to make sure all our IO operations go...

Yes, I'd like to have language localization at some point in the future. Changing the title of this issue to deal with that specifically. Don't think this work would be...