# Latex code is wrapped too early (Origin: bugzilla #687572) #4939

Closed
opened this Issue Jul 2, 2018 · 0 comments

Projects
None yet
1 participant
Owner

### doxygen commented Jul 2, 2018

 status RESOLVED severity major in component build for --- Reported in version 1.8.2 on platform Other Assigned to: Dimitri van Heesch On 2012-11-04 15:25:45 +0000, Stefan wrote: Thanks for making the width of the contents of a LaTeX generated PDF file wider. There is just one problem, where code fragments are still wrapped at the smaller width of the page used previously. The problematic sections are on pages: page 4 ... bottom (introduction => fragmentation level) page 9 ... middle (installation => example command line) page 15 ... bottom (console => example batch script) To correct this I have to add separate code blocks for HTML and LaTeX. Example: @htmlonly 
@echo off
 
 
set UD_EX_FILTER=*system volume information*;*temp*;*tmp*;*recycle*;*.zip;*.7z;*.rar
 
set UD_FILE_SIZE_THRESHOLD=50MB
 
udefrag c: > c:\ud.log
 
 
set UD_IN_FILTER=D:\My Documents\*
 
udefrag d: >> c:\ud.log
 
 
set UD_IN_FILTER=
 
udefrag e: >> c:\ud.log
 @endhtmlonly @latexonly \begin{DoxyCode} @echo off \textcolor{keyword}{set} UD_EX_FILTER=system volume information;temp;tmp;recycle;.zip;.7z;*.rar \textcolor{keyword}{set} UD_FILE_SIZE_THRESHOLD=50MB udefrag c: > c:(\backslash)ud.log \textcolor{keyword}{set} UD_IN_FILTER=D:(\backslash)My Documents(\backslash)* udefrag d: >> c:(\backslash)ud.log \textcolor{keyword}{set} UD_IN_FILTER= udefrag e: >> c:(\backslash)ud.log \end{DoxyCode} @endlatexonly Is there a possibility to allow LaTeX to do the wrapping? Thanks in advance, Stefan On 2012-11-06 20:45:22 +0000, Dimitri van Heesch wrote: As it is a verbatim section I don't think LaTeX will do the wrapping for me, but it wrap limit is indeed set too low. Should be fixed in the next subversion update. On 2012-11-06 21:58:48 +0000, Stefan wrote: Dimitri, would you mind wrapping only at white-space, since a command line was wrapped after a slash, which was really disturbing. -- Stefan On 2012-12-26 16:09:09 +0000, Dimitri van Heesch wrote: This bug was previously marked ASSIGNED, which means it should be fixed in doxygen version 1.8.3. Please verify if this is indeed the case. Reopen the bug if you think it is not fixed and please include any additional information that you think can be relevant. On 2012-12-28 20:02:54 +0000, Stefan wrote: Dimitri, I can confirm that this bug is now fixed. -- Stefan