Google缓存版本中的字体是否错误？ [英] Wrong fonts in Google cached version?
问题描述
我刚开始玩CSS和MovableType。我的主页
（ http://www.jay.fm ）现在验证CSS和XHTML。
但是，Google缓存版本在IE6中显示错误的字体。这个
似乎是因为标题而导致的。它们放在< head>之前阻止;
如果我将缓存的副本保存到磁盘并编辑出来，它显示正常。
这不是什么大问题，但我在其他页面上没有注意到这个问题，所以
我想知道是否有人有任何关于如何防止它发生的见解。奇怪的是，样式表的其余部分似乎相当顺从
;这只是麻烦的字体。
-
Jay Levitt |
Wellesley，MA |嗨！
更快：jay at jay dot eff-em |我们去哪儿了？
http://www.jay.fm |为什么我在这个手提篮里？
I''m just starting to play around with CSS and MovableType. My home page
(http://www.jay.fm) now validates on both the CSS and the XHTML.
However, the Google cached version shows the wrong font in IE6. This
seems to be because of the "header" they place before the <head> block;
if I save the cached copy to disk and edit that out, it displays fine.
It''s not a big deal, but I don''t notice this problem on other pages, so
I wondered if anyone had any insights on how to prevent it from
happening. Oddly, the rest of the style sheet seems to be obeyed fairly
well; it''s only the fonts that are troublesome.
--
Jay Levitt |
Wellesley, MA | Hi!
Faster: jay at jay dot eff-em | Where are we going?
http://www.jay.fm | Why am I in this handbasket?
推荐答案
Jay Levitt写道：
Jay Levitt wrote:
我刚开始使用CSS和MovableType。
请原谅我的无知，但是什么是MovableType？
我的主页（ http://www.jay.fm ）现在验证CSS和
XHTML。
真的吗？
http://validator.w3.org/check?uri=http://www.jay.fm/
关于css，微缩字符是什么？
但是，Google缓存版本在IE6中显示错误的字体。
这不是全部。在Moz 1.6 / Win2k中，左侧的菜单位于缓存版本中的右侧
，其中部分内容已被覆盖。不是很漂亮。
这似乎是因为标题它们放在< head>
块之前;
他们使用的代码很奇怪。我认为必须有更好的方法来做到这一点。
也许缓存的文档应该被框架？
这不是什么大问题，但是我在其他页面上没有注意到这个问题，
所以我想知道是否有人对如何防止它发生有任何见解。
I''m just starting to play around with CSS and MovableType.
Excuse my ignorance, but what is "MovableType?"
My home page (http://www.jay.fm) now validates on both the CSS and
the XHTML.
Really?
http://validator.w3.org/check?uri=http://www.jay.fm/
Regarding the css, what''s with the microfonts?
However, the Google cached version shows the wrong font in IE6.
That''s not all. In Moz 1.6/Win2k, the menu that was on the left is on
the right in the cached version, and part of it is covered. Not real pretty.
This seems to be because of the "header" they place before the <head>
block;
Very odd code they use. I''d think there must be a better way to do this.
Perhaps the cached doc should be framed?
It''s not a big deal, but I don''t notice this problem on other pages,
so I wondered if anyone had any insights on how to prevent it from
happening.
由于缓存版本中的html无效，因此无法确定
a ua将使用它。据推测，如果服务器关闭，人们只会访问缓存的
版本。这经常发生吗？
-
Brian（从我的地址中删除无效给我发电子邮件）
http://www.tsmchughs.com/
在文章< 10 ************* @ corp.supernews.com>中，使用net3
@ julietremblay.com.invalid说...
In article <10*************@corp.supernews.com>, usenet3
@julietremblay.com.invalid says...
我刚开始玩CSS和MovableType。
请原谅我的无知，但是什么是MovableType？
I''m just starting to play around with CSS and MovableType.
Excuse my ignorance, but what is "MovableType?"
一个基于CGI的博客发布软件包，它实际上非常适用于
通用免费内容管理系统。它有一个可以让你做各种各样整洁的东西，当然还有
如果你愿意，你可以随时将PHP分层。内容是
生成一次到静态文件中，因此只要您发布的次数比人们阅读的少，b / b
就非常有效。
A CGI-based blog-publishing package that''s actually quite usable as a
general-purpose, free content management system. It''s got about a
zillion plugins that let you do all sorts of neat things, and of course
you can always layer PHP on top if you want to. The content is
generated once into static files, so as long as you publish less often
than people read, it''s very efficient.
我的主页（ http：// www。 jay.fm ）现在验证CSS和
XHTML。
My home page (http://www.jay.fm) now validates on both the CSS and
the XHTML.
真的吗？
http://validator.w3.org/check?uri=http ：//www.jay.fm/
该死的。它在几个小时前完成...然后我剪切并粘贴BlogStreet
图标，这样我就可以在那里列出，并且没有眼球或重新验证它。
有什么特别奇怪的是他们懒得关闭img标签，但是他们不会在边境地区附上报价！
Bad Jay。现在好多了。
关于css，微缩字是什么？
是的，当你的默认字体是小b $ b $时，标准字体大小不能很好地扩展（尽管我发现它们在较小的情况下非常易读）在IE中）。我看到了一篇非常好的文章，它已经计算出所有字体偏好大小都有意义的百分比（或者可能是ems）
，但是我再也找不到了希望我会再遇到它。
Damn. It did a few hours ago... then I cut-and-paste the BlogStreet
icon so I could get listed there, and didn''t eyeball or revalidate it.
What''s particularly odd is that they DO bother to close the img tag, yet
they don''t put quotes around the border property!
Bad Jay. All better now.
Regarding the css, what''s with the microfonts?
Yeah, the standard font sizes don''t scale well when your default font is
small (though I find them quite readable at "Smaller" in IE). I saw a
really great article that had worked out percentages (or perhaps ems)
that made sense at all font-preference sizes, but I can no longer find
it.. hopefully I''ll run across it again.
但是，Google缓存版本在IE6中显示错误的字体。
那个'不是全部。在Moz 1.6 / Win2k中，左侧的菜单位于缓存版本的右侧，其中部分内容已被覆盖。不是真的很漂亮。
However, the Google cached version shows the wrong font in IE6.
That''s not all. In Moz 1.6/Win2k, the menu that was on the left is on
the right in the cached version, and part of it is covered. Not real pretty.
哦，当我正在调整中间时，它被缓存了，并且
从两列移动到三列格式。 （按照我的点击率获得，我不需要进行测试和制作演出
系统..）今晚' GoogleBot应该拿起新的。但字体
问题在整个过程中都非常一致。
实际上，我只注意到了一些事情：*第一次*你去的时间
缓存副本，字体正常，但更大。重新加载不做任何奇怪的事情，但回到Google列表，然后点击缓存上的
再次拉出一个罗马化的页面。
我不知道是不是因为font-family只在body
选择器中定义，并且BODY标签不在缓存的
副本中的预期位置。我打算尝试在＃content，
#navAlpha和#navBeta选择器中重新指定字体，看看今晚会发生什么。
Oh, that just got cached while I was in the middle of tweaking and
moving from a two-column to a three-column format. (At the hit rates I
get, I don''t really need to have a "test" and "production" staging
system..) Tonight''s GoogleBot should pick up the new one. But the font
problem has been pretty consistent throughout.
Actually, I just noticed something: The *first* time you go to the
cached copy, the fonts are normal, but larger. Reloading doesn''t do
anything weird, but going back to the Google listing and then clicking
on "Cached" again pulls up a times-romanized page.
I wonder if it''s because the font-family is defined only in the body
selector, and the BODY tag isn''t in the expected place in the cached
copy. I''m going to try re-specifying the font in the #content,
#navAlpha and #navBeta selectors and see what happens tonight.
这个似乎是因为标题它们放在< head>
块之前;
This seems to be because of the "header" they place before the <head>
block;
他们使用非常奇怪的代码。我认为必须有一个更好的方法来做到这一点。
也许缓存的文档应该被框架？
Very odd code they use. I''d think there must be a better way to do this.
Perhaps the cached doc should be framed?
是的，当然然后他们现在必须为每一个
提供两页。我一直在想，如果有一个内联框架，那将是多么美好。
- 不像IFRAME，而是嵌入另一个内部的HTML文档。一周或两周之前，我有另一个
用于其中一个。在任何情况下，这显然是我无法控制的价值。
Yeah, though of course then they''d have to serve up two pages for every
one now. I keep thinking how nice it''d be if there was an inline frame
- not like IFRAME, but an HTML doc nested inside another. I had another
use for one of those a week or two ago. In any case, that''s obviously
outside of my control.
这不是什么大不了的事，但我没有注意到其他页面上的这个问题，
所以我想知道是否有人对如何防止它发生有任何见解。
It''s not a big deal, but I don''t notice this problem on other pages,
so I wondered if anyone had any insights on how to prevent it from
happening.
由于缓存版本中的html无效，因此无法确定ua将使用它做什么。据推测，如果您的服务器关闭，人们只会访问缓存的版本。这经常发生吗？
Since the html in the cached version is invalid, there''s no telling what
a ua will do with it. Presumably, people would only access the cached
version if your server is down. Does that happen often?
不，但我认为我不是唯一一个在谷歌搜索时本能地点击
缓存副本的人所以我可以更快地浏览。谷歌的缓存是
几乎总是比任何网站都快，而且除了我的以外的任何网站，
似乎做得很好。显然他们的HTML无效，但由于某些原因我的网站特别容易让IE混淆......
-
Jay Levitt |
Wellesley，MA |嗨！
更快：jay at jay dot eff-em |我们去哪儿了？
http://www.jay.fm |为什么我在这个手提篮里？
No, but I presume I''m not the only one who instinctively clicks on
cached copies when Googling so I can browse faster. Google''s cache is
nearly always faster than any web site, and on any site other than mine,
seems to do a good job rendering. Obviously their HTML is invalid, but
for some reason my site is particularly confusing to IE...
--
Jay Levitt |
Wellesley, MA | Hi!
Faster: jay at jay dot eff-em | Where are we going?
http://www.jay.fm | Why am I in this handbasket?
Jay Levitt写道：
Jay Levitt wrote:
我们***** @ julietremblay.com.inva 盖子说......
us*****@julietremblay.com.invalid says...
关于css，微缩字是什么？
是的，当您的默认字体很小时，标准字体大小不能很好地扩展（尽管我发现它们在IE中的较小处非常易读）。我看到了一篇非常精彩的文章，其中列出了所有字体偏好大小都有意义的百分比（或者可能是ems），但是我可以不再找到它了......希望我能我会再遇到它。
Regarding the css, what''s with the microfonts?
Yeah, the standard font sizes don''t scale well when your default font
is small (though I find them quite readable at "Smaller" in IE). I
saw a really great article that had worked out percentages (or
perhaps ems) that made sense at all font-preference sizes, but I can
no longer find it.. hopefully I''ll run across it again.
除非这个MoveableType的东西改变了什么，否则它没什么用的。不要在body，p，ul等中设置任何字体大小。设置字体大小
仅适用于H1，H2等。
There''s not much to it, unless this MoveableType thing changes
something. Don''t set any font size in body, p, ul, etc. Set font sizes
only for things like H1, H2, etc.
但是，Google缓存版本在IE6中显示错误的字体。
我想知道是否因为字体系列仅在body
选择器，并且BODY标签不在缓存的
副本中的预期位置。
However, the Google cached version shows the wrong font in IE6.
I wonder if it''s because the font-family is defined only in the body
selector, and the BODY tag isn''t in the expected place in the cached
copy.
这是有道理的，因为html中不需要body标签。内容开始时假设为
。这可能会影响css。
他们使用的代码很奇怪。我认为必须有一个更好的方法来做这个。也许缓存的文档应该被框起来？
That would make sense since the body tag isn''t required in html. It is
assumed when the content starts. That might impact the css.
Very odd code they use. I''d think there must be a better way to do
this. Perhaps the cached doc should be framed?
是的，当然，他们现在必须为每个人提供两页。
Yeah, though of course then they''d have to serve up two pages for
every one now.
是的。 （思考）好的，为什么Google不会在
< body>之后插入那些东西。标签和任何文档内容之前？
我一直在想如果有一个内联框架会有多好 - 不像IFRAME那样，而是嵌入另一个内部的HTML文档。
我认为< object>应该能够处理，但浏览器
支持很差。
我认为我不是唯一一个本能地点击缓存的人
谷歌搜索时复制，以便我可以更快地浏览。
我只是这样做才能看到Google在其缓存中有哪些页面我已经创作了
.
Google'我的缓存几乎总是比任何网站都快。
True. (thinking) Ok, why doesn''t Google insert there stuff after the
<body> tag and before any document content?
I keep thinking how nice it''d be if there was an inline frame - not
like IFRAME, but an HTML doc nested inside another.
I think <object> is supposed to be able to handle that, but browser
support is poor.
I presume I''m not the only one who instinctively clicks on cached
copies when Googling so I can browse faster.
I''ve only done that to see what Google has in its cache for pages I
authored.
Google''s cache is nearly always faster than any web site
我觉得你从谷歌这样浏览网页很有吸引力。
作者真的不知道他的文件将如何被查看。
当然，如果有很多人这么做的话，这对我来说很麻烦
因为谷歌经常需要1或甚至2个月来重新索引我的页面。 >
网站。而且我已经看过其他页面 - 特别是最近的页面
添加了一个链接到我已经完成的网站 - 在Google的缓存中保持不变
甚至更长。
-
Brian（从我的地址中删除无效给我发电子邮件）
这篇关于Google缓存版本中的字体是否错误？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
