summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorLeo Vivier <zaeph@zaeph.net>2021-12-03 21:59:53 +0100
committerLeo Vivier <zaeph@zaeph.net>2021-12-03 21:59:53 +0100
commit2c169118b07d60030406c31f09cf3cd5ae635708 (patch)
treef3926f51954f586948cdaf207fc3ca4ec4bb2fbb
parentda2dd22fcda67d4828be03cb65b3d578957c5ee0 (diff)
downloademacsconf-wiki-2c169118b07d60030406c31f09cf3cd5ae635708.tar.xz
emacsconf-wiki-2c169118b07d60030406c31f09cf3cd5ae635708.zip
Fix whitespace
-rw-r--r--2021/talks/bidi.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/2021/talks/bidi.md b/2021/talks/bidi.md
index 8044af56..75c3b1f0 100644
--- a/2021/talks/bidi.md
+++ b/2021/talks/bidi.md
@@ -138,7 +138,7 @@ Pad:
- 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?
+- 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
@@ -153,7 +153,7 @@ Pad:
- 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
+- 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