On the first message from either person.
Jeff Gates:
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Philip:
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Best,
Karl DeSaulniers
Design Drumm
http://designdrumm.com
On
Chris, could you please forward (to the list) the message headers in the
message from me which you believe was in Korean encoding, as I did with
your message ? What you "quoted" was sent (by you) in Korean encoding
(euc-kr) so it mis-represented what I had sent which was sent in utf-8
as with all
As I noted and quoted, YOUR email had the Korean encoding markers before I
even entered the conversation.
On 10/11/15, 11:56 PM, "Philip Taylor" wrote:
>
>
>Chris Williams wrote:
>
>> Philip's second reply in this thread has the same markers. I hadn't
>>even
>> entered into the conversation yet
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.
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
that Jeff was trying to
communicate.
Philip Taylor"
> 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
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.
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
Chris Williams wrote:
> 1) These characters are font dependent. Unless you are specifically
> calling out fonts that you use, you risk using glyphs that will not be
> found on your target machine.
My understanding (and I may be wrong) is that if a modern browser is
called on to display a glyph
On 10/9/15, 12:35 PM, "css-d-boun...@lists.css-discuss.org on behalf of
Chris Williams" wrote:
>You mean the one that shows up as an unknown character on many platforms?
>For reference either a superscript 3 or 1 in my email below...
>
>1) These characters are font dependent. Unless you are spec
Gates, Jeff wrote:
> Instead of a ³tick² mark for an apostrophe, I¹d like a mark like you see
> here: ¹
> This: ¹ Not this: '
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 ma
You mean the one that shows up as an unknown character on many platforms?
For reference either a superscript 3 or 1 in my email below...
1) These characters are font dependent. Unless you are specifically
calling out fonts that you use, you risk using glyphs that will not be
found on your target
On 10/9/15, 12:20 PM, "Philip Taylor" wrote
>
>
>Gates, Jeff wrote:
>
>> Is there a way I can use css to replace all dump apostrophes with curly
>> ones ?
>
>Google has never heard of "dump apostrophe(s)" (and neither have I), so
>I regret that I can't help with this one.
>
>Philip Taylor
Inst
Gates, Jeff wrote:
> Is there a way I can use css to replace all dump apostrophes with curly
> ones ?
Google has never heard of "dump apostrophe(s)" (and neither have I), so
I regret that I can't help with this one.
Philip Taylor
___
Is there a way I can use css to replace all dump apostrophes with curly
ones? I¹m getting sick of searching and replacing with an html entity. I¹d
like to apply it to the body so that it applies to all apostrophes.
Thanks,
Jeff
>
__
27 matches
Mail list logo
