User talk:Austin J. Che/Extensions/LatexDoc: Difference between revisions

From OpenWetWare
Jump to navigationJump to search
(thanks)
Line 19: Line 19:
--[[User:Jacobs|Jacobs]] 16:11, 20 May 2007 (EDT)
--[[User:Jacobs|Jacobs]] 16:11, 20 May 2007 (EDT)
*'''[[User:Austin J. Che|Austin Che]] 22:16, 20 May 2007 (EDT)''': I made a small change (untested). Either download it or add <nowiki>function __toString() { return 'LatexDoc'; }</nowiki> to the LatexDoc class. See if that fixes your problem.
*'''[[User:Austin J. Che|Austin Che]] 22:16, 20 May 2007 (EDT)''': I made a small change (untested). Either download it or add <nowiki>function __toString() { return 'LatexDoc'; }</nowiki> to the LatexDoc class. See if that fixes your problem.
*'''--[[User:Jacobs|Jacobs]] 10:27, 22 May 2007 (EDT)''': Works perfectly! Thanks.

Revision as of 07:27, 22 May 2007

  • Reshma 19:40, 29 January 2007 (EST): The main obnoxious thing about composing latex docs on the wiki is that it doesn't wrap "plain text". It wraps in the edit window but the html page has one line per paragraph unless you manually include returns.
  • Austin Che 19:43, 29 January 2007 (EST): actually I recently changed this behavior at the request of someone. The original behavior would treat most of the text as normal html and thus wrap in the browser. However, due to mediawiki parsing, it would insert pre tags such that any lines that began with a space would be boxed which looked weird. So I put one pre around the entire document instead. If there's an alternative, I'd be happy to implement it.
  • Austin Che 21:21, 29 January 2007 (EST): Ok, I added an auto word wrap to it. Check it out.
  • Reshma 21:20, 30 January 2007 (EST): EPS files are not permitted. This is unfortunate since I seem to have better luck with EPS files when writing "normal" latex docs.
  • Reshma 21:20, 30 January 2007 (EST): Errors in the latex document (i.e. syntax errors) cause Firefox to crash on Mac OS X 10.3. However, this does not happen in Safari in Mac OS X 10.4.
  • Austin Che 23:17, 30 January 2007 (EST): Currently it uses pdflatex which I find more useful. It would be trivial to make it generate pdf via latex->dvipdf or latex->dvips->ps2pdf. But making 3 buttons called 'get PDF via ...' seemed silly but I guess I could do it. Regarding syntax errors, that seems unbelievable that firefox would crash. When does it crash? Looking at the latex document? That's just plain text for the browser and I don't see how that could do anything. When getting the pdf? If there's a syntax error, no pdf should be generated at all but even if an incorrect pdf was generated, it should have nothing to do with the browser at all, and would have to do with the pdf viewer.
  • Reshma 00:08, 31 January 2007 (EST): I see your point about it being silly to have 3 get pdf buttons. I guess the only reason to do this is it might facilitate reuse of the same images when going between offline and onlike latex documents. As for the syntax errors crashing Firefox, the crashes do happen when generating/getting the pdf. It may very well be a problem with the pdf viewer. I just thought I would note that it is happening here on the talk page.

Version page broken under 1.8

SpecialVersion.php gives the following error.

Catchable fatal error: Object of class LatexDoc could not be converted to string in /mywiki/includes/SpecialVersion.php on line 241

Is this happening when it parses the extension credits? I am running MW 1.8. --Jacobs 16:11, 20 May 2007 (EDT)

  • Austin Che 22:16, 20 May 2007 (EDT): I made a small change (untested). Either download it or add function __toString() { return 'LatexDoc'; } to the LatexDoc class. See if that fixes your problem.
  • --Jacobs 10:27, 22 May 2007 (EDT): Works perfectly! Thanks.