DokuTeXit is a DokuWiki plugin that generates a PDF file from the wiki data. It depends on LaTeX which is mandatory to generate the PDF document. This plugin is still experimental: Feedback and criticism are appreciated. Contact me at Danjer@doudouke.org.

The plugin content is :

• a LaTeX rendering class (latex.php),
• a dokuwiki specific wrapper (syntax.php),
• a configuration/admin plugin (admin.php),
• a renderer plugin (renderer.php),
• some class tools.

The goal of this plugin is to give dokuwiki users the ability to get a decent printable version of their documents. Some examples:

• If you are a student, when you get to write a paper, thanks to dokuwiki you can write it from everywhere and get a good looking printable version.
• Allow several people to work on the same document, to make it alive, at anytime you can with a click get a printable version to show your work to your boss or customers.

• http://danjer.doudouke.org/dokutexit.tar.gz
• http://danjer.doudouke.org/dokutexit.zip

Creating PDF based on HTML is not really good and the simplest and most important reason is because their purpose and usage are not the same. Why should we do a chaining conversion ?

During the chaining conversion process we will lose most of the formatting information. Let’s then keep DokuWiki Format as our root Format.

DokuTeXit is a good way to export dokuwiki format to PDF.

I see a lot's peoples do some tests with specifics characters languages like Russian, German, Finish, Hungarian. I can't do a latex configuration to support all languages, but if someone tweak one in dokuTeXit configuration, please send it to me. I'll include it the plugin package. I design this plugins to have one latex config by language.

In other words : Find the good latex tweaks and DokuTexit can work with every language.

DokuTeXit PlayGround

You can also use this playground to show me up some bugs.

Works pretty well :

• Headings
• Bulleted lists
• Ordered lists
• Bold
• Italics
• Underline
• Superscript
• Subscript
• Deleted
• Short tables (with heading and align)
• Footnotes
• Inline and separate-line teletype text
• Code blocks
• Typography
• Images
• Syntax highlighting
• Externals Links
• Smileys
• Interwiki icons
• Acronyms (as Footnotes)

May have strange layout :

• Internals Links
• Images Links
• Very long/big tables
• Quoting (It’s really sucks)

Not supported :

• Line break in tables
• Footnotes in tables
• Animated Smileys
• Embedded HTML and PHP
• Windows platforms (It may work)

You can freely set :

• Language (babel options)
• Papersize A4/Letter
• New Typography like ‘LaTeX’ (see PDF version)
• Your own LaTeX commands
• Header and footer
• Document style and options

The main goal is to have a nice looking printable version of a DokuWiki page. LaTeX is a good choice.

To avoid lots of parsing troubles and because dokuwiki is very well thought, LaTeX renderer is directly plugged into the dokuwiki framework.

To obtain good flexibilty, LaTeX generation is split into 5 parts :

• Begin/Header
• Command
• Document
• DokuWiki LaTeX Renderer mode
• Footer

This part controls everything before ‘\begin{document}‘. You can add LaTeX packages there. You may choose your babel options or change the document class (Default options are two-side printing and A4 format).

The Command part controls LaTeX commands which are used by TeXit to generate the LaTeX file. You can add LaTeX newcommands that you can use in your document. LaTeX command generated by the LaTeX renderer can be overloaded. So you can change headers and footers, color, font styles... etc.

The Document part controls everything just after ‘\begin{document} You can choose the layout of the begin of your document. You can define where you want to have the table of contents appearing.

LaTeX code is generated from dokuwiki format.

The Footer part controls the end of the LaTeX file. You may want to define the table of contents here. The last line of this field MUST BE ‘\end{document}’

Alternatively, see the installation notes by Frisco Rose under http://wiki.splitbrain.org/wiki:debian_notes

• Of course you need DokuWiki installed and running.
• DokuTeXit needs a working installation of LaTeX, Ghostscript.
• If you are on a Debian box,

  # apt-get install gs-common imagemagick texlive-lang-all texlive-latex-extra

  should be sufficient to install the required packages

  • Recommended: install also tetex-extra
  • Note: Make sure latex-ucs is installed. It’s not really a standard package. We need it because DokuWiki uses UTF-8 to store its data, so you also have to enable latex to handle UTF-8.
• If you are on a Ubuntu box,

  # apt-get install tetex-base texlive-latex-recommended tetex-extra imagemagick gs-common

  • Note: texlive-latex-recommended provide latex-ucs to enable latex to handle UTF-8.
• If you are on a gentoo 2006.1 box, add USE=”... tetex unicode jpeg jpep2k tiff wmf png gs” into file /etc/make.conf and run

  sudo emerge tetex latex-unicode imagemagick ghostscript

according to Sebastian Pipping, you must use this now:

sudo emerge -av texlive-latex imagemagick ghostscript

• If you are using CentOs

  #sudo yum install apt tetex latex-unicode imagemagick ghostscript

• within a web browser, load dokuwiki, follow the links admin > manage plugins, then download from URL:
  • http://danjer.doudouke.org/dokutexit.tar.gz
  • http://danjer.doudouke.org/dokutexit.zip
• at present, it may be necessary to make a little modification to the syntax file which requires command-line access to the dokuwiki server. See below.

  $>  cd dokuwiki
  $>  mkdir lib/plugins/dokutexit

• download http://danjer.doudouke.org/dokutexit.tar.gz

  $> cd /tmp
  $> wget http://danjer.doudouke.org/dokutexit.tar.gz

  $> tar zxvf dokutexit.tar.gz

  $> cp -R dokutexit ${YOUR_DOKU_ROOT}/lib/plugins
  $> chmod +x ${YOUR_DOKU_ROOT}/lib/plugins/dokutexit
  $> rm -rf dokutexit

You may need french quotation mark fguill if you don’t use french in babel’s options. You can find this package here :
http://lcr.math.ist.utl.pt/tetex/texmf/tex/latex/fguill/fguill.sty

I you can disable this dependency by removing theses lines in DokuTeXit entities configurations :

<<	{\guillemotleft}
>>	{\guillemotright}

Make sure you also remove the include in the DokuTexIt begin/header.

As an alternative to the elusive fguill.sty file, you could use use the package aeguill which is installed with the package texlive-lang-french. Simply replace the /usepackage{fguill} by /usepackage{aeguill} and leave the following section as is:

<<	{\guillemotleft}
>>	{\guillemotright}

First action is to go in DokuTeXit admin plugin and save configuration.

To activate TeXit plugins you just have to add this at the beginning of your document :

<texit info>
author=MySelf
title=MyTitle
</texit>

Once you saved the page, you will see that button :

Click on it, to begin generation process. If it’s successful you will see this button :

You can add some LaTeX commands any where in you document like this :

<texit>
\newpage
</texit>

You can also use this syntax in your wiki document :

title=My title
author=Myself
subject=subject
keywords=Me and my life
recurse=on

DokuTeXit supports export commands (Renderer Plugins) with Dokuwiki 2007-06-26. So you can call dokutexit with this kind of url :

http://url..?...do=export_dokutexit
http://url..?...do=export_dokutexit&dokutexit_type=zip
http://url..?...do=export_dokutexit&dokutexit_type=pdf

This feature is usefull to do an export to pdf button

Image layout with LaTeX could quickly turn into a nightmare. Once you tried to do that with latex you will really appreciate any WYSIWYG editors. To make it easier with dokutexit I put some rules to generate something close to a web browser layout :

1. An image with a title or centered is not wrapped with the text,
2. An image without a title and not centered is wrapped with text.

Other rendering plugins can be used along with DokuTeXit if they support LaTeX rendering mode. I have modified Dokuwiki graphviz plugin in that way.

Basically, it’s easier to add latex mode into a syntax plugin than

First find the render function in the syntax.php, it should look like this :

function render($mode, &$renderer, $data) {
  if ($mode == 'xhtml' /* &&... */) {
    //Build xhtml
    // ...
    $renderer->doc .= $xhtml_stuff;
    return true;
  }
  return false;
}

Then you just have to add the latex mode :

