Re: ion-ion-format open for public comment

2006-12-19 Thread Julian Reschke 

Frank Ellermann schrieb:

...
Non-ASCII, the xml2rfc txt or unpg output is ASCII.  The HTML of
rfcmarkup is very nice, but at that point all meta-data and non-ASCII
is already lost.  Maybe xml2rfc should get a new XHTML output option,
not your dogfod of course, normal XHTML 1.0 transitional text/html.

 ...

Such as with 
http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html#output.xhtml? 



Best regards, Julian


___
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

Re: ion-ion-format open for public comment

2006-12-19 Thread Frank Ellermann 
Julian Reschke wrote:
 
 Such as with
 http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html#output.xhtml?

I can't tell, is there an online XSLT engine somewhere to test it ?
When I'm able to use IE 6 I'm normally too busy for experiments :-(

Frank



___
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

Re: ion-ion-format open for public comment

2006-12-19 Thread Julian Reschke 

Frank Ellermann schrieb:

Julian Reschke wrote:
 

Such as with
http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html#output.xhtml?


I can't tell, is there an online XSLT engine somewhere to test it ?
When I'm able to use IE 6 I'm normally too busy for experiments :-(


You can use any common browser (Firefox, Opera, IE), or a command line 
tool (xsltproc, Saxon...).


If you insist on an online service, you can try 
http://www.w3.org/2005/08/online_xslt/ (but that currently dies with 
an NPE...).


Best regards, Julian

___
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

Re: ion-ion-format open for public comment

2006-12-18 Thread Brian E Carpenter 

Frank Ellermann wrote:

Brian Carpenter wrote:
 


Please see
http://www.ietf.org/IESG/content/ions/drafts/ion-ion-format.txt



It says text or html, but ion-ion-store is perfectly valid XHTML.
Is that a problem ?


I don't think so, do you?


The HTML output of xml2rfc is rather ugly with my browser, and its
nice unpaginated output doesn't offer meta-data and I18N, tough :-(

The HTML output is apparently also no valid HTML (tested with your
ion-procdoc draft), they forgot apos; in HTML 4.01, and apparently
UL needs a closing /UL - with HTML I never know, XHTML is KISS.


That is one for the xml2rfc list I think.


The SVN access doesn't work yet (authentification fails).


And that's the one you're discussing with Henrik.

   Brian

___
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

Re: ion-ion-format open for public comment

2006-12-18 Thread Frank Ellermann 
Julian Reschke wrote:

 IMHO it would be a good idea in the sense of own dogfood not to
 serve XHTML content with media type text/html.

Matter of taste, from my POV XHTML 1.0 transitional is the best way
to create backwards compatible (HTML 3.2) content visible with any
browser.
  
Or as the ion-ion-format draft puts it:  no fancy features.  If my
old browser sees some real XML it simply starts my text editor... ;-)

 The HTML output of xml2rfc is rather ugly with my browser, and its
 nice unpaginated output doesn't offer meta-data and I18N, tough :-(
 
 I18N?

Non-ASCII, the xml2rfc txt or unpg output is ASCII.  The HTML of
rfcmarkup is very nice, but at that point all meta-data and non-ASCII
is already lost.  Maybe xml2rfc should get a new XHTML output option,
not your dogfod of course, normal XHTML 1.0 transitional text/html.

Frank



___
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

Re: ion-ion-format open for public comment

2006-12-16 Thread Frank Ellermann 
Brian Carpenter wrote:
 
 Please see
 http://www.ietf.org/IESG/content/ions/drafts/ion-ion-format.txt

It says text or html, but ion-ion-store is perfectly valid XHTML.
Is that a problem ?

The HTML output of xml2rfc is rather ugly with my browser, and its
nice unpaginated output doesn't offer meta-data and I18N, tough :-(

The HTML output is apparently also no valid HTML (tested with your
ion-procdoc draft), they forgot apos; in HTML 4.01, and apparently
UL needs a closing /UL - with HTML I never know, XHTML is KISS.

The SVN access doesn't work yet (authentification fails).

Frank



___
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

Re: ion-ion-format open for public comment

2006-12-16 Thread Henrik Levkowetz 
Hi Frank,

on 2006-12-16 19:22 Frank Ellermann said the following:
...
 The SVN access doesn't work yet (authentification fails).

I just tried the recommended command:

 $ svn co https://www1.tools.ietf.org/svn/group/iesg/ions

with the following result:

  [EMAIL PROTECTED] $ svn co https://www1.tools.ietf.org/svn/group/iesg/ions
  Authentication realm: https://www1.tools.ietf.org:443 IETF
  Password for 'henrik': 
  Authentication realm: https://www1.tools.ietf.org:443 IETF
  Username: [EMAIL PROTECTED]
  Password for '[EMAIL PROTECTED]': 
  Aions/dated
  Aions/dated/ion-ion-format-2006-07-03.txt
  Aions/dated/ion-ion-store-2006-07-07.txt
  Aions/drafts
  Aions/drafts/ion-procdocs.html
  Aions/drafts/ion-ion-store.html
  Aions/drafts/ion-ion-format.txt
  Aions/drafts/ion-procdocs.xml
  Checked out revision 56.

If you have a password for authenticated access on tools.ietf.org
(go to http://tools.ietf.org/newpasswd to get one if you don't have one)
this should work for you.  If it doesn't, I'd very much like to get
details; which svn client you use, etc.; to work out what's wrong.


Regards,

Henrik

___
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf