Re: transformation help

Hi.

I remember there have been two versions of Sun J2SE, one, U.S. 
English only and the other, all languages. I did not checked 
what's the difference at all, but I guess that's the reason. 
The all languages version will solve your problem.  

Andr

Malo <nd <at> perlig.de> wrote:
> * Joshua Slive wrote:
> > I'm having some problems with the html transformations (and I might have
> > accidentally committed some of that garbage just now).  I keep getting:
> > 
> > -generate.html:
> >      [xslt] Processing D:\ap\httpd-2.0\docs\manual\mpm.xml to D:\ap\httpd-2.0\docs\manual\mpm.html.en
> >      [xslt] Loading stylesheet D:\ap\httpd-2.0\docs\manual\style\manual.en.xsl
> >      [xslt] file:/D:/ap/httpd-2.0/docs/manual/style/xsl/common.xsl:348:71:
> > Warning! Can not load requested doc: ISO2022JP
> 
> Seems, your system has problems with other encodings than iso-8859-1. I
> don't get such errors. Did you modify your java installation in some way?

---Hiroaki Kawai

Re: cvs commit: httpd-2.0/docs/manual/mod mod_ssl.xml quickreference.xml

* Joshua Slive wrote:

> On Sun, 22 Jun 2003, André Malo wrote:
>> Hmm. If we consider the sitemap containing references to all files, it
>> should contain that link, too. For example, in the CHM toc, I think, it
>> would be still useful.
> 
> A philisophical question: is a sitemap a list of all "files" or a list of
> all "content"?  I don't know, but I think I favor the latter.

philosophical - may be. Technical - we need one document that maintains a
list of all files for transformation and autogeneration purposes. The
sitemap doesn't seem to be the worst choice 

>> This problem should be gone anyway, if/when we automate the FAQ category
>> entries. Then we would do something similar to the modules (a &faq; entity
>> or so) and every transformation can do with this, what it wants. What do you
>> think?
> 
> Sure.  I'm having a hard time imagining exactly what this will look like,
> but it sounds like the right direction.

Once I have more time, I'll take it (if nobody else does).

nd
--

-- 
Gefunden auf einer "Webdesigner"-Seite:
        > Programmierung in HTML, XML, WML, CGI, FLASH <

# André Malo # http://www.perlig.de/ #

Re: transformation help

> I remember there have been two versions of Sun J2SE, one, U.S.
> English only and the other, all languages. I did not checked
> what's the difference at all, but I guess that's the reason.
> The all languages version will solve your problem. 

> > Seems, your system has problems with other encodings than iso-8859-1. I
> > don't get such errors. Did you modify your java installation in some way?

Must be something like that.  I installed a new full-version java and
things seem to be working now.

And thanks, Andre, for cleaning up my transformation mess.

Joshua.

Re: fr translating newcomer -> french xsl

Joshua Slive said:
>
> Welcome!
>
> Yes, the existing french files in the tree predate the xml conversion.
> They should be replaced by xml.
>
> I don't think a new DTD is necessary, but yes, you will need to create a
> manual/style/manual.fr.xsl and manual/style/lang/fr.xml
>
>

Good.
Here is the XSL stuff, to start with :
manual/style/manual.fr.xsl and manual/style/lang/fr.xml

Is that okay to you guys?

Vincent

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe <at> httpd.apache.org
For additional commands, e-mail: docs-help <at> httpd.apache.org

Re: fr translating newcomer -> french xsl

On Tue, 1 Jul 2003, Vincent Deffontaines wrote:
> Good.
> Here is the XSL stuff, to start with :
> manual/style/manual.fr.xsl and manual/style/lang/fr.xml
>
> Is that okay to you guys?

Looks good to me.  One other little issue is that we need another fluent
french speaker to have a look and confirm that the translation is
accurate.  We used to have some here on the list, but I'm not sure if they
are around any more.