function render($mode, &$renderer, $data) {
  if ($mode == 'xhtml' /* &&... */) {
    //Build xhtml
    // ...
    $renderer->doc .= $xhtml_stuff;
    return true;
  }
  if ($mode == 'latex' /* &&... */) {
    //Build latex
    // ...
    $renderer->doc .= $latex_stuff;
    return true;
  }
  return false;
}

:tech:dokutexit_graphviz_syntax.php.txt

Install this plugin with the plugin:plugin manager. The download link is:
→ http://danjer.doudouke.org/graphviz.tar.gz
→ http://danjer.doudouke.org/graphviz.zip

Use this in your graphviz for better rendering :

bgcolor=transparent

To use LaTeX formula in you dokuwiki and your PDF document you must do the following :

grab this plugin from : http://wiki.erazor-zone.de/doku.php?id=wiki:projects:php:dokuwiki:plugins:latex

and patch it like this :

*** lib/plugin/latex/syntax.php.org      Fri Nov 23 11:10:15 2007
--- lib/plugin/latex/syntax.php  Fri Nov 23 13:38:34 2007
***************
*** 99,104 ****
--- 99,110 ----
          }
          return true;
        }
+       if($mode == 'latex' && strlen($data[0]) > 1) {
+        $renderer->doc .= "$";
+        $renderer->doc .= $data[0];
+        $renderer->doc .= "$\n";
+          return true;
+        }
        return false;
      }

This patch already exist in darcs version.

• within a web browser, load dokuwiki, follow the links admin > manage plugins, then download from URL:
  • http://danjer.doudouke.org/latex.tar.gz
  • http://danjer.doudouke.org/latex.zip

Please keep in your mind that LaTeX plugins is more permissive than dokutexit. Dokutexit will stop at any error and it’s intentional. But I’ll try to make this work for basic cases.

Remember that using ‘\\’ (linebreak command) in formula is BAD, especially if you have the LaTeX Error: There’s no line here to end.

You can add texit tag to add some formating stuff (pretty hugly in that case) :

<texit>
\begin{figure}[h]
\begin{center}
</texit>

<latex>
\frac{3}{4 \pi}   \sqrt{4 \cdot x^2   12} \newline
\lim_{n \to \infty}
\sum_{k=1}^n \frac{1}{k^2} = \frac{\pi^2}{6} \newline
\it{f}(x) = \frac{1}{\sqrt{x} x^2} \newline
e^{i \pi} + 1 = 0
</latex>

<texit>
\end{center}
\caption{Wonderful math formula}
\end{figure}
</texit>

Or you can escape latex math mode to make better layout :

<latex>
$
\begin{eqnarray*}
2x^2 + 3(x-1)(x-2)&=&2x^2 + 3(x^2-3x+2)\\
&=& 2x^2 + 3x^2 - 9x + 6\\
&=& 5x^2 - 9x + 6
\end{eqnarray*}
$
</latex>

In that case ‘\\’ means end of array/tabular.

I make this patch to add latex mode support inside the include plugin. You must use the last version of dokutexit to use this patch.

*** syntax.php.org      Mon Nov 26 11:37:07 2007
--- syntax.php  Tue Nov 27 10:30:36 2007
***************
*** 104,111 ****
      } elseif ($mode == 'metadata'){
        if (!$flg_macro) $renderer->meta['relation']['haspart'][$id] = $exists;
        $include->pages = array(); // clear filechain - important!
! 
        return true;
      }
   
      return false;  
--- 104,132 ----
      } elseif ($mode == 'metadata'){
        if (!$flg_macro) $renderer->meta['relation']['haspart'][$id] = $exists;
        $include->pages = array(); // clear filechain - important!
!       
        return true;
+     } elseif ($mode == 'latex') {
+       $latex_info = $renderer->get_info();
+       $include->setLevel($renderer->get_clevel());
+       $include->renderer =& $renderer;
+ 
+       if ($texit =& plugin_load('texitrender', 'dokutexit')) {
+       $include->ins = p_cached_instructions($include->page['file']);
+ 
+       // show only a given section?
+       if ($include->page['section'] && $include->page['exists']) 
+         $include->_getSection();          
+ 
+       // convert relative links
+       $include->_convertInstructions();
+ 
+       // get latex content
+       $latex = $texit->p_render('latex', $include->ins, $latex_info);
+       $renderer->doc .= $latex;
+       } else {
+       msg("Can't load Dokutexit from include plugins\n", -1);
+       }
+       return true;
      }
   
      return false;  

• within a web browser, load dokuwiki, follow the links admin > manage plugins, then download from URL:
  • http://danjer.doudouke.org/include.tar.gz
  • http://danjer.doudouke.org/include.zip

This is a small patch to add latex mode for color plugin. http://wiki.ioslo.net/dokuwiki/color

*** syntax.php.org      Wed Dec  5 14:49:14 2007
--- syntax.php  Wed Dec  5 14:43:37 2007
***************
*** 69,77 ****
        $renderer->doc .= '<span style="color: '.$data[1].'">'.$data[0].'</span>';
        return true;
      }
      return false;
    }
   
  }
-  
-  
--- 69,94 ----
        $renderer->doc .= '<span style="color: '.$data[1].'">'.$data[0].'</span>';
        return true;
      }
+     if($mode == 'latex' && strlen(trim($data[0])) > 0) {
+       if ($texit =& plugin_load('texitrender', 'dokutexit')) {
+       if (substr($data[1], 0, 1) == '#') {
+         $rgb[0] = substr($data[1], 1, 2); 
+         $rgb[1] = substr($data[1], 3, 2); 
+         $rgb[2] = substr($data[1], 5, 2); 
+         for ($i = 0; i < count($rgb); $i++) {
+           $rgb[$i] = bcdiv(hexdec($rgb[$i]), 255, 2);
+         }
+         $renderer->putcmd('textcolor[rgb]{'. $rgb[0] 
+                           . ',' . $rgb[1] 
+                           . ',' . $rgb[2] 
+                           . '}{' . $data[0] . '}');
+       } else {
+         $renderer->putcmd('textcolor{'. $data[1] . '}{' . $data[0] . '}');
+       }
+       }
+       return true;
+     }
      return false;
    }
   
  }

The structure of the $data array has changed in newer versions of Dokuwiki/Color.

So Philipp Neuser modified this hack for new Versions:

        if($mode == 'latex' && strlen(trim($data[1][0])) > 0) {
           if ($texit =& plugin_load('texitrender', 'dokutexit')) {
              $data_tex = substr($data[1][0],6,strlen($data[1][0])-7);
              list($state, $match) = $data;
                  switch ($state) {
                  case DOKU_LEXER_ENTER :
                     list($color, $background) = $match;
                     $color = substr($color,6,strlen($color)-7);
                     $is_rgb = ""; # no = "", yes = "[rgb]"
                     if (substr($color, 0, 1) == '#') {
                       $is_rgb = "[rgb]";
                       $rgb[0] = substr($color, 1, 2);
                       $rgb[1] = substr($color, 3, 2);
                       $rgb[2] = substr($color, 5, 2);
                       for ($i = 0; i < count($rgb); i++) {
                        $rgb[$i] = bcdiv(hexdec($rgb[$i]), 255, 2);
                       }
                       $color = $rgb[0] . ',' . $rgb[1] . ',' . $rgb[2];
                    }
                    $renderer->doc .= "\\textcolor".$is_rgb."{".$color."}{";
                    break;
                  case DOKU_LEXER_UNMATCHED :  $renderer->doc .=
$renderer->_xmlEntities($match)."}"; break;
                  #case DOKU_LEXER_EXIT :       $renderer->doc .= "}";
break;
                }
                return true;
               }
               return true;
        }

• within a web browser, load dokuwiki, follow the links admin > manage plugins, then download from URL:
  • Old Version of color plugin
    • http://danjer.doudouke.org/color.tar.gz
    • http://danjer.doudouke.org/color.zip
  • New Version of color plugin
    • http://danjer.doudouke.org/color-new.tar.gz
    • http://danjer.doudouke.org/color-new.zip

