Minh Nguyễn

The original Orion support, which I wrote years ago, assumed (correctly at the time) that the `originalTarget` would be `div#clientDiv.editorContent`. Orion’s frontend appears to have been rewritten since then, so...

In fact, no IME extension on either Firefox or Chrome works with Orion. Google Input Tools comes the closest, allowing you to enter an entire word before the word disappears....

`originalTarget` is now `div.textviewContent`. Some Orion functionality can be accessed through `window.orion` and `window.orion.editor`, but everything else is neatly hidden away. It seems like most AVIM’s ordinary contenteditable support should...

Some possible leads: https://github.com/kogmbh/WebODF/blob/master/programs/editor/localeditor.js http://www.webodf.org/docs/symbols/gui.TextController.html http://www.webodf.org/docs/symbols/gui.SessionController.html

Not a whole lot is exported. It may be necessary to simulate copy and paste, like we did for Google Docs for awhile.

[ and ] aren’t next to each other on every keyboard layout. I just wasn’t sure if it matters.

Oops, you’re right. I guess the problem I meant to articulate is that there’s no good way to indicate that a particular word is going to be Vietnamese or non-Vietnamese....

I _should_ be able to pass `editor.doc.cursor.getTextFormat()` into `editor.doc.cursor.insert`, but that causes text to disappear at the beginning of the line and text formatting to be applied unevenly.

~~[Cờ Rôm+](https://corom.vn/)~~ [Cốc Cốc](http://coccoc.com/addtone.html) also has an auto-accent feature for the entire browser, including the search bar. AVIM needs to support something in this vein (or promote the Accentuate.us extension),...

Connecting to the API looks like a piece of cake, but the service isn’t working for Vietnamese at the moment. (It is working for other languages.) The main challenge is...