PHP Colouring without the open tag

PHP Colouring without the open tag

[emacstheviking]

[-- Attachment #1: Type: text/plain, Size: 1241 bytes --]

Hi,

I am currently on a documentation binge and using Pandoc but I have just 
found that it will not apply syntax colouring to sections:

~~~~{.php}
function foo() {
}
~~~~

but only if the section is entered as:

~~~~{.php}
<?php
function foo() {
}
~~~~

I am using a preprocessor I wrote to generate the final Pandoc and 
automatically adding the open tag into the final file for Pandoc to 
transmogrify into HTML and PDF formats. The preprocessor allows me to slice 
bits of "real" files into the output so that the documentation is linked 
with the code as it changes... kind of LP but in reverse.

Is there a way that I can make it do this without too much trouble or 
should I just use "C" mode instead maybe?

Thanks,
Sean Charles.


-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To unsubscribe from this group, send email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msg/pandoc-discuss/-/IVlZW2b7AUQJ.
For more options, visit https://groups.google.com/groups/opt_out.



[-- Attachment #2: Type: text/html, Size: 1720 bytes --]

Re: PHP Colouring without the open tag

[John MacFarlane]

The highlighting is done by the highlighting-kate library, which
derives Haskell parsers from Kate editor syntax description
files.  My guess is that the Kate syntax file for PHP expects
the '<$php'.  If you get the source for highlighting-kate, you'll
see instructions for modifying syntax descriptions and recompiling
the library.  You could try that (and then you'll have to make
sure you compile pandoc against the modified version of
highlighting-kate).  Let me know if you run into difficulties.

+++ emacstheviking [Dec 19 12 07:44 ]:
>    Hi,
> 
>    I am currently on a documentation binge and using Pandoc but I have
>    just found that it will not apply syntax colouring to sections:
> 
>    ~~~~{.php}
> 
>    function foo() {
> 
>    }
> 
>    ~~~~
> 
>    but only if the section is entered as:
> 
>    ~~~~{.php}
>    <?php
>    function foo() {
>    }
>    ~~~~
> 
>    I am using a preprocessor I wrote to generate the final Pandoc and
>    automatically adding the open tag into the final file for Pandoc to
>    transmogrify into HTML and PDF formats. The preprocessor allows me to
>    slice bits of "real" files into the output so that the documentation is
>    linked with the code as it changes... kind of LP but in reverse.
> 
>    Is there a way that I can make it do this without too much trouble or
>    should I just use "C" mode instead maybe?
> 
>    Thanks,
> 
>    Sean Charles.
> 
>    --
>    You received this message because you are subscribed to the Google
>    Groups "pandoc-discuss" group.
>    To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>    To unsubscribe from this group, send email to
>    pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>    To view this discussion on the web visit
>    [1]https://groups.google.com/d/msg/pandoc-discuss/-/IVlZW2b7AUQJ.
>    For more options, visit [2]https://groups.google.com/groups/opt_out.
> 
> References
> 
>    1. https://groups.google.com/d/msg/pandoc-discuss/-/IVlZW2b7AUQJ
>    2. https://groups.google.com/groups/opt_out

Re: PHP Colouring without the open tag

[John MacFarlane]

PS.  The php.xml file contains

      <context name="start" lineEndContext="#stay" attribute="Normal Text">
        <RegExpr context="phpsource" attribute="Keyword" String="&lt;\?(?:=|php)?" insensitive="true" />
        <StringDetect attribute="Keyword" context="#pop" String="?&gt;" />
      </context>
      <context name="phpsource" attribute="PHP Text" lineEndContext="#stay">

I think it would work just to remove the "start" context, so that "phpsource"
is the first context.  Then

    make prep

to regenerate the parsers.  You can then 'cabal install' to install the library,
or, if you're building the dev version of pandoc using the recommended Makefile,
go to the pandoc directory and 'cabal-dev add-source /PATH/TO/highlighting-kate',
then 'cabal-dev install --reinstall --force-reinstalls highlighting-kate',
then 'make install'.


+++ emacstheviking [Dec 19 12 07:44 ]:
>    Hi,
> 
>    I am currently on a documentation binge and using Pandoc but I have
>    just found that it will not apply syntax colouring to sections:
> 
>    ~~~~{.php}
> 
>    function foo() {
> 
>    }
> 
>    ~~~~
> 
>    but only if the section is entered as:
> 
>    ~~~~{.php}
>    <?php
>    function foo() {
>    }
>    ~~~~
> 
>    I am using a preprocessor I wrote to generate the final Pandoc and
>    automatically adding the open tag into the final file for Pandoc to
>    transmogrify into HTML and PDF formats. The preprocessor allows me to
>    slice bits of "real" files into the output so that the documentation is
>    linked with the code as it changes... kind of LP but in reverse.
> 
>    Is there a way that I can make it do this without too much trouble or
>    should I just use "C" mode instead maybe?
> 
>    Thanks,
> 
>    Sean Charles.
> 
>    --
>    You received this message because you are subscribed to the Google
>    Groups "pandoc-discuss" group.
>    To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>    To unsubscribe from this group, send email to
>    pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>    To view this discussion on the web visit
>    [1]https://groups.google.com/d/msg/pandoc-discuss/-/IVlZW2b7AUQJ.
>    For more options, visit [2]https://groups.google.com/groups/opt_out.
> 
> References
> 
>    1. https://groups.google.com/d/msg/pandoc-discuss/-/IVlZW2b7AUQJ
>    2. https://groups.google.com/groups/opt_out

Re: PHP Colouring without the open tag

[Vinai Kopp]

[-- Attachment #1: Type: text/plain, Size: 2224 bytes --]

Hi,

also trying to syntax highlight PHP code without an opening <?php tag. Do I 
need to rebuild pandoc after rebuilding the highlighting-kate parsers?

I've rebuilt the parsers using 

    runghc ParseSyntaxFiles.hs xml

and then cabal installed highlighting-kate from the source dir, which gave 
me:

    highlighting-kate-0.5.5 (reinstall) changes: filepath-1.3.0.1 added
    Warning: Note that reinstalls are always dangerous. Continuing anyway...
    Configuring highlighting-kate-0.5.5...
    Building highlighting-kate-0.5.5...
    Installed highlighting-kate-0.5.5


So far pandoc isn't picking up any changes, so now I'm wondering: do I have 
to rebuild pandoc, too, to pick up the changes? I'm just fumbling along 
since I'm afraid I don't know Haskell.

Thanks!

On Wednesday, December 19, 2012 4:44:53 PM UTC+1, emacstheviking wrote:
>
> Hi,
>
> I am currently on a documentation binge and using Pandoc but I have just 
> found that it will not apply syntax colouring to sections:
>
> ~~~~{.php}
> function foo() {
> }
> ~~~~
>
> but only if the section is entered as:
>
> ~~~~{.php}
> <?php
> function foo() {
> }
> ~~~~
>
> I am using a preprocessor I wrote to generate the final Pandoc and 
> automatically adding the open tag into the final file for Pandoc to 
> transmogrify into HTML and PDF formats. The preprocessor allows me to slice 
> bits of "real" files into the output so that the documentation is linked 
> with the code as it changes... kind of LP but in reverse.
>
> Is there a way that I can make it do this without too much trouble or 
> should I just use "C" mode instead maybe?
>
> Thanks,
> Sean Charles.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/4f8547e1-562d-462a-a82b-048609b5870a%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[-- Attachment #2: Type: text/html, Size: 3153 bytes --]

Re: PHP Colouring without the open tag

[John MacFarlane]

+++ Vinai Kopp [Oct 04 13 16:07 ]:
>    Hi,
>    also trying to syntax highlight PHP code without an opening <?php tag.
>    Do I need to rebuild pandoc after rebuilding the highlighting-kate
>    parsers?
>    I've rebuilt the parsers using
>        runghc ParseSyntaxFiles.hs xml
>    and then cabal installed highlighting-kate from the source dir, which
>    gave me:
>        highlighting-kate-0.5.5 (reinstall) changes: filepath-1.3.0.1 added
>        Warning: Note that reinstalls are always dangerous. Continuing
>    anyway...
>        Configuring highlighting-kate-0.5.5...
>        Building highlighting-kate-0.5.5...
>        Installed highlighting-kate-0.5.5
>    So far pandoc isn't picking up any changes, so now I'm wondering: do I
>    have to rebuild pandoc, too, to pick up the changes? I'm just fumbling
>    along since I'm afraid I don't know Haskell.

Exactly, you have to rebuild pandoc too.  By default, ghc statically links
libraries into binaries, so the old version of highlighting-kate is
still linked into your pandoc.

John

Re: PHP Colouring without the open tag

[Vinai Kopp]

[-- Attachment #1: Type: text/plain, Size: 2029 bytes --]

Thank you John, it works great now! Wonderful!

If someone else stumbles over this thread: one thing to note is that the 
rebuilt pandoc is installed in $HOME/.cabal/bin. Put that in your $PATH 
before /usr/local/bin and you are all set.

Vinai

On Saturday, October 5, 2013 2:12:49 AM UTC+2, fiddlosopher wrote:
>
> +++ Vinai Kopp [Oct 04 13 16:07 ]: 
> >    Hi, 
> >    also trying to syntax highlight PHP code without an opening <?php 
> tag. 
> >    Do I need to rebuild pandoc after rebuilding the highlighting-kate 
> >    parsers? 
> >    I've rebuilt the parsers using 
> >        runghc ParseSyntaxFiles.hs xml 
> >    and then cabal installed highlighting-kate from the source dir, which 
> >    gave me: 
> >        highlighting-kate-0.5.5 (reinstall) changes: filepath-1.3.0.1 
> added 
> >        Warning: Note that reinstalls are always dangerous. Continuing 
> >    anyway... 
> >        Configuring highlighting-kate-0.5.5... 
> >        Building highlighting-kate-0.5.5... 
> >        Installed highlighting-kate-0.5.5 
> >    So far pandoc isn't picking up any changes, so now I'm wondering: do 
> I 
> >    have to rebuild pandoc, too, to pick up the changes? I'm just 
> fumbling 
> >    along since I'm afraid I don't know Haskell. 
>
> Exactly, you have to rebuild pandoc too.  By default, ghc statically links 
> libraries into binaries, so the old version of highlighting-kate is 
> still linked into your pandoc. 
>
> John 
>

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/e5133bcf-d965-442c-bdc5-9429260aeeb9%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[-- Attachment #2: Type: text/html, Size: 2795 bytes --]

Re: PHP Colouring without the open tag

[Oscar Merida]

[-- Attachment #1: Type: text/plain, Size: 1626 bytes --]

On a related note, I found that pygments supports php without the opening 
brace via a "startinline" option. Is there a way to set that and pass it to 
the pygments per code block?

On Wednesday, December 19, 2012 10:44:53 AM UTC-5, emacstheviking wrote:
>
> Hi,
>
> I am currently on a documentation binge and using Pandoc but I have just 
> found that it will not apply syntax colouring to sections:
>
> ~~~~{.php}
> function foo() {
> }
> ~~~~
>
> but only if the section is entered as:
>
> ~~~~{.php}
> <?php
> function foo() {
> }
> ~~~~
>
> I am using a preprocessor I wrote to generate the final Pandoc and 
> automatically adding the open tag into the final file for Pandoc to 
> transmogrify into HTML and PDF formats. The preprocessor allows me to slice 
> bits of "real" files into the output so that the documentation is linked 
> with the code as it changes... kind of LP but in reverse.
>
> Is there a way that I can make it do this without too much trouble or 
> should I just use "C" mode instead maybe?
>
> Thanks,
> Sean Charles.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/f5a37ef6-f58a-419b-8a17-4e321097268a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #2: Type: text/html, Size: 2401 bytes --]

Re: PHP Colouring without the open tag

[Vinai Kopp]

[-- Attachment #1: Type: text/plain, Size: 2695 bytes --]

Pulling up this old thread:
just built highlighting-kate-0.5.8.2 and pandoc-1.12.5 from source again to 
get the updates to the epub writer.
The problem is, pandoc no longer picks up the modified syntax declaration 
from the kate library, even though it does pick up the new version there:

% pandoc --version
pandoc 1.12.5
Compiled with texmath 0.6.6.3, highlighting-kate 0.5.8.2.

The only change to the current highlighting-kate HEAD is that the first 
context is commented out in xml/php.xml.

      <!-- Remove start context to enable php highlighting without <?*
      <context name="start" lineEndContext="#stay" attribute="Normal Text">
        <RegExpr context="phpsource" attribute="Keyword" 
String="&lt;\?(?:=|php)?" insensitive="true" />
        <StringDetect attribute="Keyword" context="#pop" String="?&gt;" />
      </context>
      -->

Any pointer what might be wrong?

Thank you very much,
Vinai



On Saturday, October 5, 2013 2:12:49 AM UTC+2, fiddlosopher wrote:
>
> +++ Vinai Kopp [Oct 04 13 16:07 ]: 
> >    Hi, 
> >    also trying to syntax highlight PHP code without an opening <?php 
> tag. 
> >    Do I need to rebuild pandoc after rebuilding the highlighting-kate 
> >    parsers? 
> >    I've rebuilt the parsers using 
> >        runghc ParseSyntaxFiles.hs xml 
> >    and then cabal installed highlighting-kate from the source dir, which 
> >    gave me: 
> >        highlighting-kate-0.5.5 (reinstall) changes: filepath-1.3.0.1 
> added 
> >        Warning: Note that reinstalls are always dangerous. Continuing 
> >    anyway... 
> >        Configuring highlighting-kate-0.5.5... 
> >        Building highlighting-kate-0.5.5... 
> >        Installed highlighting-kate-0.5.5 
> >    So far pandoc isn't picking up any changes, so now I'm wondering: do 
> I 
> >    have to rebuild pandoc, too, to pick up the changes? I'm just 
> fumbling 
> >    along since I'm afraid I don't know Haskell. 
>
> Exactly, you have to rebuild pandoc too.  By default, ghc statically links 
> libraries into binaries, so the old version of highlighting-kate is 
> still linked into your pandoc. 
>
> John 
>

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/d32d1037-b6d7-4450-a6b5-adb9c1e6f43f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #2: Type: text/html, Size: 3954 bytes --]

Re: PHP Colouring without the open tag

[Vinai Kopp]

[-- Attachment #1: Type: text/plain, Size: 3010 bytes --]

Fixed by adding a filetype suffix *.php to xml/php.xml and a cabal install 
-fexecutable --force in highlighting-kate and pandoc.

Sorry for the noise ;)

Vinai

On Monday, June 16, 2014 3:02:49 PM UTC+2, Vinai Kopp wrote:
>
> Pulling up this old thread:
> just built highlighting-kate-0.5.8.2 and pandoc-1.12.5 from source again 
> to get the updates to the epub writer.
> The problem is, pandoc no longer picks up the modified syntax declaration 
> from the kate library, even though it does pick up the new version there:
>
> % pandoc --version
> pandoc 1.12.5
> Compiled with texmath 0.6.6.3, highlighting-kate 0.5.8.2.
>
> The only change to the current highlighting-kate HEAD is that the first 
> context is commented out in xml/php.xml.
>
>       <!-- Remove start context to enable php highlighting without <?*
>       <context name="start" lineEndContext="#stay" attribute="Normal Text">
>         <RegExpr context="phpsource" attribute="Keyword" 
> String="&lt;\?(?:=|php)?" insensitive="true" />
>         <StringDetect attribute="Keyword" context="#pop" String="?&gt;" />
>       </context>
>       -->
>
> Any pointer what might be wrong?
>
> Thank you very much,
> Vinai
>
>
>
> On Saturday, October 5, 2013 2:12:49 AM UTC+2, fiddlosopher wrote:
>>
>> +++ Vinai Kopp [Oct 04 13 16:07 ]: 
>> >    Hi, 
>> >    also trying to syntax highlight PHP code without an opening <?php 
>> tag. 
>> >    Do I need to rebuild pandoc after rebuilding the highlighting-kate 
>> >    parsers? 
>> >    I've rebuilt the parsers using 
>> >        runghc ParseSyntaxFiles.hs xml 
>> >    and then cabal installed highlighting-kate from the source dir, 
>> which 
>> >    gave me: 
>> >        highlighting-kate-0.5.5 (reinstall) changes: filepath-1.3.0.1 
>> added 
>> >        Warning: Note that reinstalls are always dangerous. Continuing 
>> >    anyway... 
>> >        Configuring highlighting-kate-0.5.5... 
>> >        Building highlighting-kate-0.5.5... 
>> >        Installed highlighting-kate-0.5.5 
>> >    So far pandoc isn't picking up any changes, so now I'm wondering: do 
>> I 
>> >    have to rebuild pandoc, too, to pick up the changes? I'm just 
>> fumbling 
>> >    along since I'm afraid I don't know Haskell. 
>>
>> Exactly, you have to rebuild pandoc too.  By default, ghc statically 
>> links 
>> libraries into binaries, so the old version of highlighting-kate is 
>> still linked into your pandoc. 
>>
>> John 
>>
>

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/ad664243-2c1f-4da5-9b2a-a46424c1d1a9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #2: Type: text/html, Size: 4334 bytes --]