Patch below also accepts multi-line colored output

       if($mode == 'latex') {
          if ($texit =& plugin_load('texitrender', 'dokutexit')) {
             $data_tex = substr($data[1][0],6,strlen($data[1][0])-7);
              list($state, $match) = $data;
                 switch ($state) {
                 case DOKU_LEXER_ENTER :
                    list($color, $background) = $match;
                    $color = substr($color,6,strlen($color)-7);
                    $is_rgb = ""; // no = "", yes = "[rgb]"
                    if (substr($color, 0, 1) == '#') {
                      $is_rgb = "[rgb]";
                      $rgb[0] = substr($color, 1, 2);
                      $rgb[1] = substr($color, 3, 2);
                      $rgb[2] = substr($color, 5, 2);
                      $count = count($rgb) - 1;
                      while ($count >= 0) {
                       $rgb[$count] = bcdiv(base_convert($rgb[$count], 16, 10), 255, 2);
                       $count--;
                      }
                      $color = $rgb[0] . ',' . $rgb[1] . ',' . $rgb[2];
                   }
                   $renderer->doc .= "\\textcolor".$is_rgb."{".$color."}{";
                   break;

                 case DOKU_LEXER_UNMATCHED :  $match_without_newlines=str_replace(array("\r\n","\n","\r"),"\\\\",$match); $renderer->doc .= $renderer->_xmlEntities($match_without_newlines); break;
                 case DOKU_LEXER_EXIT :       $renderer->doc .= "}"; break;
               }
               return true;
           }
           return true;
       }

This is a small patch to add latex mode for note plugin. http://wiki.splitbrain.org/plugin:note

This patch was submitted by Aurelien Bompard

--- syntax.php.org      2007-12-06 14:06:08.088635605 +0100
+++ syntax.php  2007-12-06 14:25:05.835425955 +0100
@@ -123,7 +123,43 @@
           }
           return true;
         }
-        
+        if($mode == 'latex'){
+         if ($texit =& plugin_load('texitrender', 'dokutexit')) {
+           list($state, $data) = $indata;
+           switch ($state) {
+           case DOKU_LEXER_ENTER: // opening     
+             $renderer->putcmdnl("begin{figure}[h]");
+             $renderer->putcmdnl("centering");
+             $renderer->putcmdnl("fbox{");
+             $icon = substr($data, 4);
+             if ($icon == "classic") {
+               $icon = "note";
+             }
+             $img = new TexItImage(DOKU_PLUGIN."note/images/".$icon.".png");
+             if (! $img->is_error) {
+               $ps_filename = $img->get_output_filename();
+               if ($ps_filename != '') {
+                 $renderer->putcmdnl("begin{minipage}{1.3cm}");
+                 $renderer->putcmd("includegraphics[width=1cm,height=1cm]{".$ps_filename."}");
+                 $renderer->putcmdnl("end{minipage}");
+               }
+             }
+             $renderer->putcmdnl("begin{minipage}{.75\\linewidth}");
+             break;
+           case DOKU_LEXER_UNMATCHED: // content
+             $renderer->putent($data);
+             break;
+           case DOKU_LEXER_EXIT: // closing
+             $renderer->putcmdnl("end{minipage}");
+             $renderer->put("}\n");
+             $renderer->putcmdnl("end{figure}");
+             break;
+           }
+         } else {
+           msg("Can't load Dokutexit from note plugin\n", -1);
+         }
+         return true;
+        }
         // unsupported $mode
         return false;
     } 

• within a web browser, load dokuwiki, follow the links admin > manage plugins, then download from URL:
  • http://danjer.doudouke.org/note.tar.gz
  • http://danjer.doudouke.org/note.zip

This is a patch to the syntax.php file for the charter plugin to allow it to include these graphs within the create pdf document.

*** syntax.php	2008-12-22 06:36:13.000000000 +1000
--- syntax.php	2009-06-15 09:48:05.000000000 +1000
***************
*** 92,101 ****
--- 92,118 ----
          	$renderer->doc .= '<img src="'.ml($mediaid, 'cache=nocache').'" alt="'.$flags['title'].'" width="'.$flags['size']['width'].'" height="'.$flags['size']['height'].'" class="media'.$flags['align'].'" />';
          	return true;
          }
+         if($mode == 'latex') {
+           $renderer->doc .= "\\begin{figure}[h]\n";
+           $renderer->doc .= "\t\\begin{center}\n";
+           $renderer->doc .= "\t\t\\includegraphics[width=12cm]{";
+           $renderer->doc .= createPS(mediaFN($mediaid));
+           $renderer->doc .= "}\n";
+           $renderer->doc .= "\t\\end{center}\n";
+           $renderer->doc .= "\\end{figure}\n";
+           return true;
+         }
  
          // unsupported $mode
          return false;
      }
  }
  
+ function createPS($filename)
+ {
+   $psfname = substr($filename,0,-4).".ps";
+   exec("convert $filename $psfname");
+   return $psfname;
+ }
+ 
  //Setup VIM: ex: et ts=4 enc=utf-8 :
\ No newline at end of file

This should be all that needs to be done. I have made the image a fixed width of 12cm and it’s position centered. Change as you like.

Submitted by Matthew Nelson-White

• X ⇒ Done
• H ⇒ Half done
• B ⇒ Buggy...
• T ⇒ Thinking about that
• W ⇒ Work in progress

I am thinking to write another plugins to export dokuwiki format to openoffice, and another one to make slides.

• Gijs van Gemert <g*dot*v*dot*gemert[at]inter*dot*nl*dot*net> for dutch translation.
• Stefan Pampel <stefan*dot*pampel[at]polyformal*dot*de> for german translation.
• Quinten Krijger <qkrijger[at]gmail*dot*com> for comments and windows alpha testing.
• Julius for tables reflexions.
• Rolphin for being a loser.
• Leprechaun for spending time reading over my english
• Philipp Neuser <pneuser[at]physik*dot*fu-berlin*dot*de> for Dokuwiki Color Patch

Please feel free to add your site.

• I included Drye changes as he described below. But we loose pdf clickables links when using dvipdfm instead of dvipdf.
• Is there anyone who can provide me access to a windows (IIS and/or Apache) server with dokuwiki administrative rights, miktex and imagemagick ?
• I am looking for people to translate this plugins in other languages ... Anyone ?
• Is there anyone who wants to make an howto ‘DokuTeXit & MikTeX Windows install’ ?

• A small patch to correct this error :

! LaTeX Error: File `' not found.

See the LaTeX manual or LaTeX Companion for explanation.
Type  H   for immediate help.
 ...

l.113 ...ssible via \includegraphics[height=1em]{}

\href{http://wiki.splitbra...

?

This happened on interwiki link when imagemagick do not work.

• Use $conf[’im_convert’] to set imagemagick path.
• Correct some bugs with quotting and hline.

• Correct a caption bug

! Missing $ inserted.

                $
l.108 ...tion{:polyformal:stefan.pampel_small.jpg}

?

• Include German’s support, thanks to Stefan Pampel.

• Add latex entities support for title, author, date and backgroundtext

• Add some hook for plugins command and footer part,
• Add a new option : recurse=chapter

• Add Dutch’s support thanks to Gijs van Gemert

• Add Latex Zip sources button
• Add in dokuwiki config manager (You will need the last stable dokuwiki version) :
  1. Enable/Disable Download ZIP
  2. Enable/Disable Download as PDF
  3. Enable/Disable Force Clean up Button
  4. Choose your latex processing mode :
     • latex mode (I recommend this one)
     • pdflatex mode
  5. Set latex path

I am not dead... I just overflow at work.

Danjer

• calling parser ⇒ Little bit faster, but use less memory for big documents.
• backgroundtext options ⇒ as request
• add $lang[’qb_latex’] ⇒ ?!?
• apostrophe support for $conf[’typography’] = ‘2’;
• export_dokutexit renderer plugins...
• small image cache bug

• This patch actually loads the configuration from conf/default.cfg,

thus enabling the use of pdflatex (and other settings) It also fixes a bug when the path exists but is empty.

• Do some latex plugin compatibily

• Modify dokutexit (texitrender interface) for the include plugin

I had to rename class.texitrender.php to texitrender.php. In that way plugin_load can work with dokutexit.

• Adding RSS support syntax

• Fix some bugs with links (interwiki, image).

2008-09-30: I often get the following error message: sh: /net/www/global.bin/\dvipdf: No such file or directory
Don’t know how that backslash gets there...

The plugin mathjax lets you use Latex syntax to write equations, and then generates images with a javascript library. To keep this working with DokuTeXit, you’ll need to remove the following entities from the entities settings:

\	{\textbackslash}
_	\_
$	\$
^	\^{ }

Note that you now can’t use these symbols in the regular text.

Hello, I’m trying to generate PDF files with pages like “nossa_missão” (file data/pages/nossa_miss%C3%A3o.txt) and it isn’t working. The output is:

latex pass 1:
cmdline: /usr/bin/pdflatex /home/turicas/public_html/sol/data/media/texit/tmp/nossa_miss%C3%A3o.tex 2>&1 
ret: 1
This is pdfeTeX, Version 3.141592-1.30.5-2.2 (Web2C 7.5.5)
entering extended mode
! I can't write on file `texput.log'.
Please type another transcript file name:
! Emergency stop
No pages of output.

