Bug #47201 [Com]: use an external highlight source-code engine

From: Date: Fri, 27 Aug 2010 16:18:14 +0000
Subject: Bug #47201 [Com]: use an external highlight source-code engine
References: 1  Groups: php.doc.bugs 
Request: Send a blank email to doc-bugs+get-4942@lists.php.net to get a copy of this message
Edit report at http://bugs.php.net/bug.php?id=47201&edit=1

 ID:                 47201
 Comment by:         cweiske@php.net
 Reported by:        pear at laurent-laville dot org
 Summary:            use an external highlight source-code engine
 Status:             Closed
 Type:               Bug
 Package:            Doc Build problem
 PHP Version:        0.4.3
 Assigned To:        cweiske
 Block user comment: N

 New Comment:

http://doc.php.net/phd/docs/


Previous Comments:
------------------------------------------------------------------------
[2010-08-27 18:17:28] cweiske@php.net

fixed in svn.

------------------------------------------------------------------------
[2010-08-27 11:07:37] cweiske@php.net

Automatic comment from SVN on behalf of cweiske
Revision: http://svn.php.net/viewvc/?view=revision&revision=302846
Log: Write about writing own source code highlighters. This fixes bug
#47201: use an external highlight source-code engine

------------------------------------------------------------------------
[2009-01-26 12:40:32] cweiske@php.net

documentation needed

------------------------------------------------------------------------
[2009-01-25 20:02:10] cweiske@php.net

Fixed in version 0.4.4. You can specify an own highlighting class with
--highlighter/-h

See a dummy geshi highlighter:
http://tmp.cweiske.de/PhD_Highlighter_Geshi.phps

One would put it into PhD/Highlighter/Geshi.php, so that it is in the
include path, and specify "-h PhD_Highlighter_Geshi" to phd on cmdline.

------------------------------------------------------------------------
[2009-01-24 09:20:07] pear at laurent-laville dot org

Hannes,

I've looked inside PhD code (themes handling), and I don't see how to
do.

Perharps you can explain me more. 
What do you mean by "using my own programlisting/CDATA functions" ?

Related to my external guide, link [3], the corresponding docbook source
code in peardoc repository is 

http://cvs.php.net/viewvc.cgi/peardoc/en/package/html/html-quickform-advmultiselect/firstform.xml?view=log

As you can see, line 33 and +, I used only a standard way

<programlisting role="php">
 <![CDATA[
<?php

...

?>
 ]]>
</programlisting>

------------------------------------------------------------------------


The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at

    http://bugs.php.net/bug.php?id=47201


-- 
Edit this bug report at http://bugs.php.net/bug.php?id=47201&edit=1


Thread (7 messages)

« previous php.doc.bugs (#4942) next »