71–80 of 104 posts
Such a project should have not been started using Python as all current implementations have performance issues, as long you are not gluing C wrapper invocations together.
Very nice project, however for everybody listening: I believe that in such project, but in every project, you should post some kind of document online explaining what is the big design of the project, the biggest problem you have encountered and how you fixed, the limitation of your design choice and why you made those choice. Why that ? 1) Because if I want to code something similar I don't have to read all your cod…
Very nice project, however for everybody listening: I believe that in such project, but in every project, you should post some kind of document online explaining what is the big design of the project, the biggest problem you have encountered and how you fixed, the limitation of your design choice and why you made those choice. Why that ? 1) Because if I want to code something similar I don't have to read all your cod…
I originally planned to release RinohType into wild only after I had finished a full review, refactoring and documenting of the code. I also wanted to write some API documentation and a small tutorial, all in the spirit of making a good first impression. Turns out all this takes a huge amount of time! So I’ve decided to dump the code in its current state onto GitHub, write a blog article about it and await some valuable feedback while I resume my refactoring and documenting chore.
If you decide to play around with the code, please bear in mind that this is just a preview; your experience might not be as smooth as I intend it to be eventually.Likely a clean, general public friendly GUI (web app) can leverage RinohType’s back-end power, and thus it’s adoption. Maybe monetize that as a hosted service.
A set of professionally designed stylesheets/document templates would give wider adoption a head start.
From your roadmap, I’d be glad to help you achieve some goals (if you would want me to be of any assistance):
- Provide a number of standard document/page/font styles
- Include font definitions for freely available fonts
Fake small capitals for fonts that do not provide any
- Advanced typesetting features such as Knuth-Plass … and microtypography
I looked at the sample output ( http://www.mos6581.org/files/intro_template.pdf ) and is it just me or does the vertical spacing seem off? (for example, look at the tables and how the text goes right up to kiss the horizontal bars).
"There is no strict separation of content and style. This is mostly an issue for publishers that want to ensure a consistent style across articles in a journal. With LaTeX, academic authors can always reduce the margins or change the interline spacing to be able to squeeze in more half-truths." Does this ever happen?
So yeah, it probably happens. If it's half an hour before the submission deadline and there are four lines left on the page you have to cut, you'll do what you have to to get the job done. =)
XML format is a non-starter for me. It adds too much cruft to the text; it requires putting everything inside of open and close tags, including paragraphs.
LaTeX does a lot of stuff - it'd take a long time to replicate all that functionality. However, on my todo list is to write some sort of "TeX-down" wrapper for LaTeX - I want to write my dissertation in a modified form of Markdown, with inline LaTeX equations and sectioning of "theorem" and "proof"-type environments, and then run a make to generate the TeX and PDF based off of a type of TeX template. I'm familiar wit…
It's a surprisingly pleasant environment, though it won't probably be enough for your needs (i.e. no "theorem" env).
Earlier quoted context omitted.
You want a drop-in LaTeX replacement. Use LuaTeX.
I might want to use LuaTex, if I knew what it was. It seems they can't be bothered to actually say what it is in their website, in any of their links, or in the introduction chapter of their manual. I therefore take it that no-one who actually writes ever uses it.
LuaTeX is an extended version of pdfTeX using Lua as an embedded scripting language. The LuaTeX projects main objective is to provide an open and configurable variant of TeX while at the same time offering downward compatibility.