I tried with other filenames (without accents) and it worked. I’ve tested in terminal:

pdflatex nossa_miss%C3%A3o.txt
pdflatex 'nossa_miss%C3%A3o.txt'
pdflatex "nossa_miss%C3%A3o.txt"

output is the same of dokutexit.

So, I suggest: create a tex file with other name (like a md5sum of the name of page dot tex), so pdflatex can compile without problems, like: $newTexName = md5($pagename).’.tex’; run_latex($newTexName);

I’ve got this problem - using dokuwiki with cyrillics (bulgarian). If an article has a latin name - pdf’s are generated a OK. But if the name is in cyrillic - pdflatex gives up.

latex pass 1:
cmdline: /usr/bin/pdflatex /REPLACED TEXT/data/media/texit/tmp/%D0%B0%D0%BB%D0%B8%D0%B5%D0%BD%D0%B0.tex 2>&1
ret: 1
This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4)
entering extended mode

*
! Emergency stop.
<*> ...mp/%D0%B0%D0%BB%D0%B8%D0%B5%D0%BD%D0%B0.tex

No pages of output.
Transcript written on ?.

Any help or ideas on this?

Boris Jordanov, borj at borj dot org

Looks like there are some bugs when using

recurse=on

and lists deep levels. A deph of 3 works. See DokuTeXit PlayGround for examples.

It’s not really a bug. LaTeX is limited to 4 lists deep levels. You can up to 6 when you combine enumerated and bullet lists See DokuTeXit PlayGround for examples. Danjer 2007/02/01 19:51

Yes, but there is some workaround. One of this is using the listenum package and adding the definition of enumerate and itemize in predocument definitions, like this (in DokuTeXit Begin/Header section):

...
\usepackage{enumitem}
\renewlist{itemize}{itemize}{10}
\setlist[itemize,1]{label=\textbullet, leftmargin=*}
\setlist[itemize,2]{label=\textbullet, leftmargin=*}
\setlist[itemize,3]{label=\textbullet, leftmargin=*}
\setlist[itemize,4]{label=\textbullet, leftmargin=*}
\setlist[itemize,5]{label=\textbullet, leftmargin=*}
\setlist[itemize,6]{label=\textbullet, leftmargin=*}
\setlist[itemize,7]{label=\textbullet, leftmargin=*}
\setlist[itemize,8]{label=\textbullet, leftmargin=*}
\setlist[itemize,9]{label=\textbullet, leftmargin=*}
\setlist[itemize,10]{label=\textbullet, leftmargin=*}
\renewlist{enumerate}{enumerate}{10}
\setlist[enumerate,1]{label=\roman*, leftmargin=*}
\setlist[enumerate,2]{label=\alph*, leftmargin=*}
\setlist[enumerate,3]{label=\arabic*, leftmargin=*}
\setlist[enumerate,4]{label=\roman*, leftmargin=*}
\setlist[enumerate,5]{label=\alph*, leftmargin=*}
\setlist[enumerate,6]{label=\arabic*, leftmargin=*}
\setlist[enumerate,7]{label=\roman*, leftmargin=*}
\setlist[enumerate,8]{label=\alph*, leftmargin=*}
\setlist[enumerate,9]{label=\arabic*, leftmargin=*}
\setlist[enumerate,10]{label=\roman*, leftmargin=*}

please do not blame me, but I try to get this running on a Windows server (using apache).
I have trouble to get latex running:

latex pass 1:
cmdline: (cd C:\Program Files\xampp\htdocs\dokuwiki\data\media/texit/tmp/zentech/checklists; latex C:\Program Files\xampp\htdocs\dokuwiki\data\media/texit/tmp/zentech/checklists/win_server.tex 2>&1 )
ret: 1
The filename, directory name, or volume label syntax is incorrect.

I think the problem is the “latex” command which is called latex.exe in windows, but I am not sure. Does anyone has this running on a Windows Box?

Thanks Andre

— I got it running successfully on a Windows Box. After I successfully installed MikTex, I modified the Path system variable to include c:\Program Files\MiKTeX 2.5\miktex\bin. Then i had to make some changes in some files:

In \dokuwiki\lib\plugins\dokutexit\class.texitrender.php I modified the pdffromdvi funtion, which now looks like this:

Patch included: 4 Oct 2006

In the same file, i modified the run_latex function to look like this:

Patch included: 4 Oct 2006

I also had to tweak some settings. I had to remove this line, cause miktex didn’t come with a package called fguill

%%\usepackage{fguill} %%Use this package for guillemot[left|right] useless with 

And that’s basically it.

Good luck, Drye

I have got a quite similar problem to the above one, I get the message:

latex pass 1:
cmdline: c:\Program Files\MiKTeX 2.6\miktex\bin/latex E:\Web\dokuwiki\data\media/texit/tmp/pdftest.tex 2>&1 
ret: -1

I am running a windows machine with apache and php5. The newest MikTeX version (2.6) is also installed. I have done all the above modifications without getting a better result, so any help on this problem would be much appreciated.

thanks, kurt

Ok - take everything you see after “cmdline” and run it at a CMD prompt - chances are good you installed MikTex and told it to notify you up updates so it fails when it tries to run the first time.. it’s asking if it can update, and you aren’t there to say yes. Do this, as I said, from a CMD prompt. Update all the packages.

You will still have to deal with that stupid fguill.sty porblem... but I think I found a solution to that in \support\lib\plugins\dokutexit\settings\entities - delete the entries for guillemotleft and guillemotright. I did this and it ended my problem MikTex failing while trying to find that sty file.

Another issue - MikTeX 2.7 just came out Dec 1, 2007. I think that is a big reason I’m having other issues (If I run at the cmd line I can see a whole bunch of MicTex issues when trying to create a page, and on top of that when I try to do a nearly-empty dokuwiki page, it creats a 5 page document.) I’m downloading 2.5 as I type this and I think that will solve a bunch of issues.

-Nathaniel

I just got it running under Windows. However, it doesn’t export images to the pdf at this time. I’m using MikTex 2.7 Complete(takes a while to install). I had issues with the basic install hanging because it was missing a significant number of the packages it required. Missing file errors included: ucs.sty, utf8x.def, moreverb.sty, listings.sty, lastpage.sty, fancyhdr.sty, wasysym.sty, and eso-pic.sty. I didn’t have to modify any of DokuTeXit package. The MikTex 2.7 install (both basic and complete) adds the directory of latex to your system’s path variable, so you shouldn’t have to. However, if you’re getting an error that the command isn’t defined make sure it’s there and that you’ve restarted IIS since having it added to the Path.

