Using a Chromium browser on macOS 10.14, the number 9 is often not displayed, but is replaced with a hyphen dash.
This appears to be caused by bad or duplicate Helvetica fonts—a side effect of the Helvening™, whereby every four years the number of Helveticas on your system doubles (I have 64). Isolated and resolved (in my case) by deleting HelveticaNeue.dfont, HelveticaNeue-1.dfont and HelveticaNeue-2.dfont.
Related
Some characters that I enter in editor displayed not identical to those on keyboard. So I have error messages like this:
Character with decimal value 176 does not belong to the PL/I character
set. It will be ignored.
when trying to compile PL/I programm.
Sometimes character can displayed even properly, but I still have similar error message.
Examples of this characters are character that represents logical OR, logical NOT.
How to solve this problem? Is it a settings of editor, or settings of program IBM Personal Communications? Or may be it is better to enter 16-code of those symbols (how to do that if possible, and how to determine what code I need)?
There is a lot of places where this can go wrong...
The keyboard-driver on your client machine has to be configured correctly for the keyboard you use. But if other programs work correctly and only the mainframe emulation behaves strangely then this should be OK.
The PCOMM-session has to be configured to use the correct Host-codepage. Ask your mainframe technical guys what is used and configure your terminal emulation accordingly. Since we don't use PCOMM I can't help you with this, you will have to look around the session settings a bit.
In PL/I most characters are taken from the range that is identical in most EBCDIC codepages. The main exceptions are the characters for the OR- and NOT-operators which may differ. IBM-default for OR is '4F'X, which is a pipe-character '|' in codepage 1140 (English), but an exclamation mark '!' in codepage 1141 (German). Default for NOT is '5F'X which is a logical NOT-sign '¬' in 1140 but a caret '^' in 1141.
Since these problems are well known the compiler offers two options OR() and NOT() to set the characters to be used for these operators. So you might look in your compile-listing whether these parameters are set in your installation and what their values are since these are the characters you have to use.
The previous week I moved my local server with my site from a computer with Windows to another one with Linux.Thats when i noticed that there are some weird soft lines after elements and the letter "Λ" (which is greek) showing like its damaged.Its important to mention that if i zoom out the letter is displayed correctly.Also i visited my site from a PC with windows and everything seems fine. I hope that these photos will help you understand better the problem.
Soft Lines + Letter Problem
Soft Lines + Zoom Out
I have read somewhere (don't remember much where exactly) that many problems of the sort are caused by the encoding.
So you might want to ensure that your characters are UTF-8.
Have a look at this article
Hope it helps
This question already has answers here:
How do you echo a 4-digit Unicode character in Bash?
(18 answers)
Closed 7 years ago.
Hello I am trying to display the Dice Unicode characters on a web sever using bash, however I am finding it more difficult then it should be. In short I found online that (printf '\u0026') works and prints & to my page. However when I change the number to my desired '\u2680' nothing is displayed. Admittedly I am not very knowledgeable in linux nor unicode. But I am very confused on why a lower number will work and a higher one will not, or what I am doing wrong.
I think I may have found the answer. I think that because I am echoing everything into a html it is parsing the Unicode in html and not using linux. (Not 100% sure about that so correct me if I am wrong.)
Either way, by simply putting the html code for the dice characters into the sh file I was able to display the characters that I wanted.
(i.e echo '⚀(;)' without the parentheses)
First you need to provide more information regarding what you are generating using bash. Put a sample script and specify what operating system and web server are you using.
It is essential to be sure that the encoding using by shell/bash is the same as the default encoding of the webserver. The HTML page must have a proper encoding specified in the header.
I have recently discovered that my TI-84 plus silver edition can be programmed in hex. I have been messing around with it but have had a few bugs. Whenever I try to make a bcall to PutS it only prints one character and moves on. If I add a second PutS command it puts the second letter down and to the right by one. My current code is:
AsmPrgm
219D9D
EFD9481C
C9
48692100
Necro reply: It seems like you are using one of the new Math Print OSes. Because of the "pretty print" math, TI had to change how strings are printed to the screen. Unfortunately, they broke older functions that as _PutS. One way to get around it is to just put your calc into Classic mode. This disables math print, so printing characters to the homescreen will work as expected.
Go to [Mode],[down] 8 times, [right], [Enter]
It works on my 84+ too. There is nothing wrong with this program.
Possible solutions:
Check if you typed in the hexadecimal correctly.
Perhaps you are using a different OS version that has the bcall at a different location in memory. My os version is 2.43 (no mathprint)
Good luck!
I'm using ghci to do some incremental development using Emacs' run-haskell. Every once in a while, I get an error that looks like
<interactive>:[line]:[character]: _Lexical error at character '\EOT'
Setting up an intermediate variable or two gets a working response, and the file I'm working on both loads and compiles properly. Reducing character count also works; the max I seem to be able to hit is 252.
Anyone have an idea of what's going on?
This was filed and closed as a bug in GHC several years ago, so looks like no dice on fixing it at the GHCi end. (Searching "_Lexical error at character '\EOT'" gives a few other results (for example), but I can't work out how applicable they are.)