Rodent of Unusual Size | 1 Feb 05:51 2007
Picon

[STATUS] (httpd-docs-2.0) Wed Jan 31 23:51:11 2007

Apache HTTP Server 2.0 Documentation Status File.
Last modified: $Date: 2004-11-21 09:35:21 -0500 (Sun, 21 Nov 2004) $

For more information on how to contribute to the Apache Documentation
Project, please see http://httpd.apache.org/docs-project/

This document contains only documentation issues related to 2.0 alone.
For general documentation issues, or those that relate both to 2.0 and
to future versions, please see the same file in httpd-2.0 HEAD.
Joshua Slive | 3 Feb 22:35 2007
Picon

Re: [Httpd Wiki] Update of "Recipes/CanonicalHostNames" by slive

On 1/30/07, Vincent Bray <noodlet <at> gmail.com> wrote:

> The change I made was a result of a user in #apache getting confused
> about the default vhost part. He already had a default vhost (debian
> config) and didn't want to edit it to redirect non-canonical hostnames
> for a single vhost. This makes sense when you apply this config
> pattern to multiple hostname combinations. Here's the conversation, up
> to you if you want to remove the default vhost comment.

I've tried to clarify it.  But I think it is important to mention the
default host issue, because it should be considered a "best practice"
to canonicalize requests for this host.  Otherwise, requests coming in
using the IP address or other non-handled names wind up being dealt
with improperly.

Joshua.
Rodent of Unusual Size | 8 Feb 05:52 2007
Picon

[STATUS] (httpd-docs-2.0) Wed Feb 7 23:52:32 2007

Apache HTTP Server 2.0 Documentation Status File.
Last modified: $Date: 2004-11-21 09:35:21 -0500 (Sun, 21 Nov 2004) $

For more information on how to contribute to the Apache Documentation
Project, please see http://httpd.apache.org/docs-project/

This document contains only documentation issues related to 2.0 alone.
For general documentation issues, or those that relate both to 2.0 and
to future versions, please see the same file in httpd-2.0 HEAD.
Sander Temme | 13 Feb 02:04 2007
Picon

Can I include HTML entities in XML source?

Folks,

I am working on some documentation for mod_ftp, and am using the  
httpd manual format.  I'm running into the following small problem: I  
would like to include HTML entities into the documents, like &mdash;  
&lsquo; and &rsquo;.  While XML documents containing these characters  
build fine, they make Firefox' parser crap out with an error like so:

XML Parsing Error: undefined entity
Location: file:///home/sctemme/asf/httpd/trunk/docs/manual/ftp/ 
ftp_tls.xml
Line Number 64, Column 6:

4217 &mdash; Securing FTP with TLS</a></seealso>
-----^

Any way I can define these entities?  Having Firefox barf on them  
makes it harder to proof the documents.

Oh, don't go looking for that doc in that location: it's a symlink  
from my mod_ftp checkout.

Thanks,

S.

--

-- 
sctemme <at> apache.org            http://www.temme.net/sander/
PGP FP: 51B4 8727 466A 0BC3 69F4  B7B8 B2BE BC40 1529 24AF

(Continue reading)

Vinko Vrsalovic | 13 Feb 07:37 2007
Picon

Re: Can I include HTML entities in XML source?

XML Parsing Error: undefined entity
Location: file:///home/sctemme/asf/httpd/trunk/docs/manual/ftp/
ftp_tls.xml
Line Number 64, Column 6:

4217 &mdash; Securing FTP with TLS</a></seealso>
-----^
 
Sander,
 
you must use the numbered entity. mdash's numbered entity is &#8212;
 
You can check the list here:
http://yost.com/computers/htmlchars/html40charsbynumber.html
 

HTH,
V.
André Malo | 13 Feb 11:50 2007
Picon

Re: Can I include HTML entities in XML source?

* Sander Temme wrote: 

> I am working on some documentation for mod_ftp, and am using the
> httpd manual format.  I'm running into the following small problem: I
> would like to include HTML entities into the documents, like &mdash;
> &lsquo; and &rsquo;.  While XML documents containing these characters
> build fine, they make Firefox' parser crap out with an error like so:
>
> XML Parsing Error: undefined entity
> Location: file:///home/sctemme/asf/httpd/trunk/docs/manual/ftp/
> ftp_tls.xml
> Line Number 64, Column 6:
>
> 4217 &mdash; Securing FTP with TLS</a></seealso>
> -----^
>
> Any way I can define these entities?  Having Firefox barf on them
> makes it harder to proof the documents.

That's a firefox problem (doesn't use DTD files, which are not chrome'd).
If you're running the transformation, HTML entities are accepted.

nd
Rodent of Unusual Size | 15 Feb 05:52 2007
Picon

[STATUS] (httpd-docs-2.0) Wed Feb 14 23:52:44 2007

Apache HTTP Server 2.0 Documentation Status File.
Last modified: $Date: 2004-11-21 09:35:21 -0500 (Sun, 21 Nov 2004) $

For more information on how to contribute to the Apache Documentation
Project, please see http://httpd.apache.org/docs-project/

This document contains only documentation issues related to 2.0 alone.
For general documentation issues, or those that relate both to 2.0 and
to future versions, please see the same file in httpd-2.0 HEAD.
Rodent of Unusual Size | 22 Feb 05:52 2007
Picon

[STATUS] (httpd-docs-2.0) Wed Feb 21 23:52:32 2007

Apache HTTP Server 2.0 Documentation Status File.
Last modified: $Date: 2004-11-21 09:35:21 -0500 (Sun, 21 Nov 2004) $

For more information on how to contribute to the Apache Documentation
Project, please see http://httpd.apache.org/docs-project/

This document contains only documentation issues related to 2.0 alone.
For general documentation issues, or those that relate both to 2.0 and
to future versions, please see the same file in httpd-2.0 HEAD.
Sander Temme | 23 Feb 05:16 2007
Picon

What to do with changed generated files?

Folks,

What would you consider Best Practice when one svn ups the manual  
tree, touches one file, builds and then finds a bunch of generated  
files changed because of an XML source change inherited from the svn up?

1) Commit inadvertedly changed generated files with ones own change?
2) Commit own change, its generated files, and then commit inadvertedly
    changed generated files under separate cover?
3) Commit just ones own change and its generated files?
4) Commit just ones own change and leave it to someone else to generate
    the HTML?

Enlightment appreciated.

S. (Abort, Retry, Ignore?)

--

-- 
sander <at> temme.net              http://www.temme.net/sander/
PGP FP: 51B4 8727 466A 0BC3 69F4  B7B8 B2BE BC40 1529 24AF

Attachment (smime.p7s): application/pkcs7-signature, 3295 bytes
Mads Toftum | 23 Feb 07:50 2007
Picon

Re: What to do with changed generated files?

On Thu, Feb 22, 2007 at 11:16:25PM -0500, Sander Temme wrote:
> 1) Commit inadvertedly changed generated files with ones own change?

Not the best way - it gets a bit messy that way.

> 2) Commit own change, its generated files, and then commit inadvertedly
>    changed generated files under separate cover?

I think that would be the preferred option.

> 3) Commit just ones own change and its generated files?

That's ok too if you're unsure about what else is being picked up or
worried that there might be an error in it.

> 4) Commit just ones own change and leave it to someone else to generate
>    the HTML?
> 
That does happen at times when people have trouble generating the html,
but with Andre not going through and picking up everyone elses mess as
often as he used to, that isn't fabulous.

vh

Mads Toftum
--

-- 
http://soulfood.dk

Gmane