If the complete package is too big (1.3GB) for you then install the Basic 2.7 package. During install I used the A4 default size and had set it to ‘no’ when asked about automatic update install/notification. You’ll need to add the following packages using the “Browse Packages” program: listings, unicode,moreverb, lastpage, fancyhdr, wasysym, eso-pic, ms, and wasy.There are plenty more packages you’ll need to get this working depending on the complexity of your content. Check \lang\XX\begin_config.txt for any of hte possible included packages. All I did was run ‘latex XXX.tex’ and let it tell me which files were missing. Then I would filter by filename in the Browse Packages program and install the file. The only time that didn’t quite work perfectly was with package, wasy, since it complained about something other than a missing file.
— jack 2008/03/19 10:53CST

When I run the commands at the command prompt I see several warnings, none of which have stopped the PDF from being created. These warnings are invisible when using the wiki and creating the pdf through that.
Update: I have removed the title,blank, and table of content pages by editing document.cfg in the settings directory. Make sure you read up on latex formatting before doing so. I found this tutorialuseful–it’s written by David R. Wilkins and hosted by the University of Dublin's school of mathematics
— jack 2008/03/17 16:28CST

I was not getting images initially, instead I was seeing text ‘img C:\...whatever_directory..\imagename.jpg’ where the image should be. I went into latex.php and modified the lines that output that code and changed the two parts that weren’t under the error code to grab the image height and width and then submitted it to the latex file:

    $filename = ereg_replace("\\\\","/",$filename);       
    list($x,$y,$img_type,$dim_str)= getImageSize($filename); 
   if($img_type==1 || $img_type==2 || $img_type==3 ) 
     $this->putcmd("includegraphics[bb=0 0 ".($x/2)." ".($y/2)."]{".$filename."}"); 
   else 
      $this->unformatted('img '. $filename); 

I’m not sure why I had to divide by two, but meh–I have the images in my document now..

.gif files are not displayed, however, space is allocated for them and they do appear in the .tex code just like the other image formats (.jpg and .png). I can’t get any .gif’s to display.

Could you please be a bit more precise at which line you made the changes. I’m having the same problem (under Linux) and cannot find the lines that I have to change. – Heiko 2008/12/04

When I use DokuWiki’s table headings with the caret I get errors because the command dokuheadingstyle is not defined. Adding it to the .tex file fixed the error–i made it a bold style, and coupled with the dokuheadingcolor color it’s a bold grey. Make addition in command.cfg in settings folder of dokutexit.
— jack 2008/03/18 14:13CST

I am very short sighted. I should have realized a lovely package like DokuTeXit would have come with a nice little control panel. I hadn’t realized it until I was poking around. From the admin panel you can change all the general pdf output options so long as you know your LaTeX. Thanks for the plugin.
— jack 2008/03/19 16:45CST

Under Linux (Suse 10.1) with standard tetex installation.

Two little changes I have done

1. dokutextit/settings.old renamed in dokutexit/settings
2. one line added in dokutexit/settings/command.cfg :

