View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0003698 | Scribus | Import / Export | public | 2006-04-24 11:49 | 2008-07-30 20:10 |
Reporter | mhanski | Assigned To | |||
Priority | normal | Severity | feature | Reproducibility | N/A |
Status | closed | Resolution | fixed | ||
Platform | any | OS | any | OS Version | any |
Product Version | 1.3 | ||||
Fixed in Version | 1.3.5svn | ||||
Summary | 0003698: Latex import | ||||
Description | Latex import in Scribus | ||||
Tags | No tags attached. | ||||
Patch | |||||
related to | 0001727 | confirmed | HTML import doesn't respect CSS | |
related to | 0000128 | closed | TeX rendering engine library | |
related to | 0000111 | closed | cbradney | Scribus Document File format |
related to | 0001030 | closed | [RFE] Add support for Math | |
child of | 0007647 | acknowledged | Metabug: Render Frames (LaTeX, GnuPlot, LilyPond, GraphViz, etc.) |
|
I'd say LaTeX export is a wontfix. Do you have a use case for that? LaTeX import works now if you go via PostScript. For the future it would be nice to place LaTeX files in Scribus, I think there's already an issue for that. |
|
avox: my first thought was to write "Latex import only", since export seems to be technically more complicated (just thinking of all those non-eps images in Scribus files). So I'm going to change the description accordingly. Importing Latex via Postscript is only a workaround, and not a very good one, I think. You wouldn't probably recommend to anyone importing a 200 page latex book via Postscript -- and the result would be a bunch of vector outlines, and not a Scribus file with text frames, graphic frames etc. If there is a RFE for this, it is very well hidden -- I've searched for it quite a while. |
|
I was talking about the discussion in 0000128. There are three things I don't think are feasible: * export Scribus -> LaTeX * implementing TeX engine within Scribus * importing LaTeX -> native Scribus textframes / images The problem with the last step is that we need to run LaTeX to find out the correct layout. Then all we have is an intermediate format like postscript which doesn't have the logical structure of the original text. Maybe one could use LyX as a filter, but I definitely don't feel like copying the effort the LyX team already made in interpreting LaTeX. |
|
Once 0000111 has been finally defined, this (like many other features) should become easier, I guess. Perhaps even LyX team will come up with a Scribus export filter, who knows :) |
|
Fixed by render frames. As avox said it, importing LaTeX -> native Scribus textframes / images is not realistically feasible |
Date Modified | Username | Field | Change |
---|---|---|---|
2006-04-24 11:49 | mhanski | New Issue | |
2006-04-24 11:49 | mhanski | Relationship added | related to 0001727 |
2006-04-24 11:50 | mhanski | Relationship added | related to 0000128 |
2006-04-24 11:53 | mhanski | Relationship added | related to 0000111 |
2006-04-24 11:54 | avox | Note Added: 0010395 | |
2006-04-24 12:06 | mhanski | Note Added: 0010396 | |
2006-04-24 12:06 | mhanski | Summary | Latex import/export => Latex import |
2006-04-24 12:06 | mhanski | Description Updated | |
2006-04-24 12:07 | mhanski | Note Edited: 0010396 | |
2006-04-24 12:18 | mhanski | Note Edited: 0010396 | |
2006-04-24 12:19 | avox | Note Added: 0010400 | |
2006-04-24 12:27 | mhanski | Status | new => feedback |
2006-04-24 14:43 | mhanski | Note Added: 0010418 | |
2006-06-14 12:15 | mhanski | Relationship added | related to 0001030 |
2008-02-06 18:01 | christoph_s | Status | feedback => assigned |
2008-02-06 18:01 | christoph_s | Assigned To | => Herm |
2008-07-30 20:09 | jghali | Note Added: 0020069 | |
2008-07-30 20:09 | jghali | Status | assigned => resolved |
2008-07-30 20:09 | jghali | Fixed in Version | => 1.3.5svn |
2008-07-30 20:09 | jghali | Resolution | open => fixed |
2008-07-30 20:10 | jghali | Status | resolved => closed |
2008-12-10 16:34 | mhanski | Relationship added | child of 0007647 |