unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: do ri via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 38137@debbugs.gnu.org
Subject: bug#38137: code of Emacs vs. function of OS ?
Date: Fri, 08 Nov 2019 19:28:48 +0300	[thread overview]
Message-ID: <1573230528.941707773@f537.i.mail.ru> (raw)

[-- Attachment #1: Type: text/plain, Size: 1034 bytes --]

Hi, all,
Prompt pls. 
 
1) Who - your code of text editor or function of operations system - interpret the control codes 0x00 till 0x1f (e.g. LineFeed 0x0a)? If these codes have glyphs in .ttf-files, and we wanna see these glyphs in text editor, changes should be done in text editor or in system function?
 
2) The same question for control codes 0x80 till 0x9f.
 
3) Opposite question: who interpret code 0x20 (Space) as mark to bring text to new line? To change code of Space to another one (e.g. to 0x49), where changes should be done?
 
4) To interpret code of old regular letter (e.g. 0x48) as control code (e.g. as LineFeed), where changes should be done?
 
5) For symbols 0x00 till 0x7f, what are the ways to use 7-bits encoding table with classical .ttf-files without converting text into 8-bits encoding?
 
P.S.
Reasons of questions:
https://www.youtube.com/watch?v=uu8W0uobvQs
 
(regular letters are 0x00 till 0x46, control codes 0x47 till 0x7f)
https://sun9-70.userapi.com/c855016/v855016873/147e35/y2yzXkm-EvQ.jpg

[-- Attachment #2: Type: text/html, Size: 1594 bytes --]

             reply	other threads:[~2019-11-08 16:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-08 16:28 do ri via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2020-01-18 10:28 ` bug#38137: code of Emacs vs. function of OS ? Stefan Kangas

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=1573230528.941707773@f537.i.mail.ru \
    --to=bug-gnu-emacs@gnu.org \
    --cc=38137@debbugs.gnu.org \
    --cc=do.ri.1989@bk.ru \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).