\newcommand{\dokuheadingstyle}[1]{#1}   % ça mange pas de pain !

Could you describe why you did that ?

Because code generated for arrays contains line like this :

\multicolumn{1}{|l|}{\dokuheadingstyle{\color{dokuheadingcolor} baratin \normalcolor}}& ...

Then without a \dokuheadingstyle definition, latex compiler fails.

This is very strange... This line is present in the default config :

\newcommand{\dokuheadingstyle}[1]{\textbf{#1}}

Could you check in that file : dokutexit/lang/en/command_config.txt if this line is present ?

I’ve got the same trouble as ‘ca mange pas de pain’. latex complains about dokuheadingstyle and I had to add this line into settings/command.cfg. However, I’ve double-checked in dokutexit/lang/en/command_config.txt and it exists. It seems that this file will never be loaded... weird. Maybe, I’ve done something wrong with babel options. I’ve tried in settings/begin.cfg to add line like :

\usepackage[american]{babel} %% Use your own babel language
\usepackage[british]{babel} %% Use your own babel language
\usepackage[english]{babel} %% Use your own babel language

instead of [french], but it doesn’t work either.

— pvincent 2007/07/31 07:04

Et merci beaucoup pour ce plugin, Bernard.

Pas de quoi
Yes, I see this problem yesterday.
Danjer

Hi, I installed this plugin today, I have Dokuwiki 2006-10-08 running on Gentoo linux. Looks to be working well. I think this is a very exciting plugin — thank you very much for writing this! Warren Howard

I am using dokutexit to generate PDF in german language, but there appear some mistakes in the transformation from dokuwiki to latex, which have no affect in other babel settings. This happens only when I use double quotes.
For example "One examlpe" will be rendered in the PDF as Öne example”. How can I change this behaviour?

I propose to enter this changes to the latex.php

 function doublequoteopening() {
    $this->put('\textquotedblleft');
  }
 
  function doublequoteclosing() {
    $this->put('\textquotedblright');
  }

— Christian Moll 2008/09/25 15:15

Did some hacking. Now you can create Umlgraphs by putting some java code in graphviz juml quotes. see the tail of the graphviz dokuwiki page. hm, code formatting works in wiki but texit will break dothebart

About this break : In Latex for syntax highlighting we use listing package witch exist since 1996, but language descriptor is not exactly the same in dokuwiki. ie: bash do not exist in listing package. I copy and paste you example in playground with other language descriptors (c or c++ instead of cpp) and it’s work fine.
Anyway you can make language aliases by adding this line in dokutexit command :

\lstalias{cpp}{C++}

If anyone want make all aliases between geshi and
listing package this could be great.
I am sure that listing package can be tweakable for special layout, but I will remove latex hardcoding in dokutexit for code/code hightlight/file to put in dokutexit config.

I have some troubles with boxes around code... and page break.

— Danjer 2006/11/13 09:48

Wonderful work. Very nice plugin for Dokuwiki. Thanks very much for your work. I had some problem as I mentioned on my blog

Ok, i did some hacking. The button inside of the document was annoying me. It needed to be added on two places:

• class.texitrender.php:render in line 172

    define(PDF_BUTTON_TEXT, $string);

    return ""; //return $string;

• If you want to have the pdf button inside the document, let the return intact.
• the other one goes to the theme inside lib/tpl/[yourtheme]/main.php right after the history button:

        <?php tpl_button('history')?>
        <?php echo PDF_BUTTON_TEXT; ?>

this hurts the plugin architecture a bit, but works, and looks more smart (to me) – dothebart

You’re right this button really sucks. When I start this project, I didn’t find a better way to add a button without hacking the theme. Maybe it’s time now to think in another way. I will rewrite texitrenderer to fit better to new dokuwiki version (?do_export=texit), add hook for others plugins and make it more flexible for download button. — Danjer 2006/12/11 09:09

Finally I’ve done it ! Have a look on this — Danjer 2007/07/04 14:45

Hi, I have this message when i try to generate pdf

latex pass 1:
cmdline: latex /home/mypath/public_html/aide/data/media/texit/tmp/accueil.tex 2>&1 
ret: 127
sh: latex: command not found

How to fix that ?

Thanks, Stéphanie

You need to have a full latex installation on your host. Many hosting services do not provide LaTeX, this kind of service can be available only on dedicated servers. Feel free to contact me about this subject.

— Danjer 2007/01/23 09:31

Could also be a php safe_mode issue. Try disabling safe_mode just for testing purpose.

— Frank 2007/02/22 14:02

What i can do for fix this? (I found no installation advice for latex.)

UPDATE: I solved the problem. It is just that the latex path is not set right. Set it to “/usr/tex” in the config.php.

— Jakob 2008/07/15 12:00

On this url http://lcmserv2/lcm/radio/doku.php?id=software_radio:manuel:manuel I try to generate a big PDF (about 100 pages) the first 20 pages will be OK, but after I will have wiki code ! Is it a bug ? Will it have a work around ?

Thanks in advance and sorry for my English.
Stéphane Brunner

Unfortunately, the URL you provide is not accessible. Please provide a new one for furthers investigation. — Danjer 2007/02/09 09:21

It was a plugins problem. In one plugin (for LaTeX rendering) I have something like that :

              $latexRenderer = new texitRender();
              $text = $latexRenderer->p_render_latex_text($data[0]);
              $renderer->doc .= $text; 

I replace it by :

              $text = $renderer->_latexEntities($text);
              $renderer->doc .= $text;

add all will be OK

I was trying to set the background to an empty string and realized that tex was complaining about it. The following change makes the error go away (Starting @ line 415 of class.texitrenderer.php):

Patch included: 4 Jul 2006

Basically, if the background is set to an empty string, we simply skip the ‘\dokubackground’ altogether, rather than generate an empty one.

– Renny Koshy (a grateful dokutexit user!)

Is it possible to change the default background (the URL) with a picture ?

Thanx,

Georges

Autoresponse : I inserted this code after the \begin{document} in the “DokuTeXit Document” section, and placed the Image (here spiral.png) in the /data/media/texit/tmp/folder

\makeatletter
\newcommand\BackgroundPicture[2]{%
  \setlength{\unitlength}{1pt}%
  default \put(0,\strip@pt\paperheight){%
  \parbox[t][\paperheight]{\paperwidth}{%
    \vfill
    \centering\includegraphics[angle=#2]{#1}
    \vfill
}}} %
\makeatother
\AddToShipoutPicture{\BackgroundPicture{spiral.png}{45}}% here or anywhere in text

It works great. :o)

Thank you for this tips — Danjer 2007/06/22 14:50

In order to add a export to PDF button in the toolbar, I did the following things :

• Create a toolbar button (dimension 16×16 pixels) and call it “latex.png” (I resized one from here).
• Copy the button in the correct folder /lib/images/toolbar/
• Edit the inc/toolbar.php file and add this code

        array(
                'type'   => 'insert',
                'title'  => $lang['qb_latex'],
                'icon'   => 'latex.png',
                'insert' => '<texit info> \nauthor= \ntitle= \nsubject= \nkeywords= \nrecurse=on \nbackgroundtext= \n</texit>\n \n',
                ),

• Edit the inc/lang/en/lang.php file and add this line (If you use other language than english just edit the corresponding lang.php):

$lang['qb_latex'] = 'Export to PDF';

TIP : Don’t forget to delete the cache of your browser.

~Martin

You may find interesting renderer_url — Danjer 2007/07/04 14:46

Hello Danjer,

I have just installed the plug-in and was testing it on the latest DokuWiki release (rc-2007-05-24 on Debian, shared hosting, LaTeX is installed); unfortunately, I get the following error displayed on the page I am attempting to export to PDF, right before the blue box where the LaTeX log is displayed:

Warning: getFormat() not implemented in doku_renderer_latex in /pathtomydokuwikiroot/inc/parser/renderer.php on line 46

LaTeX stops and no output is produced. What can I do to solve this? Any help will be greatly appreciated.

Thanking you for the great work,

Enrique.

Hi, I would also like to add that I am seeing this error too Warning: getFormat() not implemented in doku_renderer_latex in /var/www/localhost/htdocs/dokuwiki/inc/parser/renderer.php on line 46. I am using Dokuwiki 2007-06-26. For me the error will be repeated several times, but the PDF generation does not fail.

Regards,

Warren.

• I think the getFormat() was introduced in the new version. I added the following just before the first function in latex.php (in the dokutexit plugin folder) in line 60. Now I don’t get any of those warnings:

Patch included: 4 Jul 2006

• Hi, the above code inserted at around line 58 in my latex.php file has removed the error messages described above. With thanks, Warren.

This function getFormat() was a part of dokuwiki’s parser evolution. Dokutexit and dokuwiki’s renderer are very close together. Sorry for the late... — Danjer 2007/07/04 14:39

example : http://www.linuxpourlesnuls.org/v4/dokuwiki/doku.php?id=tutoriaux:premiers_pas_avec_linux:presentation_lpln

thanks for any suggestions...

Tom

mail: tsly_mdk A yahoo fr

Hi... In your case the origin trouble is there :

[[http://lpln.free.fr/pics/edtm0lh0.png|{{ http://lpln.free.fr/minis/edtm0lh0.png }}]]

Obviously Dokutexit have some trouble with externals images in external link. — Danjer 2007/09/24 16:11

It’s solved in 4 Dec 2007 version — Danjer 2007/12/05 16:00

Texts wrapped by <color> tags aren’t integrated into the document (example : test)

http://wiki.splitbrain.org/plugin:color

Dokutexit add a latex renderer mode to dokuwiki perhaps you can ask to the color plugin maintainer to add a latex mode to this plugin. — Danjer 2007/11/20 11:18

I write a patch for this. — Danjer 2007/12/05 15:47

I have discovered that fguill.sty is not available on my Ubuntu Linux distribution. Despite my best attempts to circumvent the need for it, I cannot overcome the error messages I see about a missing fguill.sty. (I might be able to avoid them if I actually knew how to use LaTex/TeTex).

I scanned my system using

find / -name "*guill*.sty" 

and found aeguill.sty. I thought maybe I would have other ‘guill’ styles installed so I ran:

$ apt-file search aeguill.sty
tetex-src: usr/share/texmf-tetex/source/latex/aeguill/aeguill.sty
texlive-lang-french: usr/share/texmf-texlive/tex/latex/aeguill/aeguill.sty

and it showed that I have an ‘aeguill’ style installed. I substituded this:

\usepackage{aeguill} 

for the fguill statement in my DokuTeXit Begin/Header section. I also changed my language to English:

\usepackage[english]{babel}

and everything is working fine for me. Thanks for a great plugin.

Chris Freyer

Thanks for this useful feedback, I will have a look at it. — Danjer 2007/11/20 11:16

I’ve installed dokutexit (through the plugin manager) and installed all the latex packages mentioned (in Ubuntu). The Generate PDF button on the plugin’s config page does generate a PDF but with the exception of the title page, the PDF is empty. Is there anything else I need to do to get it to work? Unfortunately, my website is internal only for the moment; I want to use dokutexit to generate a PDF file I can distribute. (There is a copy of the website here, but dokutexit won’t work here at all, probably because of the server).

Raja Mukherji

It’s solved... — Danjer 2007/12/05 16:02

Is it possible to allow LaTeX to properly parse symbols from the symbol menu (the one with the Omega icon)? If I insert a sigma from the symbol menu it crashes LaTeX processing completely. The same thing happens on the DokuWiki playground.

I did the same test in the playground but I did’nt see any crashes... — Danjer 2008/01/06 12:51

Interesting - when I generate the same symbols using my Mac they look slightly different than yours and crash the PDF generation. Perhaps something in how DokuWiki deals with symbols? I’ve left the Mac-generated symbols in for now.

It’s seem that unicode translation don’t know about \textalpha or \textanything Ok, I do the following to solve this : Add to the begin part in dokutexit config :

\usepackage{amssymb}
\usepackage{pxfonts}
\usepackage{pifont}

Add theses entities : click here to see them

keep me in touch about this — Danjer 2008/01/07 14:59

I’m the original complainant, and this has completely solved my problem. This could probably be part of the standard configuration of the plugin. Thanks!

The installation on linux systems will not work because path statements contain backslashes (\) instead of forwardslashes (/). Make the following adjustments:

At lines 326 and 334 in the file texitrender.php replace the following code:

$cmdline = $this->_dokutexit_conf['path'] . '\\';

by this code:

$cmdline = $this->_dokutexit_conf['path'] . DIRECTORY_SEPARATOR;

Note: There are several places where path statements are being ‘constructed’. At all of these places the slashes are hardcoded as forwardslashes (/). It would be ‘better’ to replace each of them by the DIRECTORY_SEPARATOR constant.

We are getting an error when trying to generate a PDF using latest version of DokuTeXit with 2008-05-05 version of dokuwiki. All packages were installed on Ubuntu server as documented above. So far it appears to work fine with basic text, but tables such as the following are not working. Do we need to go back to a previous version of dokuwiki to make this work? Is it potentially an issue with the version of LaTeX?

Example

Log

[5]
Chapter 2.
! Undefined control sequence.
\@sharp ->\dokuheadingstyle
                          {\color {dokuheadingcolor} ggg \normalcolor }
l.125 ...olor{dokuheadingcolor} ggg \normalcolor}}
                                                &\multicolumn{1}{l|}{\doku...
?
! Emergency stop.

— C. J 2008/10/09 12:11

The dokuheadingstyle style is missing, searching for dokuheadingstyle I found the following line to add in command.cfg

\newcommand{\dokuheadingstyle}[1]{\textbf{#1}}

— jmlavoie 2009/06/23 10:32

Hi, I did it on a Sid with php5 and I had one trouble: if i put the texlink at the end of the document, the wiki jams up with a php error on rendering the page. If i put it at the start of the document, it works fine. added the hint at that section. Adding two backslashes after the texsection (to do a newline) breakes tex. Ok, I’ve found a bug. Try to convert this. the backdraft is the to backslashes in a table once more.

< texit info>
author=The super duper
title=document
< /texit>

^1^  2  ^ 3   ^
| | foo | bar |
|3| bla | bli \\ blub|

I have the same problem: a linebreak in a table crashes the latex compilation. Any help would be welcome! Thank you. — Wojtek 2010/03/30

When i put this on a Dokuwikipage and try to generate a PDF-Dokument i get the following error. “! LaTeX Error: There’s no line here to end.” I have also tried it in the playground of this site and get the same error. Is this a bug?

Begin of Test
^ Tab1  | Tab2  |  |
| Tab3  | Tab4  |  Tab5 |

\\

\\

End of Test

Thanks in Advance. Friedrich

You’re right about this. I saw that a month ago. Basically you in LaTeX you can’t add a break line on an empty line. So I had to replace the break line \\ by a \vspace or something. The main difficulty is to know if the line is empty. I didn’t find the time to fix it. — Danjer 2007/04/02 19:06

Replace \\ by ~\\ — JPS 2009/05/19 16:09

If I use a large image file that is re-sized and centered in my page (like below). The generated pdf layout will be broken. The image will not be re-sized in the generated file.

{{  :wiki:big_image.png?650  |A big image}}

Also the image will be in-lined in the text, event though it is not in the web-page. Besides that, the pluging works well for me. Very nice !

I am not very proud of image management in dokuTeXit. Image printing/layout is a big problem since the 70’s : a screen is generally around 72dpi maybe 100dpi in some case in the other hand a printer can do 300dpi and much more. This fact affect image layout, so it’s really difficult to have WYSIWYG (What you see is what you get) between dokuwiki web layout and a PDF layout. I didn’t find a way that work in any case.

— Danjer 2007/01/23 09:21

I’ve got the same problem, but I wonder why it works fine when I use CutePDF Writer and print my webpage.

— Stéphanie 2007/01/30 20:11

It’s definitively not the same generating process, with CutePDF Writer you print your webpage from your browser into a file and this file is converted into a PDF. So CutePDF Write do not manage images... The browser handle this part. This is the big difficulty with dokuTeXit, that the image processing (size and postion) is blindly done because LaTeX is supposed to handle this. Besides html do not provide the same layout from a web browser to a another one so you may have different PDF with CutePDF.
Furthermore there’s some layout bug in dokuTeXit with images that I can’t handle, in particular if you put two images like this :

{{img1.png}}
{{img2.png}}

A web browser will put images one above the other or side by side, it’s depend of images size, the browser window size, style sheet... etc. — Danjer 2007/02/12 09:43

I try to do some modifications to the way dokutexit handles images. I have documentation, which contains more images than text. So I manage to change the “wrapfigure” with “figure” and try to put \FloatBarrier just before dokutexit sections to empty the stack. It looks better, but I think that I need as well wrap and not wrap figures... So I wonder on which criteria I may select between wrap and not wrap...

—Denis 2007/02/14 18:22

This is a ugly modification of latex.php : I add a line if ($width > 400) $width = 400; to force a resize of a large image

function mediatops($filename, $title=NULL, $align=NULL, $width=NULL,
                     $height=NULL, $cache=NULL, $linking=NULL) {
    if ((is_null($align) || $align == 'center') && is_null($title)) {
      $this->mediatops_old($filename, $title, $align, $width, $height,
                           $cache, $linking);

...

      $this->putnl($align . "}{0pt}");
      $this->putcmd("includegraphics"); // need config for that                                             
      if ($width > 400) $width = 400;  <-------------------------------------THIS
      if ($width || $height) {
        $this->put("[");

David

In fact it’s not so hugly. After all an A4 page is 210 mm large so an image can’t be larger than (210mm /0.3515 Tex point size) 597.4395 pt. With margins, 400 is a good value. — Danjer 2007/12/04 15:29

When i install my plug in, and i click the button to generate pdf, my explorer works and works for hours without showing anything. What could be the problem? how can i fix it?

Did you have any test url for us, again ? — Danjer 2007/09/04 11:57

Firstable, thank you for this great plugin. Unfortunatly I have a problem with document who have more than one page.

LaTeX Warning: Reference `LastPage' on page 1 undefined on input line 97.
[1]
LaTeX Warning: Reference `LastPage' on page 2 undefined on input line 99.
[2]

Any idea?

Really strange... Did you have any test url for us, again ? — Danjer 2007/09/04 11:57

I would like to thank you for your great work as well. I managed to get the same kind of error messages when I used something like this:

Here we have a footnote((and the footnote has a code part: <code>This will break, right?</code>))

This also breaks youyr playground so it is probably not a matter of server install but of doing insane things with DokuWiki

Thanks again and kind regards
Daniel

Not really a bug, but I have got a slight problem. As I am forced to use a Suse Linux Enterprise Server 10 I have problem with imagemagick, which won´t compile. Does anybody know of any alternatives for imagemagick, that could work for Enterprise Server 10? Or has anybody succeded in compiling imagemagick on that OS? Any help would be appreciated!

— Christian 2007/12/12 10:28

I got a slight problem on a Debian (etch/lenny) system: I don’t get images in the pdf.

The pdf just shows a line like: img /usr/share/dokuwiki/data/media/playground/imagename.png

All packages (see above apt-get command) are installed, dokuwiki works fine out of the box (ok, I had to adjust file size and memory for php).

Some things I had to do for DokuTeXit:
rename settings.old to settings
add \usepackage{supertabular} to settings/begin.cfg
add \newcommand{\dokusupertabularheadbreak}{\small\sl continued from previous page} to settings/command.cfg
add \newcommand{\dokusupertabulartailbreak}{\small\sl continued on next page} to settings/command.cfg

Version of DokuTeXit: downloaded 20/9/2008
all other programs are native Debian (etch or etch’n’half).

Any help would be appreciated!

— Heiko 23/9/2008

I had a similiar problem with RHEL and figured out that I did not install imagemagick. After installing it, it worked — Peter 15/06/2010

imagemagick is installed, problem persists in Debian/squeeze. — Heiko 23/3/2011

this is also happening on ubuntu lucid to me, imagemagick is also installed but problem persists. — gentakojima 23/5/2011

To fix the img /path/to/img.png problem with imagemagick installed: make sure the setting im_convert in DokuWiki is set correctly. DokuTexIt uses the convert=im_convert and also identify which it looks for in the same directory as convert. I have images now! Also, I recommend the pdflatex route for generating PDFs instead of the tex,dvi,ps,pdf route. — Ivan 2/10/2011

Once again (see above), but this time on MacOS 10.4 with a full installation of TeXLive: Clicking the “Generate PDF” button in the Dokutexit Self Test section leads to this output:

 latex pass 1:
 cmdline: latex /MYPATH/dokuwiki/data/media/texit/tmp/wiki/syntax.tex 2>&1 
 ret: 127
 sh: latex: command not found

The system path is set correctly: Calling “latex” at the command prompt in Terminal works.

Any ideas?

Thanks, Jörg

2009-01-30

Is your latex located on /usr/bin? If not, try to set the latex path on the DokuTeXit settings on the DokuWiki settings page (Admin > Configuration Settings) Christian 2009-09-18

It seems that " resolve_mediaid(getNS($ID),$src, $exists);” should be used BEFORE calling mediaFN, around line 1381 in latex.php.

Regards, TG 2010-02-12

I get some bad PDF output which I have no idea how to solve. You can find the resulted PDF here. For example, look the page numbers inside the footer. Header is also invisible. I know that the header has something in it because after changing the page format from a4 to letter, parts of it appeared. Any suggestions? Here are my page related setting:

\documentclass[twoside,letterpaper,10pt]{report}
\usepackage[american]{babel} %% Use your own babel language
\usepackage[top=1cm,bottom=1cm,left=2cm,right=1cm]{geometry}

Update: If I’m using the following settings is working better. Still, there are some big spaces between paragraphs. I guess that the plugin is doing everything possible to spread the text over the pages and keep indivisible things (like tables or code snippets) on the same page.

%%\usepackage[top=1cm,bottom=1cm,left=2cm,right=1cm]{geometry}
\usepackage[margin=2cm]{geometry}

Hellow,

I’m looking for a CMS that provide a platform :

1. to collaborate easily (from 5 to 10 people) on the same document (means good “history” and “recent change” pages)
2. to interact with a .bibtex file for citation.

Is it possible (now or in the future) to deal with all this with DokuTexIt ?

Thank you!

– Martin (a thankful user)

Hi there,

I am looking for the same thing. Could you point me in the right direction to implement this functionality myself? I just need to export something like {[references:some_article_2005]} (which us used by the bibtex plugin) as \cite{some_article_2005}

Help would be very much appreciated.

Thanks,

– Jack

Hi, we have a dokuwiki farm, and want different dokutexit templates in different wikis. Unfortunately, the configuration of dokutexit is saved somehwhere under lib/plugins/dokutexit ... Could you change that in upcoming releases?

– Sebastian (another thankful user)

• move the generated PDF to a specific media namespace

• some nice features from FancyVRB
• a cleanup button besides the download button to force a regeneration added in 11 Feb 2007 version
• work with the bibtex plugin from [http://www.hodique.info/projects/bibtex_plugin] or with a reference management software like Wikindx or Aigaion
• With the current architecture (centralized latex configuration) you unnecessarily limit the possibilities of what you have got there. Why not having multiple latex templates (at best editable online via editor) and let the user choose in the entry-tag if he wants to do a book, a paper or even st. like a letter ... Jan

There’s two reasons :
- The main goal was just to provide a decent print output, you can always download latex sources and hack it.
- Dokutexit LaTeX configuration sucks and will change soon.
— Danjer 2007/07/09 10:06

• Support of currently not supported items which are used quite often:
  • Line break in tables
  • Footnotes in tables

Ok, Why not... Line break in tables, it’s possible. Heavy code in dokutexit, but it’s possible. On the other hand Footnotes in tables is very difficult. Have a look on this: http://www.tex.ac.uk/cgi-bin/texfaq2html?label=footintab
Is there’s anyone can provide me a small and thin latex example of footnotes in tables ?
— Danjer 2007/07/12 10:15

• inetgration of notes via note plugin, seems ‘easy’ via mode=latex, but isn’t(?)

It could be a good idea... Stefan Pampel already send a patch for this. But I can’t include this in dokutexit, I can’t support every dokuwiki plugins in their evolutions. It’s simplier to add a latex mode in the notes plugins.
— Danjer 2007/09/04 11:49

You can find a patch for the note plugins here note — Danjer 2007/12/07 14:28

• I’d like to be able to use dokutexit plugin with the http://www.wikidesign.ch/en/plugin/include/start plugin, so that one can split eg. large manual into chapters included in ‘master’ document in order to get high-quality book-like manual as pdf. That would greatly enhance the functionality of dokutexit plugin It looks that dokutexit ‘just’ need to learn syntax of ‘include’ plugin I believe it can wide-open dokuwiki for many new users (Gour)

In fact it’s easier to add latex mode in the include plugin. I do So, see the patch above. — Danjer 2007/11/27 11:51

You can find a patch for the include plugin here include — Danjer 2007/12/07 14:28

• Is there now a way to make dokutexit plugin work on a windows server? Would be very nice to see a guide. Concerning the aspect above a function to choose the sites which you want to include in the pdf would be nice. Here is what i mean for pmwiki: www.wikipublisher.org.

I don’t know about windows server. I don’t have any windows server... It should work, basicaly it just PHP but the big spot is the latex installation under windows. Is there any windows users feedback ? — Danjer 2007/11/27 11:54

• Two features my colleagues and I would love to see (I realize that the latter is something that DokuWiki itself really doesn’t do, but just to let you know folks are interested):
  1. Make DokuTeXit able to resize images rather than always use full-size in the PDF
  2. Have some facility for referring to an image in the “Figure 2.3” style of LaTeX. I could imagine doing the latter with texit tags - one embedded in the figure caption to give the label, the other in the text to make the reference.

For the first feature there would be (at least) two different approaches.
First you could do the resizing in DokuTeXits latex.php, this was already posted here by David, see Image Resizing.

However this would only work if all your graphics are included like this:

{{  :wiki:big_image.png?650  |A big image}}

If you don`t state the width with each image you could get the width with the php function getimagesize(), which would look something like this:

		if(!$width){
		$imgarr = getimagesize($filename);
		$width = $imgarr[0];
		}
	  if ($width > 450) $width = 450;

The second approach would be to alter the graphics package to define a \maxwidth command which could than be used with the includegraphics command to set a maximum width for images. An example for this can be found here.
— Christian 2007/11/27 11:54

Is this page still in use?? I am searching for a solution to integrate the ‘Generate’ and ‘Download’ PDF button into the template. ...Yes, I’re read this Move Da Button part here. I’ve tried it and it won’t work with only changing these two lines. Did I do smth wrong? Did anybody try the same thing? Is there an other, more detailed solution to move the button out of the wiki pages? I’m not an expert in php programming but i can understand the syntax. ..thanks guys! —Bastian 2008.07.23 11:33—

The [#export_url] export url ] should solve this. — Danjer

I’m using the jsmath plugin with MathJax to render LaTeX on my DokuWiki pages. When I ask DokuTeXit to render to PDF all the equations are removed. Do you have any advice as to how to get the jsmath and DokuTeXit plugins working together?

Yep, you just have to add latex renderer to the jsmath plugin. Peace of cake — Danjer 2010/08/25 21:28

Please may you explain exactly how to accomplish that? Thank you so much. Is copying dokutexit/renderer.php to jsmath/renderer.php enough?

I’m having trouble getting the PDF to render properly using Debian box (Using DokuTexit). When I hit the Generate PDF button, I get

...Document Class: report 2005/09/16 v1.4f Standard LaTeX document class
(/usr/share/texmf-texlive/tex/latex/base/size10.clo))
(/usr/share/texmf-texlive/tex/latex/geometry/geometry.sty
(/usr/share/texmf-texlive/tex/latex/graphics/keyval.sty))
(/usr/share/texmf/tex/latex/ucs/ucs.sty
(/usr/share/texmf/tex/latex/ucs/data/uni-global.def))
(/usr/share/texmf-texlive/tex/latex/base/inputenc.sty
(/usr/share/texmf/tex/latex/ucs/utf8x.def))
(/usr/share/texmf-texlive/tex/latex/pslatex/pslatex.sty)
(/usr/share/texmf-texlive/tex/latex/hyperref/hyperref.sty
(/usr/share/texmf-texlive/tex/latex/hyperref/pd1enc.def)
(/etc/texmf/tex/latex/config/hyperref.cfg)

! LaTeX Error: File `kvoptions.sty' not found.

Methinks something went wrong with the LaTex install. Any ideas? – Jeff

This looks like a normal latex error. The Tex engine cannot find your sty files, update the file ls-R. See your TeX documentation how to do it. –

Website Design Cleveland thành lập doanh nghiệp dich vu ke toan dịch vụ kế toán Phần mềm nhân sự

Quản lý Nhân sự

Phần mềm quản lý nhân sự tiền lương

tham tu

cong ty tham tu

ke sieu thi

quay ke