262 reputation
19
bio website
location
age
visits member for 4 years, 4 months
seen Dec 15 at 11:49

Dec
15
comment Why do people still use Postscript?
4. PostScript programs can generate the page algorithmically , thus they can be smaller than PDF for complex graphics. -- These differences are not always relevant (i.e. they don't affect the final output noticably), in those cases the correctness, speed and configurability of the available tools decides if PostScript or PDF is used.
Dec
15
comment Why do people still use Postscript?
This summarizes my understanding. 1. The same PostScript program can be run in different environments (e.g. with different page sizes), and it can do and draw different things based on the environment. PDF can't do this. 2. The same PostScript program can be run with an interpreter with more accurate number representation, thus the visual output can be of higher quality. PDF can do this only to a limited extent (by pushing multiple transformation matrices to the stack), so it can benefit less from better numeric accuracy. 3. PDF has some other features (e.g. videos, forms and JavaScript).
Dec
15
comment Why do people still use Postscript?
@JamesRyan: For the record, I completely disagree with your opinion on what I understand and what I don't. But luckily nobody else cares.
Dec
14
comment Why do people still use Postscript?
@JamesRyan: I'm 100% sure that I get what you said, but I'm interested in getting to know more. Do you know the answer to my question? Do you care sharing the answer with us?
Dec
14
comment Why do people still use Postscript?
@JamesRyan: Sure, I get it. But this doesn't answer my question about quality. Let's suppose the PostScript program always runs with the same input (e.g. same page size). I can't imagine a situation in which conversion to PDF loses visual quality, and it's not related to numeric precision. From our conversation it seems to me that you can imagine it. Could you please give an example?
Dec
12
comment Why do people still use Postscript?
@JamesRyan: I don't understand your point. Could you please clarify what the difference is if it has nothing to do with number length? Could you please give me a simple PostScript file which loses quality when converting to PDF, even with high quality conversion settings? I'd really like to understand, and based on your description I can't imagine what such a file would contain. A counterexample (whose visual quality does not decrease): 0 9 99 { newpath dup 0 moveto 0 -99 add neg exch lineto stroke } for showpage quit
Dec
12
comment Why do people still use Postscript?
@JamesRyan: Here is how I interpret your comment about the accuracy of PostScript. Table B.1. in adobe.com/products/postscript/pdfs/PLRM.pdf suggests that typically PostScript interpreters use the 4-byte float type to represent numbers. For example, Ghostscript also does it (see ghostscript.com/doc/current/Language.htm). Let's suppose that a PostScript interpreter is modified so that it will use 8 bytes (or even more) for a number, giving it better accuracy. Then some existing PostScript programs would produce slightly better visual quality, and most PDFs wouldn't benefit.
Dec
12
comment Why do people still use Postscript?
The print output quality of PostScript and PDF file formats is the same. If you use a good converter with the right settings, conversion from PDF to PostScript and back doesn't lose visual quality. The default settings of PDF and PostScript generators may be indeed different, PDF generators being set up to do lossy compression to decrease quality. So if a random PDF generator and a random PostScript generator are used with their default settings, it may be possible that the PostScript generator generators better visual quality. But this depends on the tools.
May
28
comment Greedy line breaks for 2 lines
I don't need automatic hyphenation in this example, I've inserted all hyphens I need manually.
May
11
comment error while running latex code with embedded python code
Try to compile it with latex -shell-escape pyinlt.tex
May
11
comment error while running latex code with embedded python code
Please post the contents of the pyinlt.log file.
Feb
19
comment How to detect overfull and underfull hbox without triggering the warning?
With a positive attitude everything is possible :-). Thanks for the \lastbox solution. Feel free to give a luatex solution, but most probably we'll go with \lastbox to reduce dependencies.
Feb
18
comment Can I locally switch to a 'greedy' justification algorithm?
Thanks for the fix, it works!
Feb
18
comment Can I locally switch to a 'greedy' justification algorithm?
Please note that pastebin.com/UNdSgJCa demonstrating the bug doesn't contain any words that need more than 1 line break, so there may be another bug in your code causing text to disappear in an unanticipated way.
Feb
18
comment Can I locally switch to a 'greedy' justification algorithm?
I need to gather more data on the success rate of normal line breaking (with a large \emergencystretch), to figure out how desperately we need an alternative. Please note that if we have an alternative, then we can try both, and keep the result without an overfull \hbox, or if neither has it, keep the result with fewer number of lines.
Feb
18
comment Can I locally switch to a 'greedy' justification algorithm?
There is some input which normal TeX linebreaking can't break without an overfull \hbox, but this code can. Our input is 100000 table cells generated from a database, and we can't afford to manually fix all the failed line breaks, and we need an automated solution. I don't know of anything other than your code.
Feb
18
comment Can I locally switch to a 'greedy' justification algorithm?
Yes, I was planning to use this code in production for typesetting narrow, multiline table cells if TeX's line breaking algorithm produces overfull or underfull boxes. A bugfix would be very useful for me. Without the bugfix I can't use it, dropping text is a no-go even with a warning.
Feb
18
comment Can I locally switch to a 'greedy' justification algorithm?
I think I've found a bug in this implementation of \linebylinepar: some text disappears, see it here: pastebin.com/UNdSgJCa
Feb
17
comment Can I locally switch to a 'greedy' justification algorithm?
Would it be possible to make every line as tight as possible?
Oct
6
comment How to pass a macro as the argument to \selectlanguage
This doesn't answer the question (see the title).