diff options
Diffstat (limited to '2021/talks/bidi.md')
| -rw-r--r-- | 2021/talks/bidi.md | 68 |
1 files changed, 66 insertions, 2 deletions
diff --git a/2021/talks/bidi.md b/2021/talks/bidi.md index 340cbcea..5669a817 100644 --- a/2021/talks/bidi.md +++ b/2021/talks/bidi.md @@ -10,8 +10,6 @@ Mohsen BANAN -- <mailto:emacs@mohsen.1.banan.byname.net> -- محسن بنان pronouns: he/him, pronunciation: MO-HH-SS-EN <http://mohsen.1.banan.byname.net> - - [[!inline pages="internal(2021/info/bidi-schedule)" raw="yes"]] ## About The Video @@ -127,5 +125,71 @@ of bidi on existing emacs applications, including: <http://mohsen.1.banan.byname.net/persian> -- Farsi <http://mohsen.1.banan.byname.net/french> -- French +# Discussion + +Pad: + +- Q1: is there any additions that you have to add to emacs for using + non-English/latin characters or does it work mostly out of the box? + - A: [Prot] : I only set the default-input-method to "greek". + Then switch to it with C- (toggle-input-method) +- Q2: One stuggle I have with this input method option is, why not use + an IME that's installed on the host OS? + - A:I live inside Emacs, and that the host OS typically provides + an unintelligent keyboard, and Farsi and transliterate BANAN + provides multi-character input, which is a lot more powerful. +- Q3: Do you write any lisp or other code/markup with these scripts? + (Sorry if I missed you mentioning this.) + - A:No, everything is in pure Elisp. +- Q4: What alternatives have you looked into for solving the problem + related to your markup language idea? What isn't achieved by them? + - A:The way that Emacs has evovled about properties about string + and text. And I suggest we adopt the "web" model for Emacs + application development. If you step back and look at where we + are, there's no such thing as no 'emacs native markup language + mode' similar to HTML for web. Emacs's display engine is + capable of doing everything, but we're not exposing .... + (sorry, missed this part) + - Makes sense to me, thanks! +- Q5: bandali: genenrally curious about the state of writing/reading + Persian in the TTY +- Q6: Does your input method also solves problems with exporting + doctuments ? usually when you exporting a Persian-Enlight doc it + redirects the Persian scripts to LTR + +Questions/comments: + +- Thanks for giving such a nice presentation of the Emacs input method framework! I'm just curious about if you've made any plans for setting up your markup language? I know you said you hadn't written any code for it yet. +- That makes sense. Do you think you could use org more exclusively, and just add portions to implement your idea? As-in, there's nothing within org mode that would need to be fundamentally changed, correct? +- I wonder about that. Org doesn't quite support all the expressivness that you see in some buffers/modes. +- I agree. Finding a way to reach a happy medium without having to go "full elisp" would be quite powerful. +- Potentially the tui.el system mentioned earlier in the conference could mix will with your idea as well. +- I have one last, quick question. If you've used a version of Emacs 28, how have you found the new feature of doing a quick switch into a different IME? I know John Wiegly mentioned it in his talk earlier. +- Does OS-level stuff work when you have to change character direction on the same line, like LtR numbers in a RtL script? + +Feedback: + +- This is great. I've done a demo like this for a few friends in the past as well. +- Whoever did the captions for this was spot on, the unicode characters would be challenging. +- I just love the Emacs input method framework, and I don't think a lot of latin script users know about it. +- This is really cool, it's something that I never think about from other users in other countries using Emacs. +- The captions for this conference have has an impressive amount of work put into them. +- omg! this is great. farsi 101 in emacs +- ++ to all that stuff. Great job on the captions, and the demonstrated functionality is very impressive. +- Yay for the captions! +- This has been really slick. Kudos for the captions including the Farsi characters and latin text. +- At first, I thought the captions would be unnecessary, but over time, understanding the accents for various individuals has been challenging, so the captions helped. +- One struggle I have with this input method option is, why not use an IME that's installed on the host OS? I mean, I do that with Japanese, but that may no longer work easily with qubes, so maybe it's more of a thing that'd benefit me now. + - though, I'm thinking that certain input methods don't actually simulate key-presses on virtual keyboards ... ? + - Not a primary reason, but since I'm used to configuring Emacs, I've found it a lot easier to learn to configure the integrated IMF than to configure an external one. + - I used SCIM/uim for japanese input at one put, but that was before I used emacs, it was a nightmare to set up +- I may have to try this, the IMEs I've used haven't been an issue too much in the past, but...maybe this would be better, at least I wouldn't have to worry about config on each qube. +- Banan's work on BIDI support is an eye-opener... +- yeah absolutely. it's a really great point that Emacs can always be expanded to be more inclusive to other languages in ways that are more than just Unicode related. +- bidi destorying irssi, time to find a good emacs irc client ... +- thanks for the talk...another example how Emacs is inclusive catering for all forms of text. +- Lots to think about. Thanks for the talk and inspiration! +- Awesome. Thanks again for such a great talk and a great q&a! + [[!inline pages="internal(2021/captions/bidi)" raw="yes"]] [[!inline pages="internal(2021/info/bidi-nav)" raw="yes"]] |