ciwas mFAQ的第三个测试帖 [英] Third test post of ciwas mFAQ
问题描述
我已经在这个建议的新mFAQ版本上做了更多工作，试图将所有用户输入混合到文本中。
另一篇评论由NG会受到欢迎。
=====
存档名称：www / stylesheets / newsgroup-faq
发布频率：每周一次
最后修改日期：2004年7月22日
版本：2.00
网址：< http ：//css.nu/faq/ciwas-mFAQ.html>
维护者：Jan Roland Eriksson< re*@css.nu>
comp .infosystems。 www.authoring.stylesheets meta-FAQ v2.00
__________________________________________________ ____________________
00：===== TOC =====
01：什么是< comp.infosystems .www.authoring.stylesheets> ？
02：这个新闻组可以接受哪些帖子？
03：这个新闻组可以接受哪些帖子？
04：这个新闻组不接受哪些帖子？
05：这个新闻组的技术资源在哪里？
06：我怎么得到对我的文章做出最好的回应？
07：ciwas的氛围是什么？
08：我在哪里可以找到这个常见问题的最新版本？
09：====结束====
__________________________________________________ ____________________
01：==== = Q& A =====
问：什么是< comp.infosystems.www.authoring.stylesheets>
答：这是根据< news.announce.newgroups>中报道的未经审核的新闻组通过了创建，获得了166：19的
票数。 on
1997-03-20。
这个新闻组的章程取自投票结果
公告， ：
"这个未经审核的新闻组旨在讨论Web
样式表。样式表可以让作者的生活更轻松。
使用样式表，只需要指定一次演示前的
ference，并且可以应用样式整个网站。
不仅如此，当一个
文件包含所有样式信息时，样式表也会缩短下载时间。
02：===== Q& A =====
问：这个新闻组可以接受哪些帖子？
答：这个新闻组是一个样式表技术讨论论坛
以及适用于WWW的用法。
此新闻组的有效主题示例包括：
*如何使用样式表实现特定效果。
*不同样式表语言的相对优势。
*规格与实现。
*实施中的漏洞和限制。
03：===== Q& A =====
问：这个新闻组可以接受哪些帖子？
答：关于WWW的相关文章主题（例如（X）HTML标记，客户端或
服务器端脚本语言等）
完整讨论特定样式表可能需要问题。
一般来说：
*关于（X）HTML标记的文章应发布到
< comp.infosystems.www.authoring.html>
*有关XML标记的文章应发布到< comp.text.xml>
<关于DSSSL的文章可能会发布到< comp.text.sgml>但最好的
正确论坛可能是DSSSL邮件列表
< DS ****** @ lists.mulberrytech.com>它有一个主要的WWW条目
< http://www.mulberrytech.com/dsssl/dssslist/>
*关于Java的文章编程语言应该在< comp.lang.java。*>中发布到
合适的NG。层次结构。
*客户端脚本语言的文章Javascript和
Jscript应发布到< comp.lang.javascript>
*其他类型的客户端或服务器端的文章，脚本
和/或编程语言应该发布到新闻组
或最适合特定语言的邮件列表。
在< http：//www.google.com>帮助找到对于
< comp.infosystems.www.authoring.stylesheets>
直接偏离主题的文章的
正确的论坛
04：===== Q& A =====
问：这个新闻组中哪些帖子不被接受？
答：一些不合适的例子帖子包括：
*连锁信，包括快钱赚钱文章。
*已知恶作剧（如Good Times Virus）。
*不相关网页和服务的公告。
*个人介绍或电子邮件请求。
*关于主题文章，问题或回复。
*测试文章。
*文章交叉发布到几个新闻组，其中文章
是交叉
帖子列表中一个或多个新闻组的主题。
*文章作为单独的副本发布到许多组（垃圾邮件）。
*引用比新内容更多的文章。
*提供项目的文章销售和商业广告。
*文章主要不是标准字母中的文字
（例如二进制文件，图片，Rot13等）。
互联网工程任务组（IETF）就如何在''RFC1855'< http：//www.ietf.org/rfc中发布使用网络提供建议b / b
/rfc1855.txt>.
每当你发布到usenet时，请遵循这些建议，你的
文章不仅应该在''ciwas'中得到好评，而且还要在
其他任何其他文章中得到好评。您可能想访问的新闻组。
05：===== Q& A =====
问：这个新闻组的技术资源在哪里？
答：关于这个主题的可用信息样式表太宽泛了 -
sive可直接写入已发布的文档，如这个元 -
常见问题解答。建议您在
WWW上研究您的技术问题
在以下一个或多个地方使用样式表。
*来自万维网联盟的样式表信息
（也称为W3C）起始于< http://www.w3.org/Style/CSS/>
并继续在< http：//www.w3.org/Style/XSL/>
- 层叠样式表级别的官方推荐1
（又名CSS1）< http：//www.w3.org/TR/CSS1>
- 级联样式表级别的官方推荐2
（又名CSS2）< http：//www.w3.org/TR/CSS2/>
- 级联的官方勘误文件样式表2级
（不再维护，有利于当前正在进行的CSS2.1规范上的b $ b工作）
< http://www.w3.org/Style/css2-updates/REC-CSS2-19980512-errata.html>
- 官方候选人获得级联风格的建议
表格级别2.1（目前是正在进行的工作
文件）< http://www.w3.org/TR / CSS21 />
- XSL转换（XSLT）的官方建议
版本1.0< http：//www.w3.org/TR / xslt>
- XML路径语言（XPath）的官方建议
版本1.0< http：//www.w3.org/TR/ xpath>
- 可扩展样式表语言的官方建议
（XSL / XSL-FO）版本1.0< http：//www.w3.org / TR / xsl />
*有关其他样式表语言的信息，文件
转换方法和规范。
- 文档样式语义和规范语言（DSSSL）
< http://www.mulberrytech.com/dsssl/dssslist/>
- 格式化输出规范实例（FOSI）
< http://xml.coverpages.org/gov-apps.html ＃mil2167a>
- 交互式电子技术手册（IETM）
< http://www.ietm.net/>
< http://navycals.dt.navy.mil/cals/documents/sp87269A.pdf>
- 国际无障碍文件设计委员会（ICADD）
< http://xml.coverpages.org/ICADDiso.html>
< http://xml.coverpages.org/ICADDpur.html>
应该注意的是HTML2 DTD被设计为ICADD
兼容< http：//www.ietf.org/rfc/rfc1866.txt>
* CSS的语法检查程序可从此处在线获取
< http://www.htmlhelp.org/tools/csscheck/> （主要是CSS1）
< http://jigsaw.w3.org/css-validator/>
*真正的HTML语法验证器可在线获取从这里
< http：//www.htmlhelp.org/tools/validator/>
< http://valet.webthing.com/page/ >
< http://validator.w3.org/>
* James Clark的'nsgmls的商业Windows前端''SGML
解析器/验证器可从这里获得
< http://arealvalidator.com/>
*需要一个好的，多用途的（X）HTML - CSS，WIN
环境的编辑器？转到< http：//www.notetab.com/>。它有一个
全尺寸商业版本以及略微缩小版本的b $ b免费版本，但其实际价值在于大量的免费版本/>
加载项" clips"可用。基于真实DTD的验证
你的标记只是你不需要的模块之一
额外付费才能触手可及。
* W3C有一个CSS测试套件，设计测试的工作
套件最初是由Eric A. Meyer完成的，但今天它是主要的 -
$ b由Bert Bos提供。
< http://www.w3.org/Style/CSS/Test/>
* Eric迈耶的复杂螺旋演示成为一个典型的例子
同时发布。 Eric显示了
CSS1的全部容量（再加上一些非常基本的，来自CSS2的内容）
< http://www.meyerweb。 com / eric / css / edge / complexspiral / demo.html>
* Todd Fahrner曾经设计过一套核心样式表，这些样式表是放在W3C上的
服务器系统。 Todd在ciwas的讨论中找到了其他（或许更有价值的）生活中的兴趣，而参与了
，但他最初的出色工作是
仍然可用，现在由Bert Bos维护。
< http：//www.w3.org/StyleSheets/Core/>
*网页设计小组在这里有CSS参考
< http://www.htmlhelp.com/reference/css/>
*此新闻组的创作常见问题解答位于
< http://css.nu/faq/ciwas-aFAQ.html>
* HTML作家协会CSS常见问题解答，最初由Eva von制作
Pepel几年前。仍然声称由Eva维护
但是相当长一段时间没有更新
< http://www.hwg.org/resources/faqs/cssFAQ。 html>
*为了节省一些时间用于Google评估，我们在这里列出了从两个第一页结果页面中获取的
CSS教育网站通过简单搜索键CSS从Google获得
。大多数这些网站
时不时被ciwas中的常客推荐。
< http://www.w3schools。 com / css / default.asp>
< http://www.csszengarden.com/>
< http://glish.com/css/ >
< http://www.meyerweb.com/eric/css/edge/>
< http://css.nu/>
< http://css.maxdesign.com.au/>
< http://www.blooberry.com/indexdot/css/>
< http://www.westciv.com/style_master/house/index.html>
< http://www.alistapart.com/topics/ css />
06：===== Q& A =====
问：如何最好地回复我的文章？
答：首先，请搜索这个最近讨论你的新闻组
问题[a]。
接下来，确保你的（X）HTML标记有效并且你的CSS是
正确形成;请参阅Q& A＃5以获取（X）HTML验证器的链接和
CSS核查资源。
如果问题仍然存在，请将您的代码减少到最低限度，
仍然显示问题，并将其上传到www服务器。
发布时，表明你觉得错误，你想要什么
已经发生了，包括你准备好的测试用例的URL
。
这个过程经常在你甚至没有之前揭示问题询问，
它为真正有用的常客提供了时间和精力
想要帮助你。
[ a]< http://groups.google.com/groups？group = comp.infosystems.www.authoring.styles heets>
是搜索ciwas之前讨论的有效工具。 />
07：===== Q& A =====
问：ciwas的气氛是什么？
A：嗯，严格 ;也许是一个简短的定义，你自然会在这里找到''OT''讨论，以及你可以在
其他NG'中找到它们。自从''ciwas''创建以来的这些年来，
基本上三件物品对于任何想要发表评论文章的人来说都是必不可少的。 ''ciwas''。
a）以自然的对话顺序发表您的评论，或者低于
所引用的材料或与其一致;不要顶部帖子。
b）包括引用的材料（带有属性），但将其修剪为
要点。
c）您通常应该只将文章发布到一个新闻组。
当且仅当您的文章主题涵盖多个时才
新闻组，你应该交叉发表文章。
不要将具有相同信息的单独文章发布到不同的
新闻组。
如果看似简单的文章/评论/问题，请不要感到不安
会触发与您的
输入相关的其他问题上的长篇帖子。毕竟，usenet最初是一个讨论论坛，而不是一个
帮助台。所有可以从讨论中获得的帮助
应被视为附带福利。
一个ciwas usenaut同意让他的NG的观点是从这个mFAQ引用的< http://www.css.nu/faq/ciwas-NG.html>
08：== === Q& A =====
问：我在哪里可以找到此常见问题的最新版本？
答：此常见问题解答已上次更新2004-07-22 copyright 1998 ... 2004
- Jan Roland Eriksson -
以电子方式自由复制本文件的许可是
只要文件保持未切割且未经编辑，就会给出
。
此常见问题定期发布给NG每周一次，我会
努力在任何时候都使用相同的主题行，以便那些看过它的人可以杀死文件。
常见问题解答版本号只要修改了
文件，主题行中的内容就会被更改。你应该能够在设置你的杀戮过滤器时使用这个事实
，以确保你始终可以使用
最新版本。
这个meta-FAQ也可以在万维网上的HTML中找到
< http://css.nu/faq/ciwas-mFAQ.html>并作为文本文件在
< http://css.nu/faq/ciwas-mFAQ.txt>修订历史记录
此元数据常见问题解答位于< http://css.nu/faq/ciwas-mFAQ-rev.html>
09：== ===结束=====
__________________________________________________ ____________________
-
雷克斯
I have worked some more on this suggested new mFAQ version trying to get
all user input to blend into the text.
Another review by the NG would be welcome.
=====
Archive-name: www/stylesheets/newsgroup-faq
Posting-Frequency: once a week
Last-modified: July 22, 2004
Version: 2.00
URL: <http://css.nu/faq/ciwas-mFAQ.html>
Maintainer: Jan Roland Eriksson <re*@css.nu>
comp.infosystems.www.authoring.stylesheets meta-FAQ v2.00
__________________________________________________ ____________________
00: ===== T O C =====
01: What is <comp.infosystems.www.authoring.stylesheets> ?
02: What kinds of posts are acceptable in this news group ?
03: What kinds of posts may be acceptable in this news group ?
04: What kinds of posts are not acceptable in this news group ?
05: Where are the technical resources for this news group ?
06: How do I get best possible response to my articles ?
07: What is the atmosphere of ''ciwas'' ?
08: Where can I find the latest version of this FAQ ?
09: ==== End ====
__________________________________________________ ____________________
01: ===== Q & A =====
Q: What is <comp.infosystems.www.authoring.stylesheets>
A: This is an unmoderated news group which passed for creation by
votes of 166:19 as reported in <news.announce.newgroups> on
1997-03-20.
The charter of this news group, taken from the vote result
announcement, is:
"This unmoderated news group is intended for the discussion of Web
style sheets. Style sheets can make an author''s life much easier.
With style sheets, one only needs to specify presentational pre-
ferences once, and the style can be applied to an entire site.
Not only that, but style sheets also reduce download time when one
file contains all the style information."
02: ===== Q & A =====
Q: What kinds of posts are acceptable in this news group ?
A: This news group is a forum for discussion of style sheet technology
and usage that is applicable to the WWW.
Examples of valid topics for this news group include:
* How to achieve a particular effect with style sheets.
* The relative advantages of different style sheet languages.
* Specifications versus implementations.
* Bugs and limitations in implementations.
03: ===== Q & A =====
Q: What kinds of posts may be acceptable in this news group ?
A: Articles on related WWW subjects (e.g. (X)HTML mark-up, client or
server side scripting languages, etc.) that may be required for a
full discussion of a specific style sheet problem.
In general terms:
* articles on (X)HTML mark-up should be posted to
<comp.infosystems.www.authoring.html>
* articles on XML mark-up should be posted to <comp.text.xml>
* articles on DSSSL may be posted to <comp.text.sgml> but the most
correct forum might be the DSSSL mailing list at
<DS******@lists.mulberrytech.com> which has a main WWW entry at
<http://www.mulberrytech.com/dsssl/dssslist/>
* articles on the Java programming language should be posted to a
suitable NG in the <comp.lang.java.*> hierarchy.
* articles on the client side scripting languages Javascript and
Jscript should be posted to <comp.lang.javascript>
* articles on other types of client side, or server side, scripting
and/or programming languages should be posted to the news group
or mailing list most appropriate to the particular language.
A search at <http://www.google.com> may be of help to find the
correct forum for articles that are directly off-topic for
<comp.infosystems.www.authoring.stylesheets>
04: ===== Q & A =====
Q: What kind of posts are not acceptable in this news group ?
A: Some examples of inappropriate posts include:
* Chain letters, including "Make Money Fast" articles.
* Known hoaxes (like the "Good Times Virus").
* Announcements of non-relevant Web pages and services.
* Personal introductions or requests for e-mail.
* Off topic articles, questions or responses.
* Test articles.
* Articles cross-posted to several news groups where the article
is off-topic for one or more of the news groups in the cross-
post list.
* Articles posted as separate copies to many groups ("spam").
* Articles with significantly more quoted than new content.
* Articles offering items for sale and commercial advertisements.
* Articles which aren''t primarily text in a standard alphabet
(e.g. binaries, pictures, Rot13, etc).
The Internet Engineering Task Force (IETF) gives advice on how to
post to usenet in ''RFC1855'' <http://www.ietf.org/rfc/rfc1855.txt>.
Follow those recommendations whenever you post to usenet and your
articles should be well received not only in ''ciwas'' but also in
any other news group you may want to visit.
05: ===== Q & A =====
Q: Where are the technical resources for this news group ?
A: Available information on the subject of style sheets is too exten-
sive to be directly written into a posted document like this meta-
FAQ. It is suggested that you research your technical questions on
the use of style sheets in one or more of the following places on
the WWW.
* Style sheet information from the World Wide Web Consortium
(also known as the W3C) starts at <http://www.w3.org/Style/CSS/>
and continues at <http://www.w3.org/Style/XSL/>
- The official recommendation for Cascading Style Sheets level 1
(aka CSS1) <http://www.w3.org/TR/CSS1>
- The official recommendation for Cascading Style Sheets level 2
(aka CSS2) <http://www.w3.org/TR/CSS2/>
- The official errata document for Cascading Style Sheets level 2
(which is no longer maintained, in favor of the current ongoing
work on the CSS2.1 specification)
<http://www.w3.org/Style/css2-updates/REC-CSS2-19980512-errata.html>
- The official Candidate recommendation for Cascading Style
Sheets level 2.1 (which is currently a "work in progress"
document) <http://www.w3.org/TR/CSS21/>
- The official recommendation for XSL Transformations (XSLT)
Version 1.0 <http://www.w3.org/TR/xslt>
- The official recommendation for XML Path Language (XPath)
Version 1.0 <http://www.w3.org/TR/xpath>
- The official recommendation for Extensible Stylesheet Language
(XSL/XSL-FO) Version 1.0 <http://www.w3.org/TR/xsl/>
* Information on other style sheet capable languages, document
transformation methods and specifications.
- Document Style Semantics and Specification Language (DSSSL)
<http://www.mulberrytech.com/dsssl/dssslist/>
- Formatting Output Specification Instance (FOSI)
<http://xml.coverpages.org/gov-apps.html#mil2167a>
- Interactive Electronic Technical Manuals (IETM)
<http://www.ietm.net/>
<http://navycals.dt.navy.mil/cals/documents/sp87269A.pdf>
- International Committee for Accessible Document Design (ICADD)
<http://xml.coverpages.org/ICADDiso.html>
<http://xml.coverpages.org/ICADDpur.html>
It should be noted that the HTML2 DTD was designed to be ICADD
compatible <http://www.ietf.org/rfc/rfc1866.txt>
* Syntax checkers for CSS are available online from here
<http://www.htmlhelp.org/tools/csscheck/> (CSS1 primarily)
<http://jigsaw.w3.org/css-validator/>
* True HTML syntax validators are available online from here
<http://www.htmlhelp.org/tools/validator/>
<http://valet.webthing.com/page/>
<http://validator.w3.org/>
* A commercial Windows front for James Clark''s ''nsgmls'' SGML
parser/validator is available from here
<http://arealvalidator.com/>
* In need of a good, all purpose (X)HTML - CSS, editor for the WIN
environment? Go to <http://www.notetab.com/>. It''s available in a
full sized commercial version as well as a slightly scaled down
free version, but its real value lies in the vast amount of free
add-in "clips" available for it. True DTD based validation of
your markup is just one of the modules that you do not have to
pay extra to have at your fingertips.
* W3C has a CSS test suite available, the work to design that test
suite was originally done by Eric A. Meyer but today it''s main-
tained by Bert Bos.
<http://www.w3.org/Style/CSS/Test/>
* Eric Meyer''s "Complex Spiral Demo" became a "classic example" at
the same time it was published. Eric shows the full capacity of
CSS1 (combined with a few, very basic, pick up''s from CSS2)
<http://www.meyerweb.com/eric/css/edge/complexspiral/demo.html>
* Todd Fahrner once designed a set of core stylesheets that was
placed on the W3C server system. Todd has found other (maybe
more valuable) interests in life as compared to participating
in discussions in ''ciwas'' but his original excellent work is
still available, now maintained by Bert Bos.
<http://www.w3.org/StyleSheets/Core/>
* The Web Design Group has a CSS reference here
<http://www.htmlhelp.com/reference/css/>
* The authoring FAQ for this news group is at
<http://css.nu/faq/ciwas-aFAQ.html>
* The HTML Writers Guild CSS FAQ, originally produced by Eva von
Pepel a few years back. Still claimed to be maintained by Eva
but has not been updated for quite some time
<http://www.hwg.org/resources/faqs/cssFAQ.html>
* To save some time on Google evaluations we have here a list of
CSS educational sites as taken from the two first result pages
from Google on the simple search key ''CSS''. Most of these sites
gets recommended every now and then by regulars here in ''ciwas''.
<http://www.w3schools.com/css/default.asp>
<http://www.csszengarden.com/>
<http://glish.com/css/>
<http://www.meyerweb.com/eric/css/edge/>
<http://css.nu/>
<http://css.maxdesign.com.au/>
<http://www.blooberry.com/indexdot/css/>
<http://www.westciv.com/style_master/house/index.html>
<http://www.alistapart.com/topics/css/>
06: ===== Q & A =====
Q: How do I get best possible response to my articles ?
A: First, please search this newsgroup for recent discussion of your
issue(s) [a].
Next, make sure your (X)HTML markup is valid and that your CSS is
correctly formed; see Q&A #5 for links to (X)HTML validators and
CSS checkup resources.
If the problem remains, get your code pared down to a bare minimum,
which still shows the problem, and upload it to a www server.
When posting, indicate what you feel is wrong, what you''d like to
have happen instead, and include the URL to the test case you''ve
just prepared.
This process often reveals the problem before you even have to ask,
and it saves time and effort for the helpful regulars who really do
want to assist you.
[a]<http://groups.google.com/groups?group=comp.infosystems.www.authoring.styles heets>
is an effective tool to search previous discussions in ciwas.
07: ===== Q & A =====
Q: What is the atmosphere of ''ciwas'' ?
A: Well, "strict" maybe a short definition, and naturally you will
find ''OT'' discussions here just as well as you can find them in
other NG''s. Still, over the years since the creation of ''ciwas'',
basically three items has come to be essential for any one who
wants to place a commentary article in ''ciwas''.
a) Make your comment in a natural conversation order, either below
the quoted material or in-line with it; Do not "top-post".
b) Include quoted material (with attribution) but trim it to the
essentials.
c) You should normally post an article to one news group only.
If, and only if, the topic of your article covers more than one
news group, you should cross-post the article.
Do not post separate articles with the same message to different
news groups.
Don''t be upset if a seemingly simple article/comment/question
triggers a long thread of posts on other issues related to your
input. After all usenet is a forum for discussions at first, not a
"help desk". All eventual help that can be had from a discussion
shall be looked upon as a "fringe benefit".
One ciwas usenaut has agreed to let his views of the NG be
referenced from this mFAQ at <http://www.css.nu/faq/ciwas-NG.html>
08: ===== Q & A =====
Q: Where can I find the latest version of this FAQ ?
A: This FAQ was last updated 2004-07-22 copyright 1998 ... 2004
-- Jan Roland Eriksson --
Permission to freely reproduce this document electronically is
given as long as the document remains uncut and unedited.
This FAQ is posted periodically to the NG once a week and I''ll
endeavor to use the same subject line at all times so that those
of you who have seen it can kill-file the subject.
FAQ version number in subject line will be changed whenever the
document has been revised. You should be able to use that fact
when setting your kill filter to make sure that you have the
latest version available at all times.
This meta-FAQ is also available in HTML on the World Wide Web at
<http://css.nu/faq/ciwas-mFAQ.html> and as a text document at
<http://css.nu/faq/ciwas-mFAQ.txt> with the revision history of
this meta-FAQ at <http://css.nu/faq/ciwas-mFAQ-rev.html>
09: ===== E N D =====
__________________________________________________ ____________________
--
Rex
推荐答案
JRS：文章< ln ****************************** **@4ax.com> ;,日期
星期四，2004年7月22日01:31:31，见于新闻：comp.infosystems。 www.authoring.s
tylesheets，Jan Roland Eriksson< re*@css.nu>发表：
JRS: In article <ln********************************@4ax.com>, dated
Thu, 22 Jul 2004 01:31:31, seen in news:comp.infosystems.www.authoring.s
tylesheets, Jan Roland Eriksson <re*@css.nu> posted :
我已经对这个建议的新mFAQ版本进行了更多工作，试图将所有用户输入混合到文本中。
NG的另一篇评论会受到欢迎。
*客户端脚本语言的文章Javascript和
Jscript应该发布到< comp.lang.javascript>
c.l.j中的默认假设是Internet客户端网页;但是
服务器端javascript和（恕我直言）WS32中Win32 + * .js文件执行
是完全可以接受的。建议：只省略客户端
（连字符首选）。
Jscript正确是新闻主题：microsoft.public.scripting.jscript
（和* .vbscript& * .wsh也存在）。
*文章作为单独的副本发布到许多组（垃圾邮件）。
是的，但恕我直言没用，因为垃圾邮件发送者不会阅读常见问题解答。回复
垃圾邮件是值得弃用的。
*文章多个帖子作为单独的副本发布到不同的组。
互联网工程任务组（IETF）就如何在''RFC1855'< http://www.ietf.org/rfc/rfc1855.txt>中提供有关如何发布到usenet的建议。
每当您发布到usenet时，请遵循这些建议，并且您的
文章不仅应该在ciwas中得到好评，而且还应该在您可能想要访问的任何其他新闻组中得到好评。
FYI，AIUI，
http://www.ietf.org/internet-drafts/...article-13.txt
http://www.ietf.org/internet-drafts/ ...- useage-00.txt
将取代它和Son-of-RFC1036，完成后。
答：此常见问题解答最后更新时间2004-07-22
...
I have worked some more on this suggested new mFAQ version trying to get
all user input to blend into the text.
Another review by the NG would be welcome.
* articles on the client side scripting languages Javascript and
Jscript should be posted to <comp.lang.javascript>
The default assumption in c.l.j is Internet client-side Web pages; but
server-side javascript and (IMHO) the execution in Win32+ of *.js files
by WSH are quite acceptable. Suggestion : just omit "client side"
(hyphenated preferred).
Jscript proper is the topic of news:microsoft.public.scripting.jscript
(and *.vbscript & *.wsh also exist).
* Articles posted as separate copies to many groups ("spam").
True, but IMHO not useful, as spammers don''t read FAQs. Responses to
spam are deprecate-worthy.
* Articles multi-posted as separate copies to different groups.
The Internet Engineering Task Force (IETF) gives advice on how to
post to usenet in ''RFC1855'' <http://www.ietf.org/rfc/rfc1855.txt>.
Follow those recommendations whenever you post to usenet and your
articles should be well received not only in ''ciwas'' but also in
any other news group you may want to visit.
FYI, AIUI, one of
http://www.ietf.org/internet-drafts/...article-13.txt
http://www.ietf.org/internet-drafts/...-useage-00.txt
will supersede that and Son-of-RFC1036, when finished.
A: This FAQ was last updated 2004-07-22
...
现在是一个创作问题：对于网页，*正好*，直到
文件中的字节级别，如果ISO-8601数字分隔日期是
构造的？直到今天早些时候，我以为我知道了。
-
？约翰斯托克顿，英国萨里。 ?@merlyn.demon.co.uk Turnpike v4.00 MIME。 ？
Web< URL：http：//www.merlyn.demon.co.uk/> - w。常见问题主题，链接，首字母缩略词
PAS EXE等：< URL：http：//www.merlyn.demon.co.uk/programs/> - 见00index.htm
日期 - miscdate.htm moredate.htm js-dates.htm pas-time.htm critdate.htm等
And now an authoring question : for Web pages, *exactly*, down to the
level of bytes in the file, should an ISO-8601 numeric separated date be
constructed? Until earlier today, I thought I knew.
--
? John Stockton, Surrey, UK. ?@merlyn.demon.co.uk Turnpike v4.00 MIME. ?
Web <URL:http://www.merlyn.demon.co.uk/> - w. FAQish topics, links, acronyms
PAS EXE etc : <URL:http://www.merlyn.demon.co.uk/programs/> - see 00index.htm
Dates - miscdate.htm moredate.htm js-dates.htm pas-time.htm critdate.htm etc.
2004年7月22日星期四18:39:12 +0100，John Stockton博士
< sp ** @ merlyn.demon.co.uk>写道：
On Thu, 22 Jul 2004 18:39:12 +0100, Dr John Stockton
<sp**@merlyn.demon.co.uk> wrote:
JRS：在文章< ln ***************************** ***@4ax.com> ;,
发表于2004年7月22日星期四01:31:31，见于
新闻：comp.infosystems。 www.authoring.stylesheets ，
Jan Roland Eriksson< re*@css.nu>发布：
[...]
JRS: In article <ln********************************@4ax.com>,
dated Thu, 22 Jul 2004 01:31:31, seen in
news:comp.infosystems.www.authoring.stylesheets,
Jan Roland Eriksson <re*@css.nu> posted :
[...]
NG的另一项评论将受到欢迎。
*关于客户端脚本语言的文章Javascript和
Jscript应该发布到< comp.lang.javascript>
Another review by the NG would be welcome. * articles on the client side scripting languages Javascript and
Jscript should be posted to <comp.lang.javascript>
clj中的默认假设是Internet客户端网页;但是服务器端的javascript和（恕我直言）WSH的Win32 + * .js文件中的执行是完全可以接受的。建议：只省略客户端
（连字符首选）。
The default assumption in c.l.j is Internet client-side Web pages; but
server-side javascript and (IMHO) the execution in Win32+ of *.js files
by WSH are quite acceptable. Suggestion : just omit "client side"
(hyphenated preferred).
好的！我可以买，任何让文字更简单的东西都是可以接受的。
Jscript本身是新闻的主题：microsoft.public.scripting.jscript
（并且* .vbscript& * .wsh也存在）。
嗯;我不认为这个mFAQ的任务是''ciwas''尝试将b / b $ b转换为尽可能多的其他NG'，所以我会这样做/>
喜欢在人们引用
传统的大8中可用的内容时画一条线。 NG'和''clj''属于那里，MS NG'不属于。
我不知道你是否注意到了，但是在过去的几个MS的年份
字面意思是垃圾邮件 Usenet与新组控制消息，我不认为这是鼓励使用其中任何一个的关键。
传统的替代方案存在并继续存在一种强烈的时尚。
Jim Ley是''clj''常见问题解答的维护者，恰好是一个优秀且非常负责任的Javasript / Jscript程序员。
几乎所有他的脚本创作，仅作为MSIE的一个例子，
适合任何想要使用
脚本语言的人的教材。但是吉姆在''clj''所以'我想要参考的地方
人，因为这个原因，为有需要的人提供良好的服务，以及
$ b事实上''clj''是大8的成员。层次结构。
Ok! I can buy that, anything that makes the text more simple is
acceptable.
Jscript proper is the topic of news:microsoft.public.scripting.jscript
(and *.vbscript & *.wsh also exist).
Well; I don''t see it as the task of this mFAQ for ''ciwas'' to try to
divert OT postings into as many other NG''s as ever possible, so I would
like to draw a line at referring people to what is available within the
traditional "big 8" NG''s, and ''clj'' belongs there, MS NG''s do not.
I don''t know if you have noticed, but over the last couple of years MS
has literally "spammed" Usenet with new-group control messages, I do not
think it''s a ciwas concern to encourage the use of any of them when
traditional alternatives exists and lives on in a strong fashion.
Further; Jim Ley, who is the maintainer of the ''clj'' FAQ, happens to be
an excellent and very responsible Javasript/Jscript programmer.
Just about all of his script creations, for MSIE only as one example,
lends themselves as teaching material for any one who wants to use a
script language. But Jim is in ''clj'' so that''s where I want to refer
people, for that very reason, for good service to those in need, and the
fact that ''clj'' is a member of the "big 8" hierarchy.
*文章作为单独的副本发布到许多组（垃圾邮件）。
是的，但是恕我直言，因为垃圾邮件发送者不会阅读常见问题解答。对垃圾邮件的回复是弃用的。
所以我会放弃该行的''（垃圾邮件）部分。我喜欢的另一个简化
。
*文章多个帖子作为单独的副本发布到不同的组。
[...]
FYI，AIUI，
之一 http://www.ietf.org/internet-drafts/...article-13.txt
http ：//www.ietf.org/internet-drafts/...-useage-00.txt
将取代它和Son-of-RFC1036，完成后。
当发生这种情况时修改mFAQ的时间:-)
答：此常见问题解答最后更新2004-07-22
* Articles posted as separate copies to many groups ("spam"). True, but IMHO not useful, as spammers don''t read FAQs. Responses to
spam are deprecate-worthy.
So I will drop the ''("spam")'' part of that line. Another simplification
that I like.
* Articles multi-posted as separate copies to different groups.
[...]
FYI, AIUI, one of
http://www.ietf.org/internet-drafts/...article-13.txt
http://www.ietf.org/internet-drafts/...-useage-00.txt
will supersede that and Son-of-RFC1036, when finished.
Time to revise the mFAQ when that happens then :-)
A: This FAQ was last updated 2004-07-22
现在是一个创作问题：对于网页，*正好*，低至文件中的字节级别，如果ISO-8601数字分隔日期为
构建？直到今天早些时候，我以为我知道了。
And now an authoring question : for Web pages, *exactly*, down to the
level of bytes in the file, should an ISO-8601 numeric separated date be
constructed? Until earlier today, I thought I knew.
我不确定我是否真的理解你问题的真正支柱
首先，我将以个人观点开始。
对我来说，如上所述，写的日期是只是另一串文字
原来。如果出于某些特定原因需要解析那个
文本字符串，我相信那个人可以使用适当的软件工具，或者能够写自己的
。
作为附注;我确实有我的银行网络连接，我做了一些
99％以上的银行业务超过''网络'。
我有，作为一个实验，当我指定账单的支付日期时，试图使用几种不同的日期格式
。到目前为止，我发现我的
银行的服务器barf在违反重要性的日期。
典型的向后美国式的方式用于指定
重要性顺序的方式。如在月 - 日 - 年中是否禁止。
任何其他组合似乎都是好的，甚至命名日期的部分，如
" 25 juli 2004" （月份的名称是瑞典语）被接受。
所以，如果我在你的鞋子里，我会继续处理更重要的事情和
留下它用户可以解释你在网页上写的内容。
感谢您提供的输入方式，我们似乎正在接近一块
mFAQ文本，我可以继续发布归档。
一切顺利...
-
Rex
I''m not sure that I do understand the real backbone of your question at
first so I will give my personal view to start with.
To me a date written, as above, is "just another string of text"
initially. Should there be any one out there that needs to parse that
text string for some specific reason, I would trust that person to have
available the proper software tools to do so, or to be capable of
writing his own.
As a side note; I do have Internet connection to my bank and I do some
99%+ of my banking business over ''the net''.
I have, as an experiment, tried to use several different date formats
when I specify a pay date for my bills. So far I have found that my
bank''s server barfs at dates where order of significance is violated.
The typical "backwards" US-American way of specifying things out of
"order of significance" as in "month-day-year" is a no-no.
Any other combination seems to be Ok, even named parts of dates as in
"25 juli 2004" (name of month is in Swedish) is accepted.
So if I was in your shoes, I would move on to more important matters and
leave it to users to interpret what you have written in your web pages.
Thanks for the input by the way, it seems we are closing in on a piece
of mFAQ text that I can move on to post for archive.
All the best...
--
Rex
JRS：文章< t8 ************************ ********@4ax.com> ;,日期
周五，2004年7月23日01:30:50，见于新闻：comp.infosystems。 www.authoring.s
tylesheets，Jan Roland Eriksson< re*@css.nu>发表：
JRS: In article <t8********************************@4ax.com>, dated
Fri, 23 Jul 2004 01:30:50, seen in news:comp.infosystems.www.authoring.s
tylesheets, Jan Roland Eriksson <re*@css.nu> posted :
2004年7月22日星期四18:39:12 +0100，John Stockton博士
< sp ** @ merlyn.demon.co.uk>写道：
On Thu, 22 Jul 2004 18:39:12 +0100, Dr John Stockton
<sp**@merlyn.demon.co.uk> wrote:
JRS：在文章< ln ***************************** ***@4ax.com> ;,
发表于2004年7月22日星期四01:31:31，见于
新闻：comp.infosystems。 www.authoring.stylesheets ，
Jan Roland Eriksson< re*@css.nu>发表：
[...]
JRS: In article <ln********************************@4ax.com>,
dated Thu, 22 Jul 2004 01:31:31, seen in
news:comp.infosystems.www.authoring.stylesheets,
Jan Roland Eriksson <re*@css.nu> posted :
[...]
NG的另一项评论将受到欢迎。
其他; Jim Ley是clj常见问题解答的维护者，
目前，他提供了保护和托管; Richard Cornford对常见问题解答和备注进行了编辑。
答：此常见问题解答最后更新2004-07-22
Another review by the NG would be welcome. Further; Jim Ley, who is the maintainer of the ''clj'' FAQ,
Currently, he provides the aegis and the hosting; Richard Cornford does
the editing of FAQ and notes.
A: This FAQ was last updated 2004-07-22
现在是一个创作问题：对于网页，*正好*，低至文件中的字节级别，如果ISO-8601数字分隔日期为<建造？直到今天早些时候，我以为我知道了。
And now an authoring question : for Web pages, *exactly*, down to the
level of bytes in the file, should an ISO-8601 numeric separated date be
constructed? Until earlier today, I thought I knew.
我不确定我是否确实理解了你问题的真正支柱，所以我会给出我个人观点开始。
...
I''m not sure that I do understand the real backbone of your question at
first so I will give my personal view to start with.
...
我一直使用YYYY-MM-DD，其中 - 字符使用 - 键并且是
编码为值为45的字节。
但是，在发现了样式p {text-align：justify}后，我试了一下
只发现YYYY-MM-DD经常有一个视觉外观，而不是类似于YYYY-MM-DD的b $ b（我已经知道日期可能会显示为YYYY-
MM-DD）真的很难看。
因此，IE4中的设计或错误都是不好的;或者应该使用其他一些
字符？ &安培; ndash的;表现相似。
< nobr>防止封闭线被破坏;但是允许它延伸到
。
CSS能提供答案吗？ CSS1？
Word 97会破坏这样的日期;但是没有伸展它。
我从来没有考虑过ISO-8601可能会要求一个角色，而不是众所周知的b $ b - "用于编程为减号。
作为旁注;我的银行有互联网连接，而且我做了99％以上的银行业务而不是网络。
我作为一个实验试图使用几个不同的日期格式
当我指定账单的支付日期时。到目前为止，我发现我的
银行的服务器barf在违反重要性的日期。
典型的向后美国式的方式用于指明重要性的顺序之外的东西。如在月 - 日 - 年中是一个禁忌。
I''ve always used YYYY-MM-DD where the - characters use the - key and are
encoded as a byte of value 45.
But, having discovered style p { text-align: justify } , I tried it
only to find that YYYY-MM-DD then often had a visual appearance rather
resembling YYYY- MM- DD (I already knew that dates might appear as YYYY-
MM-DD) which is really ugly.
So is that just bad design, or a bug, in IE4; or should some other
character be used? – behaves similarly.
<nobr> prevents the enclosed being line-broken; but allows it to be
stretched.
Does CSS provide an answer? CSS1?
Word 97 will line-break such a date; but does not stretch it.
I''ve never considered that ISO-8601 might call for a character other
than the well-known "-" as used in programming for "minus".
As a side note; I do have Internet connection to my bank and I do some
99%+ of my banking business over ''the net''.
I have, as an experiment, tried to use several different date formats
when I specify a pay date for my bills. So far I have found that my
bank''s server barfs at dates where order of significance is violated.
The typical "backwards" US-American way of specifying things out of
"order of significance" as in "month-day-year" is a no-no.
虽然你的电子邮件地址是纽埃（通过新西兰，你可以把你带到英国）
联邦< ; g>），你的TZ是-0200，这表明欧盟。显然欧盟
和其他非NA组织需要拒绝美国格式化的数字
日期，除非是每月一天。
我的银行经常在YYYY-MM-DD看两次，但是没有异议就接受了。
-
？约翰斯托克顿，英国萨里。 ?@merlyn.demon.co.uk Turnpike v4.00 MIME。 ？
Web< URL：http：//www.merlyn.demon.co.uk/> - w。常见问题主题，链接，首字母缩略词
PAS EXE等：< URL：http：//www.merlyn.demon.co.uk/programs/> - 见00index.htm
日期 - miscdate.htm moredate.htm js-dates.htm pas-time.htm critdate.htm等
Although your E-address is Niue (which, via NZ, puts you in the British
Commonwealth <g>), your TZ is -0200, which suggests EU. Obviously EU
and other non-NA organisations need to reject US formatted numeric
dates, except on one day per month.
My bank often looks twice at YYYY-MM-DD, but accepts it without demur.
--
? John Stockton, Surrey, UK. ?@merlyn.demon.co.uk Turnpike v4.00 MIME. ?
Web <URL:http://www.merlyn.demon.co.uk/> - w. FAQish topics, links, acronyms
PAS EXE etc : <URL:http://www.merlyn.demon.co.uk/programs/> - see 00index.htm
Dates - miscdate.htm moredate.htm js-dates.htm pas-time.htm critdate.htm etc.
这篇关于ciwas mFAQ的第三个测试帖的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
