Your message dated Tue, 13 Mar 2012 10:23:52 -0400
with message-id <4f5f5878.7070...@debian.org>
and subject line Re: Bug#660707: www.debian.org: an invalid XML/XHTML syntax in
anchor tag's href attribute format on
/cvs/webwml/english/News/weekly/2012/03/index.wml
has caused the
Hi Ryuunosuke,
Le 21/02/2012 02:47, AYANOKOUZI, Ryuunosuke a écrit :
>> So what is the point of fixing the source if the generated file is
>> correct (WML source file are not meant to be XML valid)? It's one of the
>> WML feature to fix those details. Please note that we have a daily run
>> to ch
Hi David,
> So what is the point of fixing the source if the generated file is
> correct (WML source file are not meant to be XML valid)? It's one of the
> WML feature to fix those details. Please note that we have a daily run
> to check the validation of every pages, and translation coordinators
Processing commands for cont...@bugs.debian.org:
> user www.debian@packages.debian.org
Setting user to www.debian@packages.debian.org (was taf...@debian.org).
> usertag 660707 news
Bug#660707: www.debian.org: an invalid XML/XHTML syntax in anchor tag's href
attribute for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
user www.debian@packages.debian.org
usertag 660707 news
severity 660707 minor
tags 660707 moreinfo
thanks
Hi Ryuunosuke,
> There is an invalid XML/XHTML syntax in anchor tag's href attribute
> format on /cvs/webwml/english/News/wee
Package: www.debian.org
Severity: normal
There is an invalid XML/XHTML syntax in anchor tag's href attribute
format on /cvs/webwml/english/News/weekly/2012/03/index.wml. WML seems
to make modification to it and generate valid XML/XHTML file
(http://www.debian.org/News/weekly/2012/03/index.en
On Sun, Aug 05, 2007 at 10:32:34PM +0200, Bas Zoetekouw wrote:
> No. Have you actually looked at the pages that are produced? Wml
> automatically changes to unless explicitly told not to.
Ah, OK - thanks, I didn't realize that! I did have a look at the page, but
assumed that the relevant CVS
Hi Richard!
You wrote:
> >> -
> >> +
> >
> > I'm wondering if we have a proper plan for switching to xhtml, or this
> > markup polishing is just a substitute activity -- in the sense that yes, we
> > know that xhtml requires closing all elemen
On Sun, Aug 05, 2007 at 02:03:10PM +0300, NAGY Viktor wrote:
> [EMAIL PROTECTED] wrote:
>> -
>> +
>
> I'm wondering if we have a proper plan for switching to xhtml, or this
> markup polishing is just a substitute activity -- in the sense that yes, we
> know
* Jutta Wrage <[EMAIL PROTECTED]> [2006-03-19 20:27]:
> I converted the list to a definition list as it is one semantically.
>
> Entries where:
>
>
> Definition term here (known issue)
> definition here
>
>
> It is easy to replace all by and all by , but it
> makes more work if some files
mmit.
> This is quite fast and I edited a lot of files (2000?, more?) this
> way always having to spend more time, if these and other xhtml
> tags where there in one of the files.
>
> I think all languages should have the same markup beside a few
> language specific thi
On Sunday 19 March 2006 20:27, Jutta Wrage wrote:
> I think all languages should have the same markup beside a few
> language specific things.
You're dealing with people here with different levels of experience in
wml/html. You can hope for this situation, but I doubt you'll be able to
force it.
000?, more?) this
way always having to spend more time, if these and other xhtml
tags where there in one of the files.
I think all languages should have the same markup beside a few
language specific things.
greetings
Jutta
- --
http://www.witch.westfalen.de
http://witch.muensterland.org
On Sun, Mar 19, 2006 at 03:56:40PM +0100, Jutta Wrage wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi!
>
> As I have seen that a few pages use xhtml closing tags, a note about
> editing those files with vi and making mass changes (all languages
> for o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
As I have seen that a few pages use xhtml closing tags, a note about
editing those files with vi and making mass changes (all languages
for one page at the same time).
for example I want to take the tag.
Sometimes it is necessary to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 23.08.2005 um 22:58 schrieb Denis Barbier:
first step is to fix english/template/debian/*.wml files, then test
XHTML output on a small directory.
But again, XHTML generation will fail if tags are not properly nested,
so this is a very invasive
On Mon, Aug 22, 2005 at 04:42:46PM +0200, Frans Pop wrote:
> On Monday 22 August 2005 13:04, Tommi Vainikainen wrote:
> > These files called templates you will find from
> > webwml/english/template/debian directory. You probably need to adjust
> > those files to use XHTML in
On Monday 22 August 2005 13:04, Tommi Vainikainen wrote:
> These files called templates you will find from
> webwml/english/template/debian directory. You probably need to adjust
> those files to use XHTML instead of what current HTML 4.01
> Transitional, and then go trough every pa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tommi Vainikainen wrote:
> On 2005-08-21T20:02:59+0300, [EMAIL PROTECTED] wrote:
>
>>What I want to do is convert xhtml pages on
>>www.debian.org to XHTML 1.0 Strict. The thing is that debian.org
>>uses a tool called WML to g
On 2005-08-21T20:02:59+0300, [EMAIL PROTECTED] wrote:
> What I want to do is convert xhtml pages on
> www.debian.org to XHTML 1.0 Strict. The thing is that debian.org
> uses a tool called WML to generate the web pages. I need help in
> learning how to do this. I've downloaded t
Hi, everyone!
Someone on #debian (I believe it was madduck) suggested for me to post this
on the list. What I want to do is convert xhtml pages on www.debian.org to
XHTML 1.0 Strict. The thing is that debian.org uses a tool called WML to
generate the web pages. I need help in learning how to
don't think that the benefits of converting the pages to
XHTML is worth the effort needed. We should try to keep
an eye on new pages, though, to make the situation not much worse. New
pages should always be valid HTML strict and valid XHTML, if possible
(wml takes care of removing /> endings of
Hi!
Maybe not all read Anne van Kesteren's weblog about HTML/XHTML/CSS...
There is another interesting article, why not to use XHTML. - As
mentioned before, one problem is that XHTML has to be served as
xhtml+xml and _not_ as text/html to keep the standards, and browsers
would go into Q
On Sun, Nov 21, 2004 at 01:23:26PM +0100, Jutta Wrage wrote:
>
> Am Sonntag, 21.11.04 um 05:00 Uhr schrieb Mike Hommey:
>
> >It is wrong. xhtml 1.0 pages SHOULD be served as application/xhtml+xml
> >but can be served as text/html for compatibility purpose.
>
> Can
Am Sonntag, 21.11.04 um 05:00 Uhr schrieb Mike Hommey:
It is wrong. xhtml 1.0 pages SHOULD be served as application/xhtml+xml
but can be served as text/html for compatibility purpose.
Can you point me to the source, where it says that they may be served
without application/xhtml+xml without
Hi,
http://www.debian.org/social_contract.en.html contains two lists
("Social Contract" and DFSG) but both are not XHTML conforming.
Debian Will Remain 100% Free Software
[text]
We Will Give Back to the Free Software Community
This results in the following output in konqueror
* [EMAIL PROTECTED] [2003-12-28 03:25]:
> Why does http://www.debian.org use WML instead of valid XHTML?
Because there is no contradiction with WML and XHTML. WML can generate
valid XHTML, thanks. With new pages we try already to produce them XHTML
compatible, but there are tons of old pa
Why does http://www.debian.org use WML instead of valid XHTML? I'll be more
than happy to switch http://www.debian.org to use XHTML.
o---o
| Spencer Warren Wilson |
o---o
On Fri, 2003-12-05 at 21:04, Andre Lehovich wrote:
> Other than buzzword compliance, what advantages does this
> offer -- if it is nontrivial to switch to XHTML, why do it?
It has many advantages. XHTML is XML, so valid XHTML can be transformed
to another format by a simple XSLT transfor
> 2.) Conversion of _all_ other wml files to XHTML compatible WML code.
> This isn't a trivial task.
Other than buzzword compliance, what advantages does this
offer -- if it is nontrivial to switch to XHTML, why do it?
--Andre
On Wed, Dec 03, 2003 at 10:21:06AM +0200, Fabian Fagerholm wrote:
> I read on the Debian Website development page about the intent to
> eventually transition the www.debian.org web site to using XHTML. How
> far has this effort come, and what would be the procedure to help with
> thi
Hi,
I read on the Debian Website development page about the intent to
eventually transition the www.debian.org web site to using XHTML. How
far has this effort come, and what would be the procedure to help with
this transition?
Cheers,
--
Fabian Fagerholm <[EMAIL PROTECTED]>
signatu
Resend, because it seems no to have reached the BTS.
- Forwarded message from djpig -
To: [EMAIL PROTECTED]
Subject: xhtml: Some patches for the templates
[#98811: Future or updated pages should use XHTML 1 if possible]
I just checked the webpages if they compile with the wml option
On Sat, Jan 12, 2002 at 02:13:31PM -0500, James A. Treacy wrote:
> When editing wml files, we should start moving all the tags and
> attributes to lowercase. You don't need go change every file today,
> simple start changing them when you are editing the file anyway.
I must point out again that fo
Denis Barbier wrote:
> nearly all required changes were already described in the bugreport:
>a. Put all tags and attributes (but not attribute values) in
> lowercase
> letters
>b. Optional end tags are no more supported, so
>some text here
> must be written
>
* peter karlsson <[EMAIL PROTECTED]> [011220 14:49]:
> [...]
> Besides, Netscape 4 is ancient stuff, and it would be nice not to have to
> cater for it :-/
Do the logs for the website show what most people to the www.d.o site
use? or could they be easily changed to show this information?
--
--
Richard Atterer:
> No way! Netscape _4.77_ understands *none* of those entities! Please
> don't disable the substitution.
Netscape 4.77 *do* support them, but it has all its problems with displaying
characters outside the local encoding of the page, no matter if it supports
the entity or not.
Be
* Richard Atterer <[EMAIL PROTECTED]> [2001-12-19 14:51]:
> BTW, when referenced by decimal or hex value, the entities do work (in
> the sense that the characters are approximated with ISO-8859-1
> characters). E.g. ” doesn't work, but ” or ” does.
That would make them unicode characters, not
iso
be nice.
Maybe we could also use these pages to check that all browsers can rendered
pages when converted into XHTML. Ooops, could not resist, sorry :)
Denis
On Wed, Dec 19, 2001 at 11:24:25PM +0100, Denis Barbier wrote:
> We could either fix the problems when they are discovered, or wait for
> massive changes.
If you don't mind me saying, we could also leave this be, and instead attend
to more pressing matters :)
I'll go add hints to devel/website ab
, here are some
items:
1. A missing end tag has not yet been fixed in wml::debian::footer
in order not to change output.
2. `Minimized' attributes (i.e. attribute without values, e.g. )
are invalid with XHTML. We could either write noshade="noshade" in all
ca
On Wed, Dec 19, 2001 at 04:12:51AM +0100, peter karlsson wrote:
> Josip Rodin:
> > Some old Netscapes don't grok mdash. Not sure about others, though
> > the reason is probably similar.
>
> In the case of Netscape, I think it only applies to 3.x and earlier,
> so I don't think it should cause many
Josip Rodin:
> Some old Netscapes don't grok mdash. Not sure about others, though the
> reason is probably similar.
In the case of Netscape, I think it only applies to 3.x and earlier, so
I don't think it should cause many problems changing it not to
substitute the characters.
--
\\//
peter - h
On Tue, Dec 18, 2001 at 09:53:43PM +0100, Denis Barbier wrote:
> On Tue, Dec 18, 2001 at 03:29:24PM -0500, James A. Treacy wrote:
> > I have mostly converted the template files as per the previous
> > discussion. Just a few comments:
> >
> > template/debian/weekly/ wasn't touched (plan to do it la
On Tue, Dec 18, 2001 at 09:53:43PM +0100, Denis Barbier wrote:
> While we are on templates, Peter asked why there are entities substitutions
> in basic.wml l.126:
> [[s/—/--/g]] [[s/–/-/g]] [[s/&[lr]dquo;/"/g]] [[s/‘/`/g]]
> [[s/’/'/g
> Does someone remember why this was needed?
Some old Netsc
On Tue, Dec 18, 2001 at 03:29:24PM -0500, James A. Treacy wrote:
> I have mostly converted the template files as per the previous
> discussion. Just a few comments:
>
> template/debian/weekly/ wasn't touched (plan to do it later)
>
> there are some in the template files. I didn't create correspo
I have mostly converted the template files as per the previous
discussion. Just a few comments:
template/debian/weekly/ wasn't touched (plan to do it later)
there are some in the template files. I didn't create corresponding
I won't be able to touch this until after Christmas and didn't want t
On Mon, Dec 17, 2001 at 10:51:12AM +0100, Norbert Bottlaender-Prier wrote:
> 17/12/2001 04:36:03, "James A. Treacy" <[EMAIL PROTECTED]> a écrit:
> >...
> >Should the first line be change:
> >
>
> HI James,
>
> As the xhtml 1.0 specificatios
17/12/2001 04:36:03, "James A. Treacy" <[EMAIL PROTECTED]> a écrit:
>...
>Should the first line be change:
>
HI James,
As the xhtml 1.0 specificatios apply no extension to the html 4.01 specs
but rather some restriction, all xhtml 1.0 docs are supposed to comply
On Sun, Dec 16, 2001 at 11:28:27PM +0100, Denis Barbier wrote:
>
> nearly all required changes were already described in the bugreport:
>a. Put all tags and attributes (but not attribute values) in lowercase
> letters
>b. Optional end tags are no more supported, so
>some
he web pages
> > can't go to w3.org and read the 46 pages (+ the DTDs and whatnot) of the
> > specification ;) but if at least an overview of required changes was
> > available (maybe it exists already?) that would speed up closing of this
> > bug.
>
> Get wml
DTDs and whatnot) of the
> specification ;) but if at least an overview of required changes was
> available (maybe it exists already?) that would speed up closing of this
> bug.
Get wml xhtml compliant would be #1. I don't think it is. It's html
4.01 compliant (but not 4.0). Dennis
This flag modifies how mp4h parses input, and is suitable for XHTML
pages. Since all tags are then considered as being complex, processing
is broken if trailing slash is missing in empty elements.
Fix broken pages.
5) Set this flag in Makefiles to make it the default,
Hi,
It would be good if someone provided a thorough list of things we'd have to
change. It's not like me and other fifty or so people who edit the web pages
can't go to w3.org and read the 46 pages (+ the DTDs and whatnot) of the
specification ;) but if at least an overview of required changes was
Please read entirely before shouting :o)
One day or another we will switch to XHTML.
The main issue is with empty tags, they require a trailing slash. With
the current WML (and there is no plan to change this soon, it would
imply a deep rewriting of wml_p2_mp4h), if source files have these
55 matches
Mail list logo
