Special Characters / HTML Entities -...

User 116462 Photo


Registered User
129 posts

Wayan Jaya Space Cadet wrote:
Bosco wrote:
Wayan,

I'm missing something. I see a copyright symbol in unicode is U+00A9 or the html code © or an escape code \u00A9. Which one are you using? I can't seem to get any of them to work in the text. Just how are you pasting these?


I have put a file into my resources (named =special characters)
in that file is a list of all the characters using the keyboard for window (don't have Mac)
This list includes both the code copyright = alt +0169 and the special character this would display.
I then simply highlight the character (not the code) copy & paste it into the text wherever I want it to go.
I would make a short video to show the process but am having trouble with the video editor at the moment, I am working on it so I can show people , maybe another hour or so


I might be missing something fundamental here...
Years ago, before using SD, I would always run my code through a "Tidy" routine to convert special characters to html conform format. I somehow took for granted that SD would do that automatically when exporting the site. Being in Spain, I write a lot of special characters and only recently I realised that the html code created by SD does not do anything to convert those characters.
Using the html element is really not practical in my case, so the best bat is to cleanup the code manually with html editor after exporting it. Has it been suggested to Coffecup to add a similar option to SD as they have in the html editor?
Regards
Berthold, Spain
Astronomy site: http://www.astronomy.artinso.com
Musical events: http://www.orphelion-ensemble.com
ED V4, SD V5
User 122279 Photo


Senior Advisor
14,456 posts

Everything from Coffeecup, for the last 10 years or so, is using the 'utf-8' character set. That means, that you should be able to write the different letters 'as they come. As for myself, I'm using Norwegian (we have our 'ÆØÅ' funnies). I'm also using German, with ÄÖÜ and the sharp S. No problem with the French special characters either, not even with Turkish, but I have no experience with Spanish. But I would think that all the European Latin-based alphabets can be used 'as is'.

What I'm saying is, for example that a German ö or a Norwegian ø will look exactly the same 'under the hood' (aka in the code), they don't have to be changed to ö or ø
So my guess is, that a code cleaner hasn't been found necessary.
Ha en riktig god dag!
Inger, Norway

My work in progress:
Components for Site Designer and the HTML Editor: https://mock-up.coffeecup.com


User 116462 Photo


Registered User
129 posts

Inger wrote:
Everything from Coffeecup, for the last 10 years or so, is using the 'utf-8' character set. That means, that you should be able to write the different letters 'as they come. As for myself, I'm using Norwegian (we have our 'ÆØÅ' funnies). I'm also using German, with ÄÖÜ and the sharp S. No problem with the French special characters either, not even with Turkish, but I have no experience with Spanish. But I would think that all the European Latin-based alphabets can be used 'as is'.

What I'm saying is, for example that a German ö or a Norwegian ø will look exactly the same 'under the hood' (aka in the code), they don't have to be changed to ö or ø
So my guess is, that a code cleaner hasn't been found necessary.


Thanks for the clarification! Si, in that case, the warnings from the html validators can be safely ignored?
Berthold, Spain
Astronomy site: http://www.astronomy.artinso.com
Musical events: http://www.orphelion-ensemble.com
ED V4, SD V5
User 122279 Photo


Senior Advisor
14,456 posts

That depends on what kind of warnings you get. What are they warning you about?
Ha en riktig god dag!
Inger, Norway

My work in progress:
Components for Site Designer and the HTML Editor: https://mock-up.coffeecup.com


User 379556 Photo


Registered User
1,535 posts

Just a thought: in the Page Manager, third item down in general settings, it would be interesting to know
a. what language would be set by the Detect button, and
b. whether the use of a different language setting (perhaps testing all the likey ones) would help.

Frank

Have something to add? We’d love to hear it!
You must have an account to participate. Please Sign In Here, then join the conversation.