>> Thanks for the reply. It’s very likely that the page contains images,
>> borders, background, etc., so I can recognize all the text are missing. But
>> neither of text missing nor text garbled suggests me how to fix it. I’d try
>> another browser, then give up viewing the page.
>
> If it did
On 30/06/2014, David Starner wrote:
> On Sun, Jun 29, 2014 at 2:02 PM, Jukka K. Korpela
> wrote:
>> They might be seen as “not displayable by normal rendering”, so yes. On
>> the
>> practical side, although Private Use characters should not be used in
>> public
>> information interchange, they a
On Mon, Jun 30, 2014 at 9:12 PM, Koji Ishii wrote:
> Thanks for the reply. It’s very likely that the page contains images,
> borders, background, etc., so I can recognize all the text are missing. But
> neither of text missing nor text garbled suggests me how to fix it. I’d try
> another browse
On Jul 1, 2014, at 9:14 AM, David Starner wrote:
On Mon, Jun 30, 2014 at 11:35 AM, Koji Ishii wrote:
>> I understand some here wants to display them to help users to identify
>> broken characters, some consider it doesn’t help users at all. I tend to
>> agree with the later, but either way, it’s
On Mon, Jun 30, 2014 at 11:35 AM, Koji Ishii wrote:
> I understand some here wants to display them to help users to identify
> broken characters, some consider it doesn’t help users at all. I tend to
> agree with the later, but either way, it’s about helping users to fix their
> documents.
If you
Hi everybody,
I am currently in the process of designing a simple OpenType font for
Mandaic. As some of you are probably aware, shaping in OpenType as it
is recommended by the OpenType standard requires that the application
(i.e. the text rendering engine) knows the joining behaviour of the
chara
Thank you all for this a lot of great feedback. I learned a lot.
I, however, still don’t get one thing. In the spec text:
Surrogate code points, private-use characters, and control characters are not
given the Default_Ignorable_Code_Point property. To avoid security problems,
such characters or
I generally agree with your comment.
For your question U+FFFD is not special in CSS, it's just a standard
character that will be mapped to some symbol (from any font, or synthetized
from an internal font (or collection of glyphs) of the renderer according
to other styles (there's no warranty that
2014-06-29 22:24 GMT+03:00 Asmus Freytag :
> but things get harder the more I think:
>>
>> 3. When the above text says “surrogate code points”, does that mean
>> everything outside BMP? It reads so to me, but I’m surprised that
>> characters in BMP and outside BMP have such differences, so I’m dou
A couple of your questions are addressed by:
http://www.unicode.org/faq/unsup_char.html
In particular:
Q: Which characters should be displayed with a missing glyph, if not
supported?
A: All characters other than whitespace and default-ignorable characters.
James
On Mon, Jun 30, 2014 at 1:44 AM
10 matches
Mail list logo