[My french is good enough to understand the general point, but not good
enough to judge the quality.]

Joshua.

cvs commit: httpd-docs-1.3/htdocs/manual/misc FAQ-D.html

slive       2003/07/01 15:42:14

  Modified:    htdocs/manual/misc FAQ-D.html
  Log:
  Remove dead links to Aventail.

  PR: 20662.

  Revision  Changes    Path
  1.21      +3 -12     httpd-docs-1.3/htdocs/manual/misc/FAQ-D.html

  Index: FAQ-D.html
  ===================================================================
  RCS file: /home/cvs/httpd-docs-1.3/htdocs/manual/misc/FAQ-D.html,v
  retrieving revision 1.20
  retrieving revision 1.21
  diff -u -d -b -u -r1.20 -r1.21
  --- FAQ-D.html	7 Jun 2003 06:01:40 -0000	1.20
  +++ FAQ-D.html	1 Jul 2003 22:42:13 -0000	1.21
   <at>  <at>  -449,18 +449,9  <at>  <at> 
           <p>The shim is not unloaded when Aventail Connect is shut
           down. Once observed, the problem persists until the shim is
           either explicitly unloaded or the machine is rebooted.
  -        Instructions for temporarily removing the Aventail Connect
  -        V3.x shim can be found here: "<a
  -        href="http://support.aventail.com/akb/article00386.html">How
  -        to Remove Aventail Connect v3.x from the LSP Order for
  -        Testing Purposes</a>."</p>
  -
  -        <p>Another potential solution (not tested) is to add

manual/bind.xml french translation

Here is a translation into french for manual/bind.xml (starting
alphabetically seems to be a good way to forget nothing  )

For some reason I am unable to open xml files under mozilla (1.3.1) or
galeon (1.3.5). It gets mozilla engine to freeze (bug report in progress).
Maybe someone has a clue about this? By the way validator.w3.org does not
like it when "content type is application/octet-stream" ; does anyone know
about another online validator that would deal with it?

By the way, I have not found tools to convert xml stuff to html. Looks
like the build subdir is not included in the snapshot. So I'll let someone
of this list convert it, or explain me how to proceed if there is
somethign I didn't catch 

Vincent

--

-- 
Freedom is slavery.
Ignorance is strength.
War is peace.
                -- George Orwell

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe <at> httpd.apache.org
For additional commands, e-mail: docs-help <at> httpd.apache.org

Testing the new mailinglists

Test of the new mailinglists.

Carsten

[TRANSLATION] index.xml filter.xml

Hello again

Two translated and reviewed files. I've decided that next time I will send
patch for index.xml.ru with each new translated file - so all those docs'
menu items that are translated will lead to translated docs.

As I can see - link to 'ru' (available languages) will be available if I
insert them to 'meta' file. Am I correct?

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe <at> httpd.apache.org
For additional commands, e-mail: docs-help <at> httpd.apache.org

Re: cvs commit: httpd-2.0/docs/manual/mod mod_ssl.xml quickreference.xml

>> A philisophical question: is a sitemap a list of all "files" or a list of
>> all "content"?  I don't know, but I think I favor the latter.

> philosophical - may be. Technical - we need one document that maintains a
> list of all files for transformation and autogeneration purposes. The
> sitemap doesn't seem to be the worst choice 

I tend to tell a sitemap a table of content, not a list of all physical
files. But both needs can be fullfilled with one document, when we think
of the generated sitemap as a subset of the files list. An attribute
"hide from sitemap" would help.
For this special problem ...

>>> This problem should be gone anyway, if/when we automate the FAQ category
>>> entries. Then we would do something similar to the modules (a &faq; entity
>>> or so) and every transformation can do with this, what it wants. What do you
>>> think?
>>
>> Sure.  I'm having a hard time imagining exactly what this will look like,
>> but it sounds like the right direction.

... a new faq will do it. Sounds good.

Kess