Chris Williams wrote:
> Philip's second reply in this thread has the same markers. I hadn't even
> entered into the conversation yet.
"Philip's second reply in this thread" is presumably my message of
09/10/2015 17:36, which read :
> Gates, Jeff wrote:
>
>> Instead of a ³tick² mark for an ap
Philip's second reply in this thread has the same markers. I hadn't even
entered into the conversation yet.
-
From: Philip Taylor
...
Content-type: text/plain;
charset="EUC-KR"
Content-transfer-encoding: quoted-printable
-
On 10/11/15, 5:19 PM, "css-d-boun...@lists.css-discuss.
I have an issue whereas I'm using multiple background images, turning
off background-cover fixes the title issue with one of the background
images, but when the orientation of the screen changes to lets say,
landscape, the second background is not covered ?
_
12 okt 2015 kl. 02:01 skrev Chris Williams :
> Yeah, well whatever. I'm using Outlook on the Mac, which is not set to
> Korean, as Philip seems to believe.
When Philip quoted your letter, he didn’t think anything else beyond the fact
that your message had among it message headers the character
Yeah, well whatever. I'm using Outlook on the Mac, which is not set to
Korean, as Philip seems to believe.
From: Tom Livingston
Date: Sunday, October 11, 2015 at 4:37 PM
To: Christopher Williams
Cc: CSS-D
Subject: Re: [css-d] CSS solution for a "curly" apostrophe
On Sunday, October 11
On Sunday, October 11, 2015, Chris Williams wrote:
> This.
>
>
Philip already explained this...
"Jeff sent in ISO-8859-1, as I mentioned in my preceding message;
therefore you (and I) saw characters from the ISO-8859-1 character set,
which does not contain the very characters that Jeff was tryi
This.
From: Tom Livingston
Date: Sunday, October 11, 2015 at 12:37 PM
To: "p.tay...@rhul.ac.uk"
Cc: Christopher Williams , CSS-D
Subject: Re: [css-d] CSS solution for a "curly" apostrophe
I only saw superscripted numbers as well, and I have my doubts that ios9.x
gmail client can't display
On Sunday, October 11, 2015, Philip Taylor wrote:
>
>
> Tom Livingston wrote:
>
> > For what it's worth, I usually use entities and have yet to hear of any
> > issues.
> >
> > This: ’ not: '
> >
> > Though, I am no Unicode scholar.
>
> Certain entities come predefined in HTML and XHMTL, and entit
Tom Livingston wrote:
> For what it's worth, I usually use entities and have yet to hear of any
> issues.
>
> This: ’ not: '
>
> Though, I am no Unicode scholar.
Certain entities come predefined in HTML and XHMTL, and entities can be
declared for XML documents, but in plain text messages su
On Sunday, October 11, 2015, Philip Taylor wrote:
>
>
> Tom Livingston wrote:
>
>
> > > I only saw superscripted numbers as well, and I have my doubts that
> > > ios9.x gmail client can't display unicode...
> >
> > Saw only superscripted numbers in whose/which message, Tom ?
> > P
Tom Livingston wrote:
> > I only saw superscripted numbers as well, and I have my doubts that
> > ios9.x gmail client can't display unicode...
>
> Saw only superscripted numbers in whose/which message, Tom ?
> Philip Taylor
>
> Jeff gates first reply.
Jeff sent in ISO-8859-1
On Sunday, October 11, 2015, Philip Taylor wrote:
>
>
> Tom Livingston wrote:
>
> > I only saw superscripted numbers as well, and I have my doubts that
> > ios9.x gmail client can't display unicode...
>
> Saw only superscripted numbers in whose/which message, Tom ?
> Philip Taylor
>
Jeff gates
Tom Livingston wrote:
> I only saw superscripted numbers as well, and I have my doubts that
> ios9.x gmail client can't display unicode...
Saw only superscripted numbers in whose/which message, Tom ?
Philip Taylor
__
css-discus
On Sunday, October 11, 2015, Philip Taylor wrote:
>
>
> Chris Williams wrote:
>
> > [Can you] explain then, your email of yesterday where you explain that
> you said
>
> Explain what, Chris ? I sent a plain text message in UTF-8 which read :
>
> > Content-Type: text/plain; charset=UTF-8
> > Cont
Chris Williams wrote:
> [Can you] explain then, your email of yesterday where you explain that you
> said
Explain what, Chris ? I sent a plain text message in UTF-8 which read :
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: 8bit
>
>
>
> Gates, Jeff wrote:
>
>> In
Explain then, your email of yesterday where you explain that you said
---
Hmmm, what I see are superscript 3, 2 & 1 in that order, followed by a
prime. What I now think you meant is :
Instead of a “tick” mark for an apostrophe, I¹d like a mark like you see
here: ’
I know of no way of accomplish
Chris Williams wrote:
> My larger point was, tread carefully here. Test a lot. Unexpected
> results (as Jeff sees in his simple email to this list) are likely.
If one has to tread carefully for characters as commonplace and
straightforward as curly quotation marks, what hope has one if one wa
Perhaps. But browsers are not the only place where your text is
interpreted. Witness the fact that in my mail program all I'm seeing for
his "preferred" characters are (as you also note) superscript characters.
This is presumably because his email is being converted to ASCII
characters (it's a no
18 matches
Mail list logo
