| T O P I C R E V I E W |
| Martin1 |
Posted - 24 Nov 2006 : 16:25:14
I probably am .
But I thought that special characters placed inside a standard label were, when the page is exported, automatically changed into the appropriate html code.
I just tested a few and the only one of this random list ? & ? ? ? that is exported into html code is & = & the others aren't. This is no good because now I am starting to get into trouble with my cms[2 :-((].
This list should thus read:
? = & euro ;
& = & amp ;
? = & agrave ;
? = & Eacute ;
? = & copy ;
Obviously there shouldn't be any blank spaces in the code but otherwise the forum messes up the way one can view them.
Martin |
| 23 L A T E S T R E P L I E S (Newest First) |
| s.dav |
Posted - 17 Dec 2006 : 11:20:25
If I remember right I've used the numerical translation because it's simpler and because some textual translations don't work when exporting XML. |
| Martin1 |
Posted - 17 Dec 2006 : 00:52:39
Hello davide.
Sorry for the delay in answering but I have been out of town for a few days.
quote:
Good, so in your opinion is it correct to translate every char from 128 to 255 (Extended ASCII chars)?
Well at least every character from 160 to 255. I am not sure about the characters before 160.
The w3c page I mentioned earlier
http://www.w3.org/TR/REC-html40/sgml/entities.html#h-24.2.1
only lists 160 to 255
but this w3c page
http://www.w3.org/MarkUp/html-spec/html-spec_13.html
mentiones numbers
09 to 14
32 to 48
58 to 65
91 to 97
123 to 127
and 160 to 255
I am also not sure if using the numerical translation is the way to go or if you should use the text translation (so instead of & #169 ; using the & copy ; for the copyright symbol)?
Would that make any difference? All I can say on this is that Adobe GoLive uses the textual translation instead of the numerical and w3c leans, on the two pages given above, towards the numerical.
Martin |
| s.dav |
Posted - 14 Dec 2006 : 14:05:45
Good, so in your opinion is it correct to translate every char from 128 to 255 (Extended ASCII chars)?
I'll make a numerical translation so '?' will become #169; |
| Martin1 |
Posted - 14 Dec 2006 : 12:45:23
Answer 1:
If I read point 24.2 right and when I look at point 24.2.1 on the w3c site
http://www.w3.org/TR/REC-html40/sgml/entities.html#h-24.2.1
these characters (only numbers 160 to 255) are indeed part of the iso-8859-1 charset.
quote:
the ASCII standard encoding covers chars from 0 to 127 so they don't need translation
As you can see on the w3c site their recommendation is to use the html code for these characters. They might not need it but it's recommended.
Answer 2:
My problem with the utf8 is that although I use some of these characters (like % and @) the page doesn't get exported with utf8 at all.
I am not to sad about that because my Content Managment System can't deal with utf8. When pages are with this encoding the special characters are changed to question marks.
Besides that, when I was still using Adobe GoLive I never used utf8 but did use special characters and never had any problems.
GoLive automatically changed the special characters into the correct html code.
Answer 3:
I have no REAL problems but as you know I like to keep my pages in accordance with the w3c recommendations (so that means special characters should be written like ? = & copy ;).
Just as an example:
For the characters ?, ?, ?, & % and @ I have exported the page with the utf8 and the iso-8859-1 charsets and it didn't make any difference. The source of the pages didn't contain the correct html codes even though the % and @ are part of the characterset below number 160)
? = & uuml ;
? = & eacute ;
? = & ouml ;
& = & amp ;
% = & #37 ;
@ = & #64 ;
quote:
If you have a sample send it to me and I'll try!
I am not entirely sure what kind of sample you want form me[2 H:...(].
Martin |
| s.dav |
Posted - 14 Dec 2006 : 10:33:21
@Martin,
I've made the change to the code but this has made me to think...
D.H.E., when using UTF8 encoding, doesn't change any chars (except for &, <, >)
when NOT using UTF8 it translates each chars that has the ordinal major than 255 (because they are UNICODE and cannot be displayed without UNICODE); for example if we suppose that the char "*" has the ordinal 258 D.H.E. will encode it as #258; (* has the ordinal 42)
the ASCII standard encoding covers chars from 0 to 127 so they don't need translation
so the chars you're referring are those with ordinal from 128 to 255.
These chars are within the encoding chosed for your page so you should search the right encoding for them.
1 question:
Are you sure that the iso-8859-1 charset contains these chars?
2 question:
What problems do you have when using the UTF8 charset?
3 question:
What problems do you have when NOT using the UTF8 charset with these chars?
If you have a sample send it to me and I'll try!
I'm making you these questions because I'm trying to understand how to move on...[4 :?] |
| Martin1 |
Posted - 13 Dec 2006 : 17:55:26
I wil never understand people who do these kind of things to other peoples property. I mean cars are expensive objects so why can folks be more carefull with stuff that doesn't belong to them or simpy keep their hands of?
Anyway back to the subject at hand.
I don't want to use the utf8 charset because this gives me huge problems with my cms. Besides that the utf8 isn't neccesary just for the use of the html special characters codes.
The 'normal' iso-8859-1 charset also works fine with the characters if the correct html code is used.
Please, please Davide[5 ppp] add the character set. Pretty please[2 H:)].
If not, I will tell you girlfriend! Yeah that makes you crawl in fear doesn't it[3 ~-)].
Martin
|
| s.dav |
Posted - 13 Dec 2006 : 17:38:28
My car has been opened two times, so I've changed two keys :-(
@Martin,
Have you tried to create the page using the UTF8 charset? I think this should already fix your problem; D.H.E. translates every char from 149 to 160 (bullet, dash, tm, etc...) plus &, <, >, euro, bullet, space.
If it finds chars with ordinal major than 255 (so UNICODE), it creates UTF8 files.
For the UTF8 charset the strange encoding ### doesn't serve at all... |
| Martin1 |
Posted - 13 Dec 2006 : 16:53:14
Yeah  I don't understand people. I mean something can always happen but for gods sake leave a message or something an let the insurance company sort it out but don't just leave me behind with damage.
|
| arov |
Posted - 13 Dec 2006 : 15:47:04
@Martin
nooooooooooooooooooooo the car is untouchable!!! (also my car is damaged)
The world is full of bastards!
::arov:: |
| Martin1 |
Posted - 13 Dec 2006 : 15:11:29
@ Arov
I am sad indeed. I just saw that some bastard damaged my car[2 H:..(] AGAIN!!!
@ Waldorfio
I am in totall agreemend with you. I love the new sleek interface. The properties panel looks better and I already thought it looked excellent with the previous version .
@Davide
Maybe you should try to keep your hands off of the girlfriend so she doesn't distract you[3 ~-)].
The list might be huge but even w3c has the list
http://www.w3.org/MarkUp/html-spec/html-spec_13.html
why do you think this is not a good idae?
Martin (without girlfriend so always focused[3 :p]) |
| Waldorf |
Posted - 13 Dec 2006 : 14:23:34
tssss, pffff! ;-) |
| s.dav |
Posted - 13 Dec 2006 : 13:59:56
@Martin,
yes it's the age  ... and my girlfriend [2 puppy]
I'll fix it asap!
Just seen the list of HTML special chars... but it's huge...are you sure you want all these specials chars translated? I think this is not a good idea...
http://www.degraeve.com/reference/specialcharacters.php
@Waldorf
The icons are good but completely different from the old ones;
the white papers say nothing in my opinion...
I think you should create icons enhancing the old ones [2 OOO] using the heart as background image 
|
| Waldorf |
Posted - 13 Dec 2006 : 12:49:56
@Aston Martin1
He also, didn't like the icons, I've made especially for DHE, [2 (==)] so don't complain [2 H:)]
*but... I adore the PRO "no-nonsens" new interface [2 :D]
* |
| arov |
Posted - 13 Dec 2006 : 12:31:56
Davide, please... help Martin, is sad... [2 H:..(]
::arov:: |
| Martin1 |
Posted - 13 Dec 2006 : 12:10:19
The pit bull terrier is back[2 H:)].
I was kinda hoping the appropriate code would be added to this new version for ALL the special characters
(for example:
? = & euro ;
& = & amp ;
? = & agrave ;
? = & Eacute ;
? = & copy ;
obviously all the others as well)
But I see in this new version the code hasn't changed[2 H:..(].
The only one that is correct is & amp ; the other ones are still plain.
Davide you said you would change them. Did you forget my friend? Is old age starting to kick in.
Martin |
| Martin1 |
Posted - 29 Nov 2006 : 19:58:03
Hahahahaha you are right Waldorf! Sometimes I am just like a pitbull terrier. I don't mean to be rude or even forcefull but simetimes I can't help myself sounding like it.
I hope Davide doesn't take offence because I am just trying to get my point accross and improve DHE.
If I offended you Davide or anyone else I do appologize!
|
| Waldorf |
Posted - 29 Nov 2006 : 18:56:00
@pitbull-terrier1
very picky idd.tsss[2 :D]
now, we are equal > SU's  |
| Martin1 |
Posted - 29 Nov 2006 : 17:59:42
Are you planning of doing the others as well?
Martin |
| s.dav |
Posted - 29 Nov 2006 : 17:56:53
The & is aldready translated |
| Martin1 |
Posted - 29 Nov 2006 : 13:46:25
I don't want to be picky but you should translate them all.
I made a list for you with all of the special characters that, when used, should be converted to html code.
Just go here and take a look and add them to dhe if you can and want to of course[2 H:)]. It would be a great improvement.
http://www.albruna.nl/voorbeeld/special.html
|
| s.dav |
Posted - 28 Nov 2006 : 22:34:23
Ok I'll translate them! |
| Martin1 |
Posted - 28 Nov 2006 : 14:24:16
Sorry for the delay in answering but i took a few very needed days of.
My problem is that when I type these special characters in the standard label and I export the page they are not modified to the appropriate html code.
Martin |
| s.dav |
Posted - 25 Nov 2006 : 14:50:00
So what is your problem? Should I translate also the others? |
