Friday, 8 September 2006
|
| Number, Date, Time, Quantity Alan Hendry 19:03:43 |
| |
If there was a tag like <number>1,234.56</number>
it could be displayed as 1.234,56 based upon the users settings
(regional options in Windows)
further it could be read as "one thousand two hundred ..." by a screen
reader
If there was a tag like <shortdate>31/12/2006</shortdate>
it could be displayed as 12-31-06 based on the users settings
If there was a tag like <longdate>31/12/2006</longdate>
it could be displayed as 31 December 2006 based on the users settings
(and language)
If there was a tag like <time>23:59:59</time>
it could be displayed as 11.59.59 PM
If there was a tag like <quantity unit=km>1.6</quantity>
then it could be displayed as 1 MILE
(there could be a lot of different units for length, area, volume,
weight, temperature, etc)
*********************************************************************************
This email is intended solely for the use of the individual to whom
it is addressed and may contain confidential and/or privileged
material. Any views or opinions presented are solely those of the
author and do not necessarily represent those of AGCO.
If you are not the intended recipient, be advised that you have
received this email in error and that any use, dissemination,
forwarding, printing or copying of this email is strictly prohibited.
Neither AGCO nor the sender accepts any responsibility for viruses and it
is your
responsibility to scan and virus check the e-mail and its attachment(s)
(if any).
*********************************************************************************
|
| |  20 answers | Add comment |
|
| Metadata (was: Re: Number, Date, Time, Quantity) Anne van Kesteren 14:56:27 |
| |
On Fri, 08 Sep 2006 09:48:43 +0200, Henri Sivonen <hsivonen@iki.fi> wrote:> Also, it seems to me that the core competence and point of > differentiation of successful search engines is yielding useful results > even in the absence of such explicit metadata.
The other problem is of course that metadata can be incorrect and if
enough people add incorrect metadata it will be ignored again (happened
before to the <meta> element for instance).
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
|
| | 5 answers | Add comment |
Friday, 1 September 2006
|
| IBM Position Statement on XForms and Web Forms 2.0 John Boyer 16:04:41 |
| | Dear W3C Chairs and W3C AC Members,
The text below represents the IBM position statement on XForms and Web
Forms 2.0.
An advance copy of this document was reviewed favorably by Steve Bratt and
Chris Lilley, and I believe it is accurate to say that IBM offers this
position statement in the spirit described by Steve when he said, "I very
much hope that it will serve to open (not close) doors to much improved
cooperation from all parties to help us move forward. I think this is a
good start."
Based on further details provided by Steve and Chris on the rechartering
plans in progress, I am left feeling quite optimistic that the full team
of W3C working group members interested in this space will be able to
forge a path of collaboration and compromise that satisfies the most
urgent requirements of all the parties in a timely fashion.
Best regards,
John M. Boyer, Ph.D.
Senior Product Architect/Research Scientist
Co-Chair, W3C XForms Working Group
Workplace, Portal and Collaboration Software
IBM Victoria Software Lab
E-Mail: boyerj@ca.ibm.com http://www.ibm.com/software/
Blog: http://www.ibm.com/developerworks/blogs/page/JohnBoyer
===================================================================================
IBM is a strong supporter of the XForms recommendation and working group.
As well, IBM has looked positively upon Web Forms 2.0 (WF2) since its
member submission because the W3C team's acknowledgement strongly
encouraged the charter mandates of XForms and HTML be enhanced to allow
unification of WF2 features into XForms.
The current draft of WF2 suggests that we can appropriately meet users
needs with two different technologies: an XForms or similar system used
purely at the server to meet the needs of powerful applications and their
designers, and a different more HTML-oriented solution "on the wire". On
this point we respectfully disagree. It is true that authors of simple
documents and applications do indeed need a simple and convenient
solution, but it is equally important that the technologies used in more
powerful applications migrate seamlessly between client and server,
according to the needs of the application and the capabilities of the
client. So the choice is not whether we can have XForms at the server and
WF2 on the wire, but whether the "on the wire standard" can scale to meet
the needs of both simple and powerful applications. This is the reason
that we are pushing so strongly for unification.
The first working draft of Web Forms 2.0 contains many good features,
including XML Submissions, declarative repeating constructs, and strongly
typed input fields, and indeed, many of the features exist in the XForms
recommendation. From this we conclude that many of these features are of
use, not just at the server, but on the wire as well. IBM sees a
significant advantage for the future of the web to rationalize the WF2
proposal with the XForms recommendation in the places where there are
direct overlaps, while incorporating the WF2 features that are distinct,
and being attentive to the needs of users who seek truly simple solutions.
XForms and WF2 have very many features and use cases in common, so it
should be possible to unify the two with a common syntax. Most of the
current differences between XForms and WF2 appear to be along two
orthogonal axes:
1) Simple vs. Complex content: the extent to which new features of HTML
can be accessed as simply as possible to scale up the functionality of
content gradually.
IBM believes this is a strength of Web Forms 2.0 that needs to be better
incorporated into XForms. For example, the XForms input control could
accept the name attribute as a substitute for the ref attribute when
creating the implicit data model, and attributes such as type, readonly
and value placed directly on the input control can be used to implicitly
create the appropriate model item properties and default values. This
type of change basically recognizes the legitimacy of the Web Forms 2.0
requirements by importing the syntactic constructs directly with little or
no modification. Importantly, IBM understands that it is users (albeit in
various roles, and with various levels of expertise) who must be
reasonably satisfied with both the convenience and the power of whatever
solutions we adopt.
2) XML vs. non-XML content: the extent of belief in the premise that new
features in HTML should be defined via XML syntax rather than non-XML
syntax
While ease of browser implementation of new features is one important
concern, IBM believes that there are many important factors that
contribute not only to the total cost of ownership of web applications but
also to the ability to create and maintain a significantly broader
spectrum of current and future web technologies. IBM believes that these
factors are important enough that it is essential to use new features of
HTML as an enticement toward greater conformance of web content to XML
syntax, granting that effort will be required to achieve a result that is
also sufficiently convenient for various users.
Simultaneously, IBM believes that the requirement of XML conformance for
HTML that exercises new features does no real harm to legacy UAs, which
would provide graceful degradation based on HTML content that happens to
comply with XML syntax, and the requirement does no real harm to UAs
updated to respond to the new syntax since they can be updated to respond
to any new syntax. As for accommodating reduced functionality UAs, we
believe it is necessary to have a unified conceptual model from which a
more appropriate language profile can be created for reduced functionality
UAs. The profile should focus on the ease-of-use syntax and its ability
to imply a basic data model, and it should only delegate the more advanced
features of an explicit model to the server when a reduced functionality
UA is being served.
In conclusion, IBM strongly advocates for the renewed charter of the
XForms and HTML working groups to include unification of the Web Forms 2.0
work with emphases on the ease-of-use benefits from WF2 and the XML basis
from XForms. There will be compromises required of all parties, but also
significant synergies that become possible by accommodating the full range
of forms expertise available in the W3C.
===================================================================================
|
| | 2 answer | Add comment |
Thursday, 31 August 2006
|
| Design question about formats based on XHTML 2 Peter Krantz 01:30:31 |
| |
Hi!
In a project we are looking at XHTML 2 as the foundation for a
document format in the legal domain. XHTML 2 is a great starting point
as it is a generic document format covering most of our markup needs.
In our domain we would like to express that some section elements are
of a specific type. The type belongs to a namespace. The function of
the section element is the same but we would like to be able to
extract sections of this specific type.
What would be a good way to markup our sections? The role attribute
sounds like a candidate but looking at the XHTML2 specification it
does not feel right ("It is used by applications and assistive
technologies to determine the purpose of UI widgets."). Is the class
attribute the way to go?
Kind regards,
Peter
|
| | 11 answers | Add comment |
Wednesday, 30 August 2006
|
| Re: Screen readers and numbers (was RE: Number, Date, Time, Quantity) Philip TAYLOR 20:55:01 |
| |
John Foliot wrote:
Perhaps more work is required for the numeric rendering/speaking, perhaps > "whole-number" (where 1,012 would be expressed as "one thousand twelve")
Only in some dialects; in others (e.g., <Br.E>) this would be
"one thousand /and/ twelve".
Philip Taylor
|
| | Add comment |
Monday, 28 August 2006
|
| Mapping XML to XHTML - your recommendation for handling attributes? Roger L. Costello 13:22:11 |
| | Hi Folks,
I am mapping an XML document to XHTML.
Leaf nodes in the XML document I map to an XHTML <dl> element, e.g.,
<aircraft_elevation>12000</aircraft_elevation>
I map to:
<dl class="aircraft_elevation">
<dt>Aircraft Elevation</dt>
<dd>12000</dd>
</dl>
Now suppose <aircraft_elevation> has an attribute:
<aircraft_elevation units="meters">12000</aircraft_elevation>
How do you recommend I map the attribute?
/Roger
|
| | 7 answers | Add comment |
Saturday, 26 August 2006
|
| Security Markup Ahmed Saad 03:02:34 |
| |
Hello all,
I'm no expert on (X)HTML but I had an idea that I think might help
implement more secure web applications, in more specific words,
protecting users against XSS attacks. The idea is to add a "nocode"
(or a more descriptive name) attribute to elements that hints the
browser to not execute any client-side code found within that element.
For example, a content management system or a blog software that
allows comments on some entry might use the following markup ..
<div id="comment123" nocode="true">
<script type="text/javascript">alert('This piece of code will not be
executed even though it evaded the server-side filter');</script>
</div>
Of course it's not a complete alternative to server-side filters, but
it would act as a secondary safe guard solidifying a "defense in
depth" approach. Comments are welcome.
Regards,
Ahmed
|
| | 18 answers | Add comment |
Friday, 25 August 2006
|
| Keeping the structure, Moving the meaning Re: samp, kbd, var Karl Dubost 11:24:08 |
| |
Le 24 ao t 06 15:18, David Woolley a crit :>> - These semantics of meaning are useful>> - These should not be element but role/property attribute values.>
I'd say that was in conflict with the original SGML concept, and > actually> represents a move towards a presentational language.
The original SGML specification is in front of my eyes right now and
nothing is said in this sense. But let's clarify a bit more, because
it's definitely not a move towards a presentational language.
XHTML 2.0 Specification abstract says it
[[[
XHTML 2 is a general-purpose markup language designed for
representing documents for a wide range of purposes across the World
Wide Web. To this end it does not attempt to be all things to all
people, supplying every possible markup idiom, but to supply a
generally useful set of elements.
]]] -- XHTML 2.0
http://www.w3.org/TR/2006/WD-xhtml2-20060726/
Wed, 26 Jul 2006 20:04:34 GMT
I will avoid to use word "semantics", because it has too many
understanding and will dilute the message. Let's keep this in mind:
"general-purpose markup language"
I think we can agree that the fields of *meaning* for text and
applications are wide, very wide. Each profession, each domain has
its own set of meaning, with sometimes overlaps.
HTML = Hyper Text Markup Language
Hyper stands for the link capability
Text stands for the text.
Since the beginning of HTML, we can classify the elements in 3
categories
- Structure: p, li, table, etc.
- Functionnal: a, form, link, etc.
- Meaning: code, quote, samp, address. etc.
The proposal here is not to remove "Meaning" but to move it from the
element to the "property/role" attribute, which have been conceived
for this purpose. Creating a specification which would cover all
possible meanings even only the most important, would be tiresome,
not achievable in a reasonable time and highly unsatisfying because
of different cultural needs and professional needs.
The block/inline model is part structural par presentational
(inheritage of the codex as in conveying structure by a specific
layout), CSS covers it which is right.
Keeping "Meaning" elements leads to problems of presentation
specifically:
blockcode/code
blockquote/quote
Duplication of "meaning" elements because of presentational aspects.
Keeping the "structure" element and at a certain degree "functional"
element meets exactly the general purpose nature which is stated at
the beginning. More than that, it makes it the ideal vehicle to
create "meaning" application of all kind without too much trouble.
I don't really like role, because it seems to be an abdication of> responsibility, which could result in every web site having its own> definition of what role names are and what they mean.
Yes and that's good. Right now, an author has the choice of the terms
to be used in "class" attribute values. Standards are a community and
social process where a community agrees on the needs of this community.
Sets of values for "role" and "property" can be defined exactly in
the same way than the semantics of an element, either being "meaning"
or "structure". It's a question of defining them.
The proposal is to ship with XHTML 2.0 what was before "meaning"
elements has a standardized set of modules defining the values for
the attribute role and property. Exactly what WAI will do, and
exactly what XHTML 2.0 already does for certain values.
It is not an abdication at all, it is a proposal to give more
flexibility, to have specifications and associated schemas a lot
easier to maintain.
I think I would much rather have first class elements, but if the > elements> aren't considered general purpose enough, there should be standards> profiles defined, which, for example, had different profiles for say;> e-commerce sites; corporate sites; informational sites; search > engines,> leaf node pure documents, etc. Each profile could be made of several> modules, but authors would be expected to use a complete profile, not> make their own selection from modules.
That is the proposal. Even better a professional domain could say we
need a standard set of values for our profession. Can we do it at
W3C? Yes! Do it.
I'm not convinced this will work, though, because most authors seem to> want to confuse CSS, EcmaScript, object models, and Flash into a > single> thing that they call HTML.
Most authors don't edit their page by hands, the authoring tools
(forms, converter, or HTML authoring tools) do. It's a lot easier to
add set of defined values than having to deal with adding new
elements for each version of the language.
I hope I made the proposal clearer.
--
Karl Dubost - http://www.w3.org/People/karl/
W3C Conformance Manager, QA Activity Lead
QA Weblog - http://www.w3.org/QA/
*** Be Strict To Be Cool ***
|
| | 2 answer | Add comment |
|
| sub/sup (was Re: samp, kbd, var) Patrick H. Lauke 11:13:30 |
| |
Along the same lines, what about sub and sup? To me, they seem
dangerously close to presentational markup, unless someone can enlighten
me as to what the semantic meaning of these two elements is...
The examples given at
http://www.w3.org/TR/xhtml2/mod-text.html#sec_9.12. aren't making it any
clearer:
H<sub>2</sub>O
E = mc<sup>2</sup>
Surely this should be marked up more rightly with something like MathML?
<span xml:lang="fr">M<sup>lle</sup> Dupont</span>
As the line just above the example states: "Many scripts (e.g., French)
require superscripts or subscripts for proper rendering." So,
"rendering" to me again suggests visual, unless you're suggesting that
if "lle" isn't set as sup (when other forms of styling are
disabled/unavailable), Mlle loses its meaning (which I'd contest).
P
--
Patrick H. Lauke
__________________________________________________________
re dux (adj.): brought back; returned. used postpositively
[latin : re-, re- + dux, leader; see duke.]
www.splintered.co.uk | www.photographia.co.uk
http://redux.deviantart.com
__________________________________________________________
Web Standards Project (WaSP) Accessibility Task Force
http://webstandards.org/
__________________________________________________________
|
| | 15 answers | Add comment |
|
| samp, kbd, var Toby Inkster 11:11:57 |
| |
What are these elements still doing in XHTML 2? They're an anachronism!
<samp>Hello World</samp> => <q role="compsci:outputScreen">Hello World</q>
<var>i</var> => <code role="compsci:variable">i</code>
<kbd>Alt + X</kbd> => <span role="compsci:inputKey">Alt + X</span>
--
Toby Inkster <tobyink@goddamn.co.uk>
|
| | 29 answers | Add comment |
Thursday, 24 August 2006
|
| Re: Re: samp, kbd, var and code Peter Krantz 02:28:27 |
| |
On 8/23/06, Toby Inkster <tobyink@goddamn.co.uk> wrote:>
Yes -- this is mostly my point. XHTML 2 still has too much compsci stuff> in it. I can see how <code> can be useful: I use it myself frequently,> which is why it's not in the subject line of this thread.>
I am sorry but "code" is not part of a generic document markup format
even if you personally find it useful. As covered earlier, the
extensibility of XHTML2 makes it easy for you to add whatever module
you may require for your domain.
code and blockcode should be removed with samp, kbd and var. Is there
anyone on this list that can argument for their existence?
|
| | 3 answer | Add comment |
Wednesday, 23 August 2006
|
| Re: extensibility of role/class/property/rel Al Gilman 22:48:29 |
| |
Apologies for continuing this digressive sub-thread.
The initial security markup idea has been addressed in other forks.
But the misconceptions aired here have long beards, so somehow
I feel compelled to address them.
To begin with,
<quote
cite="">
The whole point of QNames is disambiguation, not interoperability.
</quote>
There's a hoary misconception if I ever saw one.
True, QNames were introduced in the Namespaces in XML Recommendation,
where it says that the prefixes that qualify QNames are for disambiguation.
There is no other omnibus semantic for the prefixes.
That doesn't change the fact that the qualified *names* so disambiguated
are about whatever the names thus distinguished are about in their respective
namespaces. The Namespaces Rec places no limits on the semantics
of the names disambiguated by these prefixes. It just doesn't set any
higher floor on their semantics.
The XML+namespaces generic processing of a document instance can be
completed without using the prefixes for anything but disambiguation. But
that does not say that a compound document which employs QNames after
the manner of Namespaces in XML has been carried to completion at that
point. There is a lot of namespace-dependent processing yet to go.
*The point of disambiguation* in QNames is to preserve the interoperability
that is afforded by the namespace-local names.
.. to continue with the recent discourse...
At 10:54 AM +0900 8/23/06, Karl Dubost wrote:>Hi Mark,>
Le 22 ao t 06 18:01, Mark Birbeck a crit :>>Karl,>> but the issue, I have raised is about the second aspects, which is>>>the mechanism to prefetch values and their definitions in a user>>>agents. The same way, it is possible to fetch DTD, schemas, etc and>>>do something with them because the software knows the grammar for>>>reading a DTD or schema>> If I understand you correctly, you are saying that behaviour can be>>defined using RDF, and this RDF can be retrieved at run-time based on>>the use of @role.> Not exactly and not necessary RDF, but it's one possibility.>Restating the issue:> When someone, an organization, a group want to define a vocabulary >for property, role, class, etc to be used in XHTML 2.0> 1. There must be a file with the values and their associate >definitions somewhere on the Web.>2. There must be an *interoperable* and *defined* mechanism >to load the values and their definitions in a software.> It is not necessary the software for the software to understand the >meaning of the values or to have a specific behaviour for each >values.
Now we are making progress. That is how you perceive "the issue."
That framing of the issue doesn't suffice, however, either for the
security issue that started this thread, or for access to rich
internet applications.
The capability that you assert as "the issue" here would indeed
in many circumstances be value added. But to say at the outset
that this increment of value added is all that is appropriate to add
is, in my understanding, unjustified.
For example, look at how far this thread has drifted. Clearly
"security markup" doesn't merit that epithet unless it has very
reliable implications for system behavior.
Likewise, in the sub-topic of "access to interactive widgets" which
is a significant part of the 'roadmap' work in PFWG, there are
behavior conventions that are part of the existing understanding
between Assistive Technology and mainstream installed applications
that are captured in the access APIs. Creating markup that keys the
binding of web applications to those APIs clearly has behavioral
connotations that are inherited from the existing community
agreements at the API level. We do our customers disservice if we
pretend the behavior aspect is not part of the deal.
I think we have to go back to Noah's mantra of "partial
understanding." The metadata can and should shift the frontier of the
machine's [partial] understanding of the pragmatic semantics. Even
'though it still won't get it all.
But it is important that the user of the software can have access to >the prose defining of the values,
This assumption that the definition is prose and not literate
programming is an arbitrary limitation of the possible value-add of
the metadata. For example, to see why this is an anti-socially
discriminatory limitation, read Lisa Seeman's copious output on the
values of concept coding in addressing the needs of those with
cognitive disabilities, such as
http://www.w3.org/WAI/PF/usage/languageUsageAndAccess.html
I fully recognize that the simple pattern of a machinable link to
human-able documentation is frequently all we can provide in
mitigating access barriers. But this does not equal an a-priori
"requirement" that is limited to that pattern. We need to be
designing in a space that opens the door to more machine initiative
in affording assistance than that pattern allows.
Al
so developers do not have to hardcode all possible values and their >definitions that groups could define.>The intent is to really:>1. make the life of developers easier>2. promote the usability of vocabularies>3. promote the practice of well defined vocabularies> If so, I agree with you 110%. That has been my>>'dream', so to speak, since even before I got involved in the HTML WG.>>;) However...as Shane has pointed out, what the group has been very>>careful to do, is not *mandate* this approach.> HTML 4.01 made possible to have "alt" attributes, and "title" >attributes, which gives more information about an information given >in a document. It is exactly the same kind of approach.>It has also accessibility and usability benefits for people >authoring documents.> Example: Use case scenario in HTML 4.01> <dt id="vcard">vcard</dt>> <dd>A container for the rest of the class names defined in this >XMDP profile.> See <a href="../../2002/12/cal/rfc2426#sec1.">section 1. of RFC 2426</a>.> </dd>> And presents to the author a list of values and their associated >definitions, then the author can choose among these values.> Another benefit is that the authoring can have up to date >definitions if these ones are changing slightly.> I think we've gone about as far as we can at this stage of the>>language's development by adding the necessary hooks for such>>functionality--@role, RDFa, and so on.> What kind of hooks would help to achieve the scenario described >above? That would be very interesting indeed.> The next phase is to let people>>use it, and see what emerges. Taxonomies like the one Al refers to>>will begin to emerge, and then we can start looking at how we define>>the features of those taxonomies, how we locate them, and so on. But>>it would be premature to try to define this now, since we just don't>>have the experience. (And that definition need not be in XHTML 2>>anyway, but should be a separate spec.)> The thing is that it is possible to call a stylesheet, there's the >mechanism to do that. Is there a mechanism to tie the extension of >values of roles, class, etc.> So, the state of play is that we have a mechanism that can be used in>>a many ways...we have a 'hook'. This hook could be used simply as a>>container for a unique cookie that a browser or some server process>>understands inately (the QName as identifier), or the hook could point>>to some data to be retrieved and used by a process, such as a>>server-side transformation or dynamically in the browser itself to>>control behaviour (the QName as URI). But at the moment implementers>>can choose how to use it.> The hook is? namespace URI?>
|
| | Add comment |
|
| extensibility of role/class/property/rel Re: Security Markup Karl Dubost 05:54:28 |
| |
Le 22 ao t 06 01:34, Shane McCarron a crit :> Karl Dubost wrote:>>
Issue to solve.>> Same than for "property" attribute.>> There is no defined mechanism to extend the values of role/ >> property/rel/class attributes.> Sure there is. You can create any values you want for role, > property, rel: they are defined to be QNames. Just declare a > namespace and do whatever you want within that namespace. Sort of > the whole point of QNames. The values that are defined in the > XHTML 2 draft are in the XHTML namespace.
It is not a *defined* mechanism.
The whole point of QNames is disambiguation, not interoperability.
"Do whatever you want" doesn't help interoperability on what has been
defined at all and promotes things like:
[[[
In a User Interface if a model was clearly, it would make it possible
for
- User agent to display the definition of the property if requested
(accessibility, usability)
- Authoring tool to display a menu with choices of values and their
definition when editing
- Search engines to index content with help on definition when
someone is using the search engine.
]]]
-- [xhtml2] extending values for property from karl@w3.org on
2006-08-17 (www-html-editor@w3.org from July to September 2006)
http://lists.w3.org/Archives/Public/www-html-editor/2006JulSep/0090
Thu, 17 Aug 2006 10:04:02 GMT
We could imagine that there is a way with XML, RDF, simple XHTML
file, a way to create a reference which is explaining the goal and
meaning of the new values and which is automaticly processable by
user agents (including authoring tools and others).
--
Karl Dubost - http://www.w3.org/People/karl/
W3C Conformance Manager, QA Activity Lead
QA Weblog - http://www.w3.org/QA/
*** Be Strict To Be Cool ***
|
| | 6 answers | Add comment |
Saturday, 19 August 2006
|
| Extending "Short" or "Shallow" Webpages to Effect Jumps to Anchors Within Guest 11:34:15 |
| | Once spoiled by links that jump to a section within a document such as at:
http://www.gutenberg.org/browse/authors/d#a37
the occasional link to such as:
http://en.wikipedia.org/wiki/Bleak_House#External_links
where the relevant code within
<a name="External_links" id="External_links"></a>
to the heading
*External links*
is mid-page rather than at top because there isn't enough page following the
heading.
Surely there are many suggestions/alternatives to effect that heading
appearing at the top of the window that might be entertained, even if
ridiculous.
Aren't they all browser standard change suggestions?
Is it all pass the buck?
What are related issues?
Surely an outline of failing considerations would be comedy enough for a
week.
"What have they done to my webpage? It's so long in this window??? I didn't
put that whitespace at the bottom of the page. Maybe it's my browser. Let me
check my page in another window. Hey! There's no whitespace in this one.
Didn't I upload my most recent version? Has there been a version change of
my IE? I'd better send them a letter to change it back. It's messed up.
Maybe a standards board can straighten out that bloated monopoly. Where's my
congressman's email address?"
--
Gordon Murray
Chicago:1-312-212-DING
Ottawa: 1-613-729-4129
060601@eastontario.com
"eastontario" on skype (www.skype.com)
|
| | 3 answer | Add comment |
Friday, 18 August 2006
|
| XHTML2 and JS ads Magick 21:52:38 |
| |
Do you think by the time XHTML 2.0 ready for use (use your own term,
public release, stable release, whatever) ad services such as Google and
Clicksor will have XHTML2-compatible ads? Right now their ads aren't
compatible with application/xhtml+xml
Also, does anyone have any idea of when XHTML 2.0 will be ready for
public use?
|
| | 9 answers | Add comment |
Thursday, 17 August 2006
Tuesday, 15 August 2006
|
| validation problem Richard 18:24:00 |
| | Checking my latest playtoy for errors I run across these two gems I can't
figure out.
1) "div" not allowed here.
2) "A" not allowed here.
www.somestuff.batcave.net/expandmenu2.htm
Since that was put up, I have cleaned up a few items.
Put the script in an external file so any errors on that part should be
ignored.
Don't flame me for the script bugs. I did not write it as clearly stated in
the comments.
|
| | 12 answers | Add comment |
Monday, 14 August 2006
|
| Moving folder contents on a server... Dorayme 16:02:35 |
| | I would appreciate any advice on how best to move the contents of
a folder up one or two levels on a server. Not something I much
do. I did it by deleting the whole thing and then going up a
level and uploading the files from my local machine, loose to
that level... but I suspect there is more intelligent, not
needing to reload them all up. Unix server, normal sort of FTP
program as far as I can tell. Perhaps I better read the FTP
program manual on these things again... but I cannot resist
pestering you lot to see if I get lucky first...
--
dorayme
|
| | 4 answer | Add comment |
|
| 2 text alignment on the same line Allerdyce John 14:39:02 |
| | Hi,
Can someone please tell me how can I have 2 text alignment on the same
line?
I want a line where it has 'left text' to the farest left of the line
and 'right text' to the farest right of the same line.
I try below, but it does not work. It has 'left text' and 'right text'
next to each other:
<span style="color urple" align="left">left text</span><span
style="color:green" align="right">right text</span> <br/>
And I try not to use Table or css float to achieve that.
Thank you.
|
| | 5 answers | Add comment |
|
| [News] Internet Explorer 7 Still Against Web Standards Roy Schestowitz 14:18:11 |
| | http://developers.slashdot.org/article.pl?sid=06/08/07/1824250&from=rss
,----[ Quote ]
| With the redesign of my own site last month, I discovered just
| how non-compliant IE is with basic CSS: IE 52% vs. Firefox 93%. Is
| Microsoft purely incompetent and tone-deaf to customers -- or simply
| counting on IE's non-compliance remaining a de-facto standard?"
`----
Points to: http://www.idealog.us/2006/08/microsoft_drops.html
|
| | 17 answers | Add comment |
|
| html to css help!! Koolbreak 14:01:28 |
| | Ok I need help. im a newbie to css..i know most html. i need to change
this html to xhtml and css. Can someone just show me so that i can
learn? i tried all those online tutorials but its a no go. ok here:
<td height="78" align="left" valign="top"><img src="images/title.gif"
width="777" height="78"></td>
</tr>
</table>
<table width="777" border="0" align="center" cellpadding="0"
cellspacing="0">
<tr align="center">
<td width="200" align="left" valign="top"
background="images/bg-left.jpg"><table width="200" height="256"
border="0" align="center" cellpadding="0" cellspacing="0"
class="leftmenu">
<tr>
<td width="200" height="25" align="center" valign="top"
class="white-text"> </td>
</tr>
<tr>
<td height="227" align="center" valign="top"> </td>
</tr>
</table></td>
<td width="577" valign="top" bgcolor="#FFFFFF">
<table width="577" border="0" cellspacing="0" cellpadding="0">
<tr>
<td width="583" height="22" align="left" valign="bottom"
background="images/white-bar.gif" class="bar-spacing"><font size="2"
face="Arial, Helvetica, sans-serif" class="bar-text">Invite</font></td>
</tr>
</table>
<table width="577" height="344" border="0" cellpadding="0"
cellspacing="0">
<tr>
<td width="555" height="344" align="left"
valign="top"><table width="577" border="0" cellspacing="0"
cellpadding="0">
<tr>
<td align="center" valign="top" class="text">
<table width="100%" border="0" cellspacing="0"
cellpadding="0">
<tr>
<td height="30" valign="bottom"
class="text-bold-blue"><table width="100" border="0" cellspacing="0"
cellpadding="0">
</table></td>
</tr>
</table>
<table width="437" border="0" cellspacing="0"
cellpadding="0" class="invite-form">
<tr>
<td width="435" align="center">
<table width="423"
border="0" align="center" cellpadding="0"
cellspacing="0" class="confirm">
<tr>
<td width="421" height="326"
valign="top"><table width="100%" height="97" border="0" cellpadding="0"
cellspacing="0" class="confirm-inner">
<tr>
<td height="24"
class="confirm-line"><span class="confirm-text">Send an Invite
</span></td>
</tr>
<tr>
<td valign="top"
class="confirm-info"><table width="100%" height="245" border="0"
cellpadding="0" cellspacing="0" class="confirm-info">
<tr>
<td height="245"
valign="top"><table width="408" border="0" cellspacing="0"
cellpadding="0">
<tr>
<td width="63" height="25"
class="bold-text-Black">From:</td>
<td width="345" height="25"
class="text-blue-no-underline">Matt Beckham <m...@get2spec.com>
</td>
</tr>
<tr>
<td height="25" class="bold-text"> To: </td>
<td height="25" class="text">Seperate email addresses
with
commas </td>
</tr>
<tr>
<td height="84" class="text"> </td>
<td height="84" valign="top"><label>
<textarea name="textarea"
class="invite"></textarea>
</label></td>
</tr>
<tr>
<td height="25" valign="middle"
class="bold-text">Message:</td>
<td height="25" valign="middle" class="text">Send a
message
with the invite (optional). </td>
</tr>
<tr>
How do I take out the tables and turn it inot css? please help!! Thank
you...
|
| | 6 answers | Add comment |
|
| Determine what elements are slowing a web page load John 13:54:04 |
| | Hello,
I use FP 2003, and one feature is that it shows a report which tells you how
long a page will load based on 56K speed.
For instance, it will say "index.htm" will load in 48 seconds, etc.
Is there a way/ program to determine what INDIVIDUAL ELEMENTS of a webpage
are taking up the most time so that one can concentrate on whittling down
the big stuff?
Something that says:
Table or Stylesheet- 20 seconds
Page background-5 seconds
123.jpg- 10 seconds
456.jpg -10 seconds
top of page jpg 3 sec
Total = 48 seconds.
?
Surfing around, I found an online type of service, but I was wanting a
program I can download and use off-line.
Any help appreciated.
VR/
John
|
| | 4 answer | Add comment |
|
| More lies from Richard Scoville Gary L . Burnore 08:36:22 |
| | On 12 Aug 2006 07:57:43 -0700, DefamationOuter@aol.com wrote:
This is where this PUNK resides...>Address as of June 2004... http://tinyurl.com/munxq>224 ARMOUR STREET>DAVIDSON, NC 28036>Phone No.: 704-578-5577> His access is through RR residential service using Dynamic IP>addresses. In his most recent access IP 66.57.248.154. Having>problems with this PERVERT, then report him to Roadrunner and the folks>below...>
Yeah! Report me to RR and to NC! Hahaha.
June 2004. Hahahahahahahahah. NC. Hahahahahahahahaha. Roadrunner.
Hahahahahahahahahaha. Scoville, you crack me up.
--
gburnore at DataBasix dot Com
---------------------------------------------------------------------------
How you look depends on where you go.
---------------------------------------------------------------------------
Gary L. Burnore | ÝÛ³ºÝ³Þ³º³³Ýۺݳ޳ݳݳ޳ºÝ³ÝÛ³
| ÝÛ³ºÝ³Þ³º³³Ýۺݳ޳ݳݳ޳ºÝ³ÝÛ³
Official .sig, Accept no substitutes. | ÝÛ³ºÝ³Þ³º³³Ýۺݳ޳ݳݳ޳ºÝ³ÝÛ³
| ÝÛ 0 1 7 2 3 / Ý³Þ 3 7 4 9 3 0 Û³
Black Helicopter Repair Services, Ltd.| Official Proof of Purchase
===========================================================================
|
| | 9 answers | Add comment |
|
