MultiMarkdown Composer Version 2.5 (34) issue with Input Method
Hi Support Team,
I bought MultiMarkdown Composer Version 2.5 (34) from Mac App Store. This application looks great at first glance but issue arises when I start typing. I'm Chinese and I use input method (PinYin) to type in Chinese words. The PinYin input method basically maps Roman characters to Chinese words. When I type '你好' in the caption of a table, weird thing happens. I captured a short video to demonstrate this.
In the video in the attach file, I typed ‘你好' twice. The first was typed into a normal text paragraph and the behavior is correct. The second was typed into the caption of a table and you can see the behavior is wrong.
Please help fix this bug.
OS X version is 10.8.5
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
Support Staff 1 Posted by Fletcher on 12 Oct, 2013 12:34 PM
Composer attempts to autocomplete potential internal links to other parts of the document. Something inside of brackets (e.g. [foo]) will be compared to potential matches and modified to match as you type.
Since the caption is inside square brackets, it tries to autocomplete.
Apparently this is breaking when you use PinYin.
There may be a better way that I eventually discover, but for now the only approach might be an option to disable autocomplete. You should be able to work around this for now by typing your caption, and then wrapping it in `[…]`.
Hope this helps, and thanks for pointing this out!
Fletcher
--
Fletcher T. Penney
Manager, Founder
MultiMarkdown Software, LLC
[email blocked]
2 Posted by uframer on 12 Oct, 2013 05:02 PM
Thanks for your reply.
I believe there is a solution for this because PINYIN is the most popular input method in Chinese world and Apple should have provided some APIs or something to make it work with auto completes in their frameworks.
I'm looking forward to your solution :)
Support Staff 3 Posted by Fletcher on 12 Oct, 2013 05:07 PM
The autocomplete API seems really poor, to be honest. I'm probably doing it wrong, but it required a lot more hacking than I would have thought.
In either case, the next release has an option to disable Composer's custom autocomplete, solving the problem you're having.
FTP
--
Fletcher T. Penney
Manager, Founder
MultiMarkdown Software, LLC
[email blocked]
Fletcher closed this discussion on 15 Oct, 2013 07:46 PM.