Why doesn't vBulletin software recognize simple special characters like the degree symbol? You know the little circle superior to the numbers. Type 75? and you get 75?, not the little superior circle.
-
-
-
? ?
Alt 0176
Dammit .. never noticed that before.Roses are red. Tacos are enjoyable. Don't blame immigrants, because you're unemployable.
T-11 Flaccid Paraplegic due to TM July 1985 @ age 12Comment
-
Comment
-
Dems fightin words San Franny..Roses are red. Tacos are enjoyable. Don't blame immigrants, because you're unemployable.
T-11 Flaccid Paraplegic due to TM July 1985 @ age 12Comment
-
I think you have to use the exponent function for that, which is available only if you use Go Advanced reply.Originally posted by t8burst View Post
(KLD)The SCI-Nurses are advanced practice nurses specializing in SCI/D care. They are available to answer questions, provide education, and make suggestions which you should always discuss with your physician/primary health care provider before implementing. Medical diagnosis is not provided, nor do the SCI-Nurses provide nursing or medical care through their responses on the CareCure forums.Comment
-
Originally posted by t8burst View PostYes you do. In the example below, I followed your suggestion "KLD" (the other moderator was less than helpful). I selected "Go Advanced," then the superscript, typed 75 and option/shift "8." You can see the result. Thanks for your suggestion.Originally posted by SCI-Nurse View Post
I also notice if you copy something from an article on the internet and paste it into a post, and if that copy has special characters you get question marks instead.Attached FilesComment
-
-
Bah, moved out of the city, too many smelly hippies. Down in the silly con valley now. Oh and KLD has it wrong, there is a way to put any special character in the text for example one for prescriptions: ℞Originally posted by lynnifer View Post
Or one you would like ℠ (because I know you are fond of service marks).
Comment
-
I?ve been having text encoding issues for a little while now. Maybe a couple/few weeks.
Quotes and apostrophes aren?t being converted correctly at post time. I can go back and edit them in, and they show up fine during preview, but during the initial post encoding they?re not being recognized and are being replaced with question mark (normal for encoding error).
I don?t know if something changed in the character set of iOS, which recently updated to v11, or what, but it?s annoying."I have great faith in fools; self-confidence my friends call it." - Edgar Allen Poe
"If you only know your side of an issue, you know nothing." -John Stuart Mill, On LibertyComment
-
Try pasting in as plain text or I gues on a mac it's "match style". It a problem with the character encoding
Originally posted by Oddity View PostComment
-
Originally posted by t8burst View Post
I?ve been using an iPhone for posting here since they came out and haven?t ever had an issue until the past few weeks. Trying to nail down what changed and unless some backend update happened to the server/servers/cloud that hosts this site all I?ve got to go on is the recent iOS update. No info on character set included in the patch notes though.
As far as I know, there isn?t a way to natively generate plain text on an iPhone. Maybe there?s an app for ?dat.
What?s odd is that I can edit and save the quotes back into a post, and they also appear while previewing the post, it?s only during the initial submission and insertion into the database that the character encoding for quotes goes wrong.
Anyone else using an iPhone on the latest iOS experiencing the same thing?
ETA: Ok, looks like iOS 11.1.x has some Unicode text formatting bugs. There question marks appearing all over the internet in iOS 11.1 users posts. Apple rules. They say they fixed some Unicode bugs in 11.1.1 but some still exist, apparently.Last edited by Oddity; 14 Nov 2017, 9:12 AM."I have great faith in fools; self-confidence my friends call it." - Edgar Allen Poe
"If you only know your side of an issue, you know nothing." -John Stuart Mill, On LibertyComment
-
The new IOS is crap. I constantly have to restart my phone because it loses it mind when it can't find the network in my garage. As a work around I put it in airplane mode until I get outside the garage and back in coverage.
Originally posted by Oddity View PostI?ve been using an iPhone for posting here since they came out and haven?t ever had an issue until the past few weeks. Trying to nail down what changed and unless some backend update happened to the server/servers/cloud that hosts this site all I?ve got to go on is the recent iOS update. No info on character set included in the patch notes though.
As far as I know, there isn?t a way to natively generate plain text on an iPhone. Maybe there?s an app for ?dat.
What?s odd is that I can edit and save the quotes back into a post, and they also appear while previewing the post, it?s only during the initial submission and insertion into the database that the character encoding for quotes goes wrong.
Anyone else using an iPhone on the latest iOS experiencing the same thing?
ETA: Ok, looks like iOS 11.1.x has some Unicode text formatting bugs. There question marks appearing all over the internet in iOS 11.1 users posts. Apple rules. They say they fixed some Unicode bugs in 11.1.1 but some still exist, apparently.Comment
-
An update just dropped a few minutes ago, I wonder if it?s fixed....Originally posted by t8burst View Post
???????????????
...sigh..."I have great faith in fools; self-confidence my friends call it." - Edgar Allen Poe
"If you only know your side of an issue, you know nothing." -John Stuart Mill, On LibertyComment
-
I'm not using iOS. When I have the problem I described earlier, I am using MacOS High Sierra version 10.13.1.Originally posted by Oddity View PostComment
-
That update yesterday with iphone was supposed to solve the ?'boxed A' problem ... I have a 6 and when it dies, never Apple again!
Hello Android.Roses are red. Tacos are enjoyable. Don't blame immigrants, because you're unemployable.
T-11 Flaccid Paraplegic due to TM July 1985 @ age 12Comment
Comment