unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Rusi <rustompmody@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Unicode in emacs (was Single quotes in Info)
Date: Sun, 25 Jan 2015 19:26:04 -0800 (PST)	[thread overview]
Message-ID: <499f291f-b4bb-4005-b79f-3cd48c4fdaca@googlegroups.com> (raw)
In-Reply-To: <mailman.18484.1422057224.1147.help-gnu-emacs@gnu.org>

On Saturday, January 24, 2015 at 5:23:46 AM UTC+5:30, Drew Adams wrote:
> > I'm not sure about it, but it seems that after upgrading from 24.3 to
> > 25.0.50.1, the Info buffer is a bit uglified.  First, it uses some face
> > I don't like for variable and function names - but if this annoys me too
> > much, I can change it easily.  Worse, instead of e.g. `t' it now says
> > 't', for instance (i.e., it uses Unicode single quotation marks).
> > 
> > This is extremely annoying, since it makes incremental searching for
> > single-quoted strings much harder.
> > 
> > I apropos'ed the "Info-" variables and grepped the list for "quot",
> > "unicode" and "single", all to no avail, and ran out of ideas.  Is this
> > behavior customizable?  How to get back to ASCII quotes?
> 
> Oh boy, you'll have fun reading about this in the bug threads:
> 
> #16292 - http://debbugs.gnu.org/cgi/bugreport.cgi?bug=16292
>          info docs now contain single straight quotes instead of `'
> 
> #13131 - http://debbugs.gnu.org/cgi/bugreport.cgi?bug=13131
>          Allow curly quotes to be found by searching for straight quotes?
> 
> #16439 - http://debbugs.gnu.org/cgi/bugreport.cgi?bug=16439
>          Highlighting of strings within Info buffers
> 
> #13228 - http://debbugs.gnu.org/cgi/bugreport.cgi?bug=13228
>          Request for highlighting back-quote/quote pair notation
> 
> Enjoy!
> 
> (Info+ can at least help by highlighting quoted names etc.
> http://www.emacswiki.org/emacs/InfoPlus)

Just some (very laymanish) thoughts about unicode.
Uni-code has two aspects:
1. Uni-fying the tower of babel that is human languages
2. Uni-versality of a common core

Historically, the 1st is the driver why unicode caught on at all
[The world is a bit larger than the two sides of the atlantic!]

However the 2nd probably holds more hope for reducing babel-ish bedlam.

Some of the more universal sides of unicode:
1. ASCII (for historical reasons alone)
2. Math
3. Typography  (which this thread is about)

[Note this will not technically hold up. I am talking more sociologically
ie
"2+3" is more likely to universalize than "Add two and three"
]

Further expanded in this post
http://blog.languager.org/2015/01/unicode-and-universe.html

Also a plea for programming languages to start getting more unicoded
[Not to be taken too seriously - just a possible direction]
http://blog.languager.org/2014/04/unicoded-python.html


      parent reply	other threads:[~2015-01-26  3:26 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-23 23:17 Single quotes in Info Marcin Borkowski
2015-01-23 23:53 ` Drew Adams
2015-01-24 17:01   ` Marcin Borkowski
2015-01-24  8:38 ` Eli Zaretskii
2015-01-24 15:11   ` Drew Adams
2015-01-24 15:19     ` Eli Zaretskii
     [not found]     ` <<838ugsrysw.fsf@gnu.org>
2015-01-24 15:54       ` Drew Adams
2015-01-24 16:45         ` Marcin Borkowski
2015-01-24 17:00     ` Marcin Borkowski
2015-01-27 16:27       ` Artur Malabarba
2015-01-27 17:37         ` Stefan Monnier
2015-01-27 18:09           ` Eli Zaretskii
2015-01-27 19:00             ` Stefan Monnier
2015-01-27 19:49           ` Artur Malabarba
2015-01-27 20:30             ` Stefan Monnier
2015-01-28  3:48               ` Stefan Monnier
2015-01-28 21:42                 ` Artur Malabarba
2015-01-28 22:23                   ` Stefan Monnier
2015-01-27 18:04         ` Eli Zaretskii
     [not found] ` <mailman.18484.1422057224.1147.help-gnu-emacs@gnu.org>
2015-01-26  3:26   ` Rusi [this message]
     [not found] <<87twzhgk84.fsf@wmi.amu.edu.pl>

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=499f291f-b4bb-4005-b79f-3cd48c4fdaca@googlegroups.com \
    --to=rustompmody@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).