Skip to content

Instantly share code, notes, and snippets.

Show Gist options
  • Save mezzoblue/cb9377d21bdfdc3072ba to your computer and use it in GitHub Desktop.
Save mezzoblue/cb9377d21bdfdc3072ba to your computer and use it in GitHub Desktop.
I get email. Crazy, random, long-ass email.
I prefer a Monospace font over any and all Proportional fonts!... i.e., the two
MAIN FONT CATEGORIES into which all other fonts can-- and should!-- be grouped!
But... there's a systemic problem with how FOSS-based Text Formatting suites
(leaving aside, Closed Source/ Closedware suites!) render Monospace, when
incorporating Superscript or Subscript (SS/ SS), graphic boxes, and images (but,
etc.!)!
Why... in a Monospace Format... when placing superscript (or subscript)
characters in LibreOffice (but also, in other FOSS-based programs such as Apache
OpenOffice, and AbiWord!), does the "normal point size" typed below and above
the line I'm working on, not line up with the "normal point size" I'm on? And
so, for example, if I type 10 Xes in 12point (and the 12point, being the larger
"normal point size" I'm using), then the word "house painter" (e.g.) in
superscript... and then type 5 more 12point Xes to the right of my SS/ SS...
then go down one line, and type 12point Xes until I reach the last 12point X
typed above... the last 12point X on the second line, won't align with the last
X typed above! A "squeeze-play" has occurred with the SS/ SS characters...
wherewith, the 12point vertical spacial alignment to the right of the SS/ SS is
no longer contiguous with the 12point vertical spacial justification on the left
of the SS/ SS!... or below it! In other words, the SS/ SS h as creat ed its
own vertical spacial justification!... AND D-MN THE VERTICAL SPACIAL
JUSTIFICATION OF THE NORMAL POINT SIZE ON THE SCREEN!... AND THUS, D-MN FULL
MONOSPACE ALIGNMENT! And... to be clear... it doesn't matter what larger point
size one is using!... the invoking of SS/ SS on one's computer screen will mean
a failure of the alignment of the larger point size!
IF I'M IN MONOSPACE, THE "NORMAL POINT SIZE" SHOULD BE IN ALIGNMENT THROUGHOUT
THE PAGE!... WHETHER I'M USING SS/ SS, OR OTHERWISE (and that goes for the
inclusion of boxes around "normal point size" text, and/ or SS/ SS... i.e., if I
add a vertical bar to form a box, the normal point size to the left or right of
the bar, SHOULD ALIGN IN ACCORDANCE WITH THE NORMAL POINT SIZE BELOW, OR ABOVE
THE BAR!-- AND REGARDLESS OF THE ADDITION OF SS/ SS!)! Otherwise, what's the
point of adopting Monospace to effect-- in part-- the display mechanics of a
typewriter (and the use of the latest software that renders the look and feel--
if you will-- of old-style typewriter fonts; the "bleeding" of keystrokes on
one's computer screen that some developers have fashioned-- and, linked to the
actual pressure one uses when hitting one's keyboard; the ability to go
backwards, and "overtype" one's already typed text-- and repeatedly, with
varying keys; and, software that enables the "clicking sound " of a t
ypewriter's keys!) when the alignment of SS/ SS, and graphic boxes have been
neglected in relation to the normal point size being used in the Monospace
Environment (and thereby, ELIMINATING THE MOST NOTABLE FEATURE OF OF A
MECHANICAL TYPEWRITER'S CHARACTERISTICS!... i.e., 100% MONOSPACE ALIGNMENT OF
ONE'S NORMAL TEXT!)? H--l... my typewriter aligns better than that!... and, for
both SS/ SS, and boxes!
And yes!... I know that the SS/ SS-- as such-- with a typewriter, is THE SAME as
that of/ for the fixed point size of the "normal text"! But arguing that, misses
the point! And that is, that the typewriter affords-- due to its "fixed
mechanics"!-- 100% CHARACTER ALIGNMENT FOR BOTH NORMAL POINT SIZE CHARACTERS,
AND, SS/ SS (IN ADDITION, TO INCORPORATED GRAPHIC BOXES!... and the latter,
which may be fashioned from a mechanical typewriter's "underscore symbol" and
the "single quote symbol"!)! And that, to me-- at least!-- is the QUINTESSENTIAL
DEFINITION OF TRUE MONOSPACE!... and, the reason why many (if not!... why MOST!)
desire Monospace! But, regardless of this PREREQUISITE STANDARD DEFINITION of
what SHOULD constitute TRUE MONOSPACE... AND, DESPITE THE ADOPTED RATIONALE BY
MANY (AND IF NOT... BY MOST!) USERS FOR USING MONOSPACE!... Text Formatting Apps
have gone on to subvert that definition (e.g., Apache's OpenOffice, and
AbiWord!... among others!), in favour of a "hybrid v ersion"! ... i.e., part
Monospace, and, PART NONSENSE!
And by this, I don't mean to suggest that digital SS/ SS must be the SAME SIZE
as that found within a mechanical typewriter! That's silly! But... that
afterupon placing SS/ SS text adjoining the normal point size on screen, the
normal point size should be in alignment with the normal point size elsewhere on
the page! And... I'm not saying that the glyphs themselves aren't Monospace!...
but, that their overall alignment in relation to each other, isn't! And so,
what's the point of referring to a given font as Monospace, when their
alignment... together!... is forsaken!
And just because the SS/ SS within a Text Formatting App may, itself, be
Monospace, this doesn't mean that its application in relation to the larger
normal point size, is-- in fact-- adhering to the Monospace Environment of the
larger point size (and as found in the operation of a mechanical typewriter)!
And, just because a vertical or horizontal bar composing/ comprising a graphic
box around the normal point size on a given screen is not regarded as
"synonymous" with the "alphanumeric, and grammatic family of characters" of a
given larger point size, and Font (and apart from... but in addition to... the
issue of SS/ SS!), doesn't mean that the graphic box elements should be
"estranged" from, and adversely affecting (once invoked) the larger normal point
size chosen! The consistent alignment one achieves with a single or double
quotation mark and underscore character found within a mechanical typewriter
(both vertical, and horizontal!... and, regardless of the "default mechan ics"
uni que to a typewriter!), should be the same consistent alignment achieved
with a Text Formatting App (in Monospace!) used in conjunction with a PC (the
differences between the size of the SS/ SS characters within a mechanical
typewriter, versus that found on a computer screen, NOTWITHSTANDING!)! ANYTHING
INCLUDED WITHIN A MONOSPACE ENVIRONMENT (IMAGES, DINGBATS, OR WHATEVER!) ON A
COMPUTER SCREEN, MUST BE CONFINED TO (I.E., CALIBRATED WITHIN THE PARAMETERS
OF!... OR CONSISTENT WITH!) THE VERTICAL SPACIAL ALLOTMENT ASSIGNED TO THE
NORMAL (LARGER) POINT SIZE SYMBOLS/ CHARACTERS/ TEXT ENTERED ON ONE'S SCREEN!
And so... if an IMAGE requires-- let's say-- 30 and a 1/4 normal point size
characters for its width (leaving aside... for the moment... the image's
height!)... and the image begins at the leftmost side of the screen... then the
placement of the next normal size character to the right of the image (whether
at the top right of the image, or somewhere below this to the bottom right of
the image!), should begin-- MUST BEGIN!-- at the "Monospace Coordinate" "31
(whatever the normal point size... save, for a point size wherewith the
characters are too large!... and thus, a scaled-up '31st character' could not be
entered!)"!... not "30 and 1/2", "30 and 3/4"... and so on... WHICH WOULD BRING
THE NORMAL (LARGER) POINT SIZE ABOVE, OR BELOW, OUT OF VERTICAL ALIGNMENT! The
normal point size text should dictate-- MUST DICTATE!-- how the SS/ SS, image...
or whatever!... will be framed!-- MUST BE FRAMED! THE NORMAL (LARGER) POINT
SIZE, SHOULD BE THE GUIDE-- TEMPLATE!-- WITH WHICH TO ALIGN EVERYTHING ELSE ON A
GIVEN SCREEN IN A MONOSPACE ENVIRONMENT!... PERIOD!
And, it would be just as disconcerting to find, that an image (or SS/ SS, or
graphic box) has adversely impacted on the HORIZONTAL ALIGNMENT in a Monospace
Environment!... i.e., to find, that the HORIZONTAL SYMMETRY of normal point size
lines of text has been compromised, once an image (or whatever) has been
invoked! And... as would be the case, with a mechanical typewriter!
Lastly, because of the problems cited above, I cannot use LibreOffice (or any
other Office Suite with the same issue!... and e.g., Apache's OpenOffice, or
AbiWord!) AT ALL! I... for my purposes (and for users like me!)... require TRUE
MONOSPACE (i.e., 100% ALIGNMENT IN THE USE OF SS/ SS, GRAPHIC BOXES-- OR
IMAGES!... AND, IN CONJUNCTION, WITH THE NORMAL POINT SIZE ADOPTED FOR THE
SCREEN I'M WORKING ON!)! AND, IT'S "THE ONLY REASON" FOR CHOOSING LIBREOFFICE
(OR... ANY OTHER TEXT FORMATTING SOFTWARE!... WHATSOEVER!)! AND... I DARE
SAY!... IT'S A PREFERRED ITEM, OF CONNOISSEURS OF THE MECHANICS OF OLD STYLE
TYPEWRITERS!... AND, IN ADDITION TO (BUT, BEYOND!) A-L-L OF THE NEWEST SOFTWARE
FEATURES DESCRIBED ABOVE! AND!... IF FOR NO OTHR REASON, THAN TO INVOKE THE
"LAST WORD (IF YOU WILL!)" IN RENDERING THE COMPLETE AESTHETIC "LOOK AND FEEL"
OF OLD-STYLE TYPEWRITER MECHANICS! AND!... WHY NOT?
Why... indeed!... would this-- should this!-- one element of the "look and feel"
of old-style typewriter mechanics (and given all of the software that has been
fashioned to provide a true recreation of the experience of using an old-style
typewriter!) be left out of the "aesthetic experience" of old-style typewriting?
Why would this one element be any less important than glyphs (bleeding!... or
otherwise!)... or, the software rendering of the clicking sounds made with old-
style typewriter keys! H-ll!... even the actor Tom Hanks (with his Hanx Writer!)
has gotten into the "act" of old-style typewriting, using his own brand of
typewriting software!... though, the Hanx Writer does not-- as well!-- include
this essential feature!
And so, I'm now forced to hunt the web for my needed superscript "q (see:
http://webcache.googleuser
content.com/search?q=cache:5i6OGFIStVsJ:www.unicode.org/L2/L2011/11208-n4068.
pdf+&cd=5&hl=en&ct=clnk&gl=us)" for inclusion within the remaining alphabet I've
copied from the web (see: https://en.wikipedia.org/
wiki/Unicode_subscripts_and_superscripts); paste and store this-- somehow (if
found, and if possible!)-- in MS' Notepad (in Monospace)!; play with MS'
Character Map to implement graphic boxes!; and, use MS' Private Character Editor
to effect the underlining of text, and the incorporation of other symbols not
found within MS' family of Monospace Fonts! Oh!... or REDESIGN A WHOLLY NEW
MONOSPACE TEXT FORMATTING SUITE FROM SCRATCH! CRAAAAZY!! And all because my
otherwise chosen LibreOffice doesn't allow for 100% Monospace Alignment of a
given normal point size (i.e., when SS/ SS, boxes, or other elements, are
added)! And the fact that I am having to discuss this c--p in 2016, is...
well... RIDICULOUS!... and boggles the mind!
And now... if the foregoing wasn't bad enough!... although one can copy and
paste 25 of the latin-based alphabetic superscript letters from a website into
Notepad... I am-- nevertheless!-- unable to add the "q" into Notepad!... because
someone, or somebody (or, SOME "BODY"!) has failed to see the significance of
including this (and more!) within Unicode (and the "BODY"!.... and so far!...
being the Unicode Consortium!)!
For me-- at least-- the inability to render ALL of the Latin-based alphabetic
SS/ SS characters in Unicode, is dumb (let alone, the many other symbols one
could, and should be able to render as a SS/ SS character in Unicode!)! I-- and,
other users!-- should be able to immediately capture that unique symbol out
there on the Net (SS/ SS, or otherwise!), and incorporate such within the body
of our chosen Net Medium, or personal file/ (s)!... AND, "TEXT FORMATTING
SUITE"! And, if Unicode is to play a role in that, then it MUST be able to "turn
on a dime (so to speak)"... and, accommodate our proficient, and prolific use of
what's out there! UNICODE MUST SERVE US!... NOT THE OTHER WAY AROUND!
My recommendation is simple... LibreOffice (but, add Apache OpenOffice, and
AbiWord!... but, etc.!) should create a NEW Menu Option in association with its
SS/ SS icons (possibly, through a "drop-down menu"!... maybe, when the cursor
moves over these icons!), that will enable (activate!) 100% alignment of a given
Monospace normal point size on a computer screen, with any SS/ SS, and/ or
graphic box rendering (unless!... and of course!... LibreOffice simply renders
all of its Monospace text in the manner as aforedescribed!)! In other words, the
optional (or ONLY!) FOSS-BASED TEXT FORMATTING STANDARD will render
(henceforth!... and specific to a Monospace Environment!), all SS/ SS, and
graphic boxes (etc.) in alignment with (in calibration with!) a given chosen
"normal point size's" spatial configuration (VERTICALLY, AND HORIZONTALLY!)!
And... that will require, that when a SS/ SS expression, box, or image (or
whatever) is rendered in Monospace, the NEW FOSS-BASED TEXT FORMATTI NG FORMA
TTING STANDARD (and call it what one will!) will automatically frame the SS/ SS,
box, or image (or whatever) WITHIN A DETERMINED NUMBER OF NORMAL (LARGER) POINT
SIZE SPACES!... so that, any normal (larger) point size text typed to the right
of the SS/ SS (in the case of SS/ SS), or included above or below a given line
of typed normal point size, WILL BE IN 100% ALIGNMENT! And, all of the
immediately aforesaid should be SCALABLE!... i.e., if there are "multiple normal
point sizes (if you will!)" on a screen (e.g., ads converted, or translated to
Monospace!... and-- of course!-- which should be so converted, or translated!),
the same principles of alignment will apply within these respective conversions,
or translations!... AND, IN RELATION TO (CONTIGUOUS WITH!) ONE ANOTHER! THAT'S
TRUE MONOSPACE!... NOT THE C--P WE NOW HAVE (though, with ALL DUE CONSIDERATION
to the FINE EFFORTS of ANY AND ALL who have contributed to the creation of the
LibreOffice family... and OTHER FOSS FA MILIES!. .. of text formatting
products!)!
I would like to believe that a style sheet could end this madness!... and
correct what FOSS-based Office Suites have failed to incorporate! But... I--
presently!-- don't see this, as an option!
Thanks for your time!... and consideration!
Please!... no emails!... or email publication! If a "reworking" of LibreOffice
(and other FOSS-based text formatting office suites/ software products!) to
accommodate the SERIOUS CONCERNS I've raised is effected, I will learn of such,
soon enough! And... if there is a CSS option that would get the job done, that
I'm unaware of, then... please!... include this option as a response to this
message, within mezzoblue.com!... and... for all to see! Otherwise... I'll see
you, when I see you!
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment