Adobe GoLive 6 - 采用UTF-8编码的令人讨厌的功能 [英] Adobe GoLive 6 - Nasty feature with UTF-8 encoding

查看:69
本文介绍了Adobe GoLive 6 - 采用UTF-8编码的令人讨厌的功能的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

最近我在GoLive 6中编辑了一个文档。我喜欢GoLive,因为它有一些不错的

功能,例如:

*重写源代码

*检查语法

*全球搜索&替换(通过几个文件一次)

*正则表达式搜索&替换。


通常我的文档是用ISO设置编码的。


最近我写了一个XHTML文档。将编码更改为UTF-8后,我使用了

GoLive''重写源代码''功能。大错。它将我所有有趣的角色改为

非符合SGML标准的角色(例如& eacute;被转换为é),直到

之后我才注意到我保存了文件。讨厌。用ISO编码的文件不能做到这一点。

Recently I was editing a document in GoLive 6. I like GoLive because it has some nice
features such as:
* rewrite source code
* check syntax
* global search & replace (through several files at once)
* regular expression search & replace.

Normally my documents are encoded with the ISO setting.

Recently I was writing an XHTML document. After changing the encoding to UTF-8 I used the
GoLive ''rewrite source code'' feature. Big mistake. It changed all my funny characters to
non-SGML compliant characters (e.g. é was converted to é) and I didn''t notice until
after I''d saved the document. Nasty. It doesn''t do that with ISO encoded documents.

推荐答案

Zenobia< 5. ******** **@spamgourmet.com>写道:
Zenobia <5.**********@spamgourmet.com> wrote:
最近我写了一个XHTML文档。将编码更改为UTF-8后,我使用了
GoLive''重写源代码''功能。大错。它将我所有有趣的角色改为
非符合SGML的角色(例如& eacute;被转换为é)
Recently I was writing an XHTML document. After changing the encoding to UTF-8 I used the
GoLive ''rewrite source code'' feature. Big mistake. It changed all my funny characters to
non-SGML compliant characters (e.g. &eacute; was converted to é)




没有什么非符合é。它存在于UTF-8中,因此如果

UTF-8是声明的编码,则完全可以使用它。这个

也适用于包含é的任何编码,例如

ISO-8859-1等。无论您的文档是HTML还是XHTML,都是如此。 />

但是,一个符合SGML兼容的XHTML文档?当然那是'b
矛盾。 ;-)


史蒂夫


-

我的理论给你起见,我的异端邪说你,

我从不回信,你也不喜欢我的领带。 - 医生


Steve Pugh< st *** @ pugh.net> < http://steve.pugh.net/>



There''s nothing non-compliant about é. It exists in UTF-8 therefore if
UTF-8 is the declared encoding it is perfectly okay to use it. This
would also be the case for any encoding that contained é, e.g.
ISO-8859-1 etc. This is true whether your document is HTML or XHTML.

However, an XHTML document that is "SGML compliant"? Surely that''s an
oxymoron. ;-)

Steve

--
"My theories appal you, my heresies outrage you,
I never answer letters and you don''t like my tie." - The Doctor

Steve Pugh <st***@pugh.net> <http://steve.pugh.net/>


Zenobia< 5. ********** @ spamgourmet.com>写道:
Zenobia <5.**********@spamgourmet.com> wrote:
最近我写了一个XHTML文档。将编码更改为UTF-8后,我使用了
GoLive''重写源代码''功能。大错。它将我所有有趣的角色改为
非符合SGML的角色(例如& eacute;被转换为é)
Recently I was writing an XHTML document. After changing the encoding to UTF-8 I used the
GoLive ''rewrite source code'' feature. Big mistake. It changed all my funny characters to
non-SGML compliant characters (e.g. &eacute; was converted to é)




没有什么非符合é。它存在于UTF-8中,因此如果

UTF-8是声明的编码,则完全可以使用它。这个

也适用于包含é的任何编码,例如

ISO-8859-1等。无论您的文档是HTML还是XHTML,都是如此。 />

但是,一个符合SGML兼容的XHTML文档?当然那是'b
矛盾。 ;-)


史蒂夫


-

我的理论给你起见,我的异端邪说你,

我从不回信,你也不喜欢我的领带。 - 医生


Steve Pugh< st *** @ pugh.net> < http://steve.pugh.net/>



There''s nothing non-compliant about é. It exists in UTF-8 therefore if
UTF-8 is the declared encoding it is perfectly okay to use it. This
would also be the case for any encoding that contained é, e.g.
ISO-8859-1 etc. This is true whether your document is HTML or XHTML.

However, an XHTML document that is "SGML compliant"? Surely that''s an
oxymoron. ;-)

Steve

--
"My theories appal you, my heresies outrage you,
I never answer letters and you don''t like my tie." - The Doctor

Steve Pugh <st***@pugh.net> <http://steve.pugh.net/>


2004年4月10日星期六12:11:54 +0100,Steve Pugh< st ** *@pugh.net>写道:
On Sat, 10 Apr 2004 12:11:54 +0100, Steve Pugh <st***@pugh.net> wrote:
Zenobia< 5. ********** @ spamgourmet.com>写道:
Zenobia <5.**********@spamgourmet.com> wrote:
最近我写了一个XHTML文档。将编码更改为UTF-8后,我使用了
GoLive''重写源代码''功能。大错。它将我所有有趣的角色改为
非符合SGML的角色(例如& eacute;被转换为é)
Recently I was writing an XHTML document. After changing the encoding to UTF-8 I used the
GoLive ''rewrite source code'' feature. Big mistake. It changed all my funny characters to
non-SGML compliant characters (e.g. &eacute; was converted to é)



没有任何不符合é的内容。它存在于UTF-8中,因此如果UTF-8是声明的编码,则完全可以使用它。对于任何包含é的编码也会如此,例如
ISO-8859-1等。无论您的文档是HTML还是XHTML,都是如此。



There''s nothing non-compliant about é. It exists in UTF-8 therefore if
UTF-8 is the declared encoding it is perfectly okay to use it. This
would also be the case for any encoding that contained é, e.g.
ISO-8859-1 etc. This is true whether your document is HTML or XHTML.




我将这些字符输入到XHTML文档中:


& plusmn; &安培;度; & auml;


它通过W3c XHTML验证器验证确定。


这是GoLive 6在''重写源代码'后显示的内容'


?±?°?¤


这些是由IE6呈现的字符:


±°?


这是我使用W3c XHTML验证(修改过的)文档时得到的错误消息

验证器:


抱歉,我无法验证此文档,因为在第11行它包含了一个或多个字节,我无法将其解释为us-ascii(换句话说,找到的字节

在指定的字符编码中不是有效值。请检查

文件的内容和字符编码指示。


嗯,相应的数字代码是:


±°ä


(我想w3c验证器也会接受这些)。


这些字符怎么样(±° ?或者2-char版本)如果

W3C验证器不接受它们,则是有效的UTF-8字符?或者W3C验证器不能正常工作吗?


我也迷失了为什么在GoLive编辑器中显示为±?等等。这个角色是

± - 当然这只是一个字节的字符。 GoLive应该显示为±


你将如何使用GoLive编写XTHML有效代码 - (a)使用文档集

来使用UTF-8编码(但没有''重写源代码''功能的好处。或者

(b)使用ISO-8859-1,这样你就可以使用''重写源代码' '功能?



I entered these character into an XHTML document:

&plusmn; &deg; &auml;

It validated OK by the W3c XHTML validator.

This is what GoLive 6 displays after ''rewrite source code''

?± ?° ?¤

These are the characters, as rendered, by IE6:

± ° ?

This is the error message I get when I validate the (modified) document with the W3c XHTML
validator:

Sorry, I am unable to validate this document because on line 11 it contained
one or more bytes that I cannot interpret as us-ascii (in other words, the bytes
found are not valid values in the specified Character Encoding). Please check
both the content of the file and the character encoding indication.

Well, the corresponding numeric codes are:

± ° ä

(I suppose the w3c validator would also accept these).

How can these characters (± ° ?, or the 2-char versions) be valid UTF-8 characters if the
W3C validator doesn''t accept them? Or does the W3C validator not work correctly?

I''m also lost as to why ± is shown in the GoLive editor as ?±, etc. That character is
± - surely this is just a one byte character. GoLive should display it as ±

How would you go about writing XTHML valid code using GoLive - (a) with the document set
to use UTF-8 encoding (but without the benefit of the ''rewrite source code'' feature. OR
(b) using ISO-8859-1, so that you are able to use the ''rewrite source code'' feature?


这篇关于Adobe GoLive 6 - 采用UTF-8编码的令人讨厌的功能的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