Re: [Gimp-developer] Yes, you can help even if you can't code

2002-05-05 Thread Ayose

On Sat, May 04, 2002 at 10:20:25PM +0200, Daniel Egger wrote:
> > I love sablotron. It is fast and very easy to use. Also, it has almost
> > every feature of the XSLT standar.
> 
> I see, how long would it take to transform into HTML compared to Jade?

sablotron is very fast, look this:



  $ wc -l enlaces.xml gimp.xsl 
  544 enlaces.xml
  400 gimp.xsl
  944 total
  $ time sabcmd gimp.xsl enlaces.xml > /dev/null 

  real  0m0.542s
  user  0m0.540s
  sys   0m0.000s



And with jade:



  $ wc -l gimp1.sgml 
  460 gimp1.sgml
  $ time db2html gimp1.sgml > /dev/null 

  real  0m5.465s
  user  0m4.810s
  sys   0m0.290s



In gimp.es.gnome.org, we have a lot of XMLs files which are transformed
to HTML or PHP using sablotron, and it takes a few time to complete the
process.

> 
> > When you "XSLT files" you must say "XSLT file". Unlike DocBook, with
> > XSLT we only will be able to produce one file, instead of one by
> > .
>  
> > Anyway, it will be easy :)
> 
> So we cannot slice the HTML output into several files? That's sort of a
> problem, really. It took quite some time to figure out how to get Jade
> to do that and still releases are a pain in the neck because there's a
> lot which has do be done manually still.

Well, this is a problem if you want all text in a few files, but slice
the content in a lot of files makes easier transforming to HTML, or
other format. Moreover, it will be easier to keep and write :)

BTW, another solution could be use the XSLT to make intermediates files
and, with a script (perl, python...), create the definitives files. That
is: we have one XML, using XSLT we transform it in a pre-HTML (without
headers), and with the script we split it in severals files and add to
it the headers (both HTML and content headers).

-- 
Ayose Cazorla León
Debian GNU/Linux - setepo
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer



Re: [Gimp-developer] Yes, you can help even if you can't code.

2002-05-04 Thread Ayose

On Sat, May 04, 2002 at 06:55:56PM +0200, Sven Neumann wrote:
> Hi,
> 
> Ayose <[EMAIL PROTECTED]> writes:
> 
> > > we will most likely need at least one XLST that extracts a much
> > > simpler format to be used in the About dialog.
> > 
> > How "simpler"? Something like
> > 
> >  name, author (email), comments
> 
> all we need are simple list of names. Or do we want email addresses in
> the about dialog and the AUTHORS file? I think not. The transformation
> wouldn't be a real XSLT since what we need as output format is not
> actually XML. I'd like to generate the plain-text file AUTHORS as well
> as the header file app/gui/authors.h from the XML file.

Wait a moment, please. Who says that XSLT only works with XML?
With XSLT you can transform a XML file in everything: a plain-text,
HTML, a new XML or even in C source. You only need put
 in the top-level.

http://www.w3.org/TR/xslt.html#section-Text-Output-Method

> 
> Commenting on your proposal, I'd say that it probably makes sense to
> organize the XML file by persons because we need more than only
> plug-ins.

So I was wrong

> We also want to list core developers, tool authors, help
> writers, web masters, screen designers, just everyone who contributed
> to The GIMP.

Well, imaging you want to know only his/her name and email, and put a
comment about he/she

The XML:


 
  the name
  
  email
  A little comment
 

 


For every person will be a  entry. And, for instance, if you want
to get a list like

name1, work1
name2, work2
name3, work3
[...]

The XSLT will be




http://www.w3.org/1999/XSL/Transform";>



 
  ,
  

 





There are a lot of chars, but the code is simple. :)

Of course, with the same XML you can get a more detailed list about
people.

-- 
Ayose Cazorla León
Debian GNU/Linux - setepo
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer



Re: [Gimp-developer] Yes, you can help even if you can't code.

2002-05-04 Thread Ayose

On Sat, May 04, 2002 at 06:02:44PM +0200, Daniel Egger wrote:
> 
> gimp-help is written in DocBook/SGML 

It should be DockBook/XML :)

> which is converted to HTML to be
> suitable for online-browsing and the help-browser plugin for GIMP. There
> are HTML and PS/PDF DSSSL stylesheets which can be used to produce
> either the HTML or some (buttugly) PS/PDF file; also we have an
> experimental DocBook->LaTeX converter written in python by me which
> tends to produce much better PDF output.

Yes, I have seen it, but I think that it is better XSLT instead of
python, because XSLT is more easy and it was designed for this kind of
jobs :-). However, XSLT could be insufficient if the LaTeX generated is
very complex. The loops and conditionals in XSLT are very basics, and
variables and parameters are limited.

> 
> The DocBook source is written such that the conversion to XML is merely
> changing the DTD to an XML one; in short: it is already supposed to be
> valid XML. It just hadn't been done so far because the tools were not
> mature and fast enough last time I looked but if they were now
> 
> So what we need is:
> - A featurerich (and possibly FAST!) XSLT processor

I love sablotron. It is fast and very easy to use. Also, it has almost
every feature of the XSLT standar.

> - XSLT files and CSS stylesheets to produce XHTML which looks nice in
>   nowadays webbrowsers

