ultraedit can't recognise trademark ™

[woodyk]

I use ultraedit to sort some page code, while in Dreamweaver the trademark ™ can be recognised, but ultraedit can't, the mark is shown as a "?"

Could you give me some advise to solve the problem.

Thanks

[encyclo]

Welcome to the forums woodyk! It sounds like the two editors have differing opinions of the charset of the document. If you use the entity reference

™

does the character show up correctly?

[woodyk]

encyclo: thank you for your reply

The sequence of my creating a page is, first copy code from DW to ultraedit, then edit, then copy back to DW. So after the sequcence, the trademark ™ has been changed to "?".

Not only the trademark ™, but other marks like copyright are also changed.

[kaled]

I'm not familiar with UltraEdit, however...

When you say "Copy" are you talking about clipboard operations (i.e. cut/copy and paste)?

If yes, then the issue is likely to revolve around supported clipboard formats. The only likely solution will be a software update. However, you should be able to cut and paste in source-mode without difficulties.

Kaled.

[le_gber]

kaled nailed it! when copying, if you copy the source code, you shouldn't get any problem - try copying everything into notepad first and then DW.

Could I ask you why you use two editors?

[rocknbil]

. . . So after the sequcence, the trademark ™ has been changed to "?"

Even if you get this to work it will persist to be a problem on various browsers, especially if you're not using the correct document encoding. All "special" characters such as this should be replaced with HTML entities as encyclo suggested:

If you use the entity reference ™ does the character show up correctly?

If you fall into this habit you will find all sorts of?'s thoughout your documents, anything from em dashes - to a curly quote ', if the ascii value is greater than 127, use an html entity.

[woodyk]

Thanks all.

I use ultraedit to do some regular replaces and sortings, I can't find a way to edit an macro in DW :(

If HTMl entity used, there will be no problem. But transferring all these special characters (widely used in names) into entities is not an enjoyable job.

So, I think ultraedit should support these characters. Maybe I do something wrong, or maybe there is something hided in ultraedit.

[Robin_reala]

All "special" characters such as this should be replaced with HTML entities

That's the short-term fix. The longer but better solution is to transition your development process to Unicode.

[encyclo]

All "special" characters such as this should be replaced with HTML entities as encyclo suggested

Just to clarify this, ideally we would all be using UTF-8, where you can use the character directly without resorting to entity references except in exceptional circumstances.

I assume the document in question is declaring the charset of ISO-8859-1. The trouble with the ™ symbol is that the character does not exist in ISO-8859-1 (the most commonly-declared western European charset). It does however exist in the windows-1252 charset, and Windows always handles ISO-8859-1 as if it is windows-1252. Only using

™

will ensure cross-platform compatibility for a document declaring ISO-8859-1.

The bug is a Windows bug, as the two charsets seen as synonymous by the OS are in fact different. Ultraedit may be being more "correct", whereas Dreamweaver is handling the character encoding as windows-1252.

Useful reading:
[intertwingly.net...]
[webmasterworld.com...]