cvs commit: xml-axkit TODO

[jw...@apache.org]

jwalt       02/03/12 11:10:15

  Modified:    .        TODO
  Log:
  add i18n (xml:lang)
  
  Revision  Changes    Path
  1.7       +17 -11    xml-axkit/TODO
  
  Index: TODO
  ===================================================================
  RCS file: /home/cvs/xml-axkit/TODO,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- TODO	27 Feb 2002 13:59:14 -0000	1.6
  +++ TODO	12 Mar 2002 19:10:15 -0000	1.7
  @@ -1,5 +1,5 @@
   
  -This is the TODO file for AxKit. Thank you for wanting to contribute! The 
  +This is the TODO file for AxKit. Thank you for wanting to contribute! The
   first thing you probably want to do if you haven't already is to check out
   the xml-axkit module from the cvs.apache.org CVS in order to get the latest
   code, and to read the CONTRIB file.
  @@ -10,7 +10,7 @@
   is described here. So before you jump on an item and hack it into AxKit you
   always want to ask the axkit-devel list about it and tell us what you think
   you'll be doing in that area. Paying a visit to #axkit can certainly help as
  -well. In any case, the cumulated experience of the folks that dwell there 
  +well. In any case, the cumulated experience of the folks that dwell there
   will certainly be of great help to you as you try to add something to AxKit.
   Remember that this is a community thing, we need consensus ;-)
   
  @@ -29,14 +29,14 @@
     . Documentation
   
       This is the job of the axkit-docs project. It really needs to be done and
  -    can use all the help that it gets. This would be a nice way to learn 
  -    AxKit's internals if you are not familiar with them. Ask the 
  +    can use all the help that it gets. This would be a nice way to learn
  +    AxKit's internals if you are not familiar with them. Ask the
       axkit-docs@axkit.org list.
   
   
     . Make the configuration fully XML
   
  -    The configuration as it is now is ok overall, but it's hard to extend 
  +    The configuration as it is now is ok overall, but it's hard to extend
       without writing some C code, which is a pain. Switching to an XML syntax
       would be a big win, though we don't want to make the mistakes the Cocoon
       folks made. We probably also want to make the syntax extensible with
  @@ -45,14 +45,14 @@
   
     . XSP executed twice when using the '.' href
   
  -    It has been reported that when using '.' as the href for the XSP 
  +    It has been reported that when using '.' as the href for the XSP
       stylesheet the XSP is executed twice. This has to be investigated, in the
       meantime one should use the preferred 'NULL' instead of '.'.
   
   
     . Splitting XSP out
   
  -    Currently XSP is tied into AxKit but it would make a marvellous 
  +    Currently XSP is tied into AxKit but it would make a marvellous
       standalone module for XML processing.
   
   
  @@ -60,7 +60,7 @@
   
       There are cases when the error messages aren't all that good. These need
       to be addressed. A good example is AxKit::XSP::Util that apparently
  -    doesn't warn properly when it fails to grab content, as well as 
  +    doesn't warn properly when it fails to grab content, as well as
       XML::LibXML that happily blows up when it's fed an empty string.
   
   
  @@ -80,14 +80,14 @@
   
     . New providers
   
  -    New plugin providers would surely help. A good example could be a 
  +    New plugin providers would surely help. A good example could be a
       provider that uses an XML DB on the backend.
   
   
     . More control on the interaction between the configuration and PIs
   
       Some would like it to be possible to use both the configuration and PIs
  -    simultaneously, either by having the possibility of ignoring PIs 
  +    simultaneously, either by having the possibility of ignoring PIs
       completely, or by allowing one to append/prepend/insert the PIs into the
       style list.
   
  @@ -107,6 +107,12 @@
     
     . Make Taint safe
   
  -    I believe AxKit doesn't run under PerlTaintCheck. This needs fixed.
  +    I believe AxKit doesn't run under PerlTaintCheck. This needs to be fixed.
   
   
  +  . i18n support
  +
  +    AxKit should provide a global policy for xml:lang support. The way it is now,
  +    a user must either do processing of that element himself or rely on a particular
  +	module's implementation. Moreover, in XSP difficulties can arise. Having a
  +	global xml:lang policy would make multi-language support easier.