When you "XSLT files" you must say "XSLT file". Unlike DocBook, with
XSLT we only will be able to produce one file, instead of one by
.

Anyway, it will be easy :)

Well. If you want, look my work in http://gimp.es.gnome.org (spanish).
The tutorials (http://gimp.es.gnome.org/manuales.php) are written in a
new XML vocabulary. For instance, the XML file
http://www.es.gnome.org/cgi-bin/cvsweb/web-xml/gimp.es.gnome.org/manuales/ilustracion/index.xml?rev=1.3&content-type=text/x-cvsweb-markup&cvsroot=GNOME
will generate http://gimp.es.gnome.org/manuales/ilustracion/ using the
XSLT
http://www.es.gnome.org/cgi-bin/cvsweb/web-xml/gimp.es.gnome.org/gimp.xsl?rev=1.36&content-type=text/x-cvsweb-markup&cvsroot=GNOME


> - XSLT files which produce output which is grokkable by the (new?)
>   helpbrowser plugin; That means we either need simple HTML files for
>   something like the current plugin or some other (new?) simple
>   fileformat which allows for additional features which also need to be
>   defined. This has to be discussed with the person(s) who will code
>   that (and that certainly won't be me).

So we need two XSLT files

> 
> This need a lot of planning and someone with your experience can
> possibly bring in some thoughts which would be really appreciated.
> 

Of course :). If I'm useful for GIMP I will work here. What do you need?

-- 
Ayose Cazorla León
Debian GNU/Linux - setepo
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer



Re: [Gimp-developer] Yes, you can help even if you can't code.

2002-05-04 Thread Ayose

On Sat, May 04, 2002 at 03:51:05PM +0200, Daniel Egger wrote:
> Am Sam, 2002-05-04 um 15.41 schrieb Ayose:
> 
> > If you need help with a XSLT I will help you pleased :-)
> 
> Actually if you have experience in that area it would be nice if 
> you could help out with the gimp-help project.

I know well the XSLT specification, and I have written a lot of lines of
XSLT ;)

Where is info about gimp-help? In http://www.gimp.org/mailing_list.html
there is no list for it :/, but I have downloaded the gimp-help module
for CVS. What can I do?, look at bugs.gimp.org? ;)



-- 
Ayose Cazorla León
Debian GNU/Linux - setepo
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer



Re: [Gimp-developer] Yes, you can help even if you can't code.

2002-05-04 Thread Ayose

On Sat, May 04, 2002 at 03:48:20PM +0200, Sven Neumann wrote:
> Hi,
> 
> Ayose <[EMAIL PROTECTED]> writes:
> 
> > 
> >  AlienMap
> >  
> >Daniel Cotting
> >[EMAIL PROTECTED]
> >http://www.mygale.org/~cotting
> >  
> >  
> >   
> >  
> >  
> >74.0
> >only C files counted
> >  
> >  
> > 
> 
> would it make sense to organize the file by persons instead of
> plug-ins? I have no strong feelings either way but I think it should
> be considered at least.

By persons? No... With that format the plugins are described inside
, and every plugin is led by , so the file is organized
by plug-ins. Where are you seeing that the organize is by persons?

My english is not very good, so if I didn't explain it correctly,
please, notice me :)

> 
> > If you need help with a XSLT I will help you pleased :-)
> 
> we will most likely need at least one XLST that extracts a much
> simpler format to be used in the About dialog.

How "simpler"? Something like

 name, author (email), comments

-- 
Ayose Cazorla León
Debian GNU/Linux - setepo
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer



Re: [Gimp-developer] Yes, you can help even if you can't code.

2002-05-04 Thread Ayose

On Sat, May 04, 2002 at 01:31:27PM +0200, Sven Neumann wrote:
> Hi,
> 
> just in case that anyone out there feels bored and useless, here's a
> list of things you can do to help us with GIMP-1.3 even if you can't
> (or don't want to) code. The items appear in no particular order.
> 
> 
>  (2) There are some files that list contributors and plug-in
>  maintainers (namely the files PLUGIN_MAINTAINERS and
>  tools/contributors). I'd like to keep this information in one XML
>  file that is then used for several purposes: To extract info to
>  display in the about dialog and to handle maintainance of
>  plug-ins and bug-reports. The XML approach would have several
>  advantages. It allows to specify an encoding, so we could use
>  UTF-8 to be able to show contributor names in the way they are
>  written natively. We can add all sort of meta information like
>  email address, bugzilla account, CVS account and what parts of
>  the code the specific person has contributed to or maintains.
>  I'd welcome if someone could sit down and come up with a proposal
>  how such an XML file could be organized. You don't need to write
>  a DTD, an example would do.

The PLUGIN_MAINTAINERS has this

---
NAME   : AlienMap
AUTHOR : Daniel Cotting ([EMAIL PROTECTED], http://www.mygale.org/~cotting)
MAINTAINER : 
SIZE   :  74.0 kB  in  1 file  (only C files counted)
COMMENT: 
---

That could be


 AlienMap
 
   Daniel Cotting
   [EMAIL PROTECTED]
   http://www.mygale.org/~cotting
 
 
  
 
 
   74.0
   only C files counted
 
 



If you need help with a XSLT I will help you pleased :-)

-- 
Ayose Cazorla León
Debian GNU/Linux - setepo
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer