What's the difference between 's and 's?

and what would cause transformation of one over the other?

Meaning, why would one apostrophe get converted one way over the other, and vice versa?

This might help:

and this:

and this:

1 Like

What about 's, do you have anything on that one?



Can you provide some more context? What is the word (or words) surrounding the apostrophe? To me, it just looks like 's as in “it’s” or “Fred’s”.


If that is your answer I will let @chrisofarabia try to reply. Reason is with so little information as to where the string will be used I am at a complete loss on how to answer your cryptic question… and I am hopeless at guessing games :frowning:

1 Like

It’s not guessing games, the apostrophe would be at the end of a name.

It depends on where the string is being used.

With grammar usage an apostrophe s indicates the following article belongs to the person.

Is English your first language?

Which end, right or left?

1 Like



Please post the code that does not place the apostrophe at the right end of the name as you expect it to,

a jsfiddle or codepen that demonstrates the error would be very helpful.

<meta content='ronpat's' name='keywords'/>

it converts the top text to the bottom.

<meta content='ronpat&apos;s' name='keywords'/>

it’s not an error.

Change it to: <meta content="ronpat's" name="keywords"/>

It should work just fine. You’ve got your single/double quotes messed up again.

1 Like

That’s a very smart conversion. I would have expected it to fail.

You had a strong discussion about the use of quotation marks with @TechnoBear. Her counsel was spot on. In your example code, the outer quote marks should be double-quotes, although that may not stop the conversion because you have not explained the use that is causing the conversion. Older software required some text entities to be coded as HTML entities for proper transmission on the internet. That was the standard of the day.

@asasass: yet again, you are running into difficulties unnecessarily by flying in the face of convention.

If you stick with the standard usage of double quotes (with single quotes nested inside them, if required), then you are very unlikely to run into a scenario where this will happen. This is exactly what I warned against in my last example.

IIRC, it was (is?) only required when using character encoding other than UTF-8, although there are still occasions where it’s required for escaping characters.

Discourse converts some entities, like < and > “on the fly” when you quote a post, for example.

[quote="asasass, post:14, topic:229409"]
&lt;meta content='ronpat's' name='keywords'/&gt;

THAT would be the flaw in my “memory” because I used ISO-8859-1 for the longest time…



I think that’s how blogger does it.