PDF manual soon available online in HTML (maybe)
Richard
available online in HTML:
On Feb 9, 3:33 am, mdipierro <mdipie...@cs.depaul.edu> wrote:
> I am considering posting most of the book on line in HTML. This may be
> possible with a disclaimer about "do not reproduce in print". The main
> issue is that the book is in latex and not easy to convert.
http://groups.google.com/group/web2py/browse_thread/thread/ce1c7614ceb92a7c#07d7e012362e1490
There have been a number of complaints lately about the documentation
so it is good this is being considered.
Some points to ponder:
- How would the online manual best be hosted? - the wiki app? A
djangobook clone?
- Should the PDF/latex be manually inserted into this app, or is there
an automatic method?
- How would online edits be fed back into the official PDF version?
Richard
mdipierro
Let me resolve some of the issues on my side first.
This should not be stopping anybody from writing howtos, examples and
tutorials.
this is complementary and putting everything together is a secondary
step.
If people know of a good tool to convert latex to wiki format and vice
versa, I could use that.
Massimo
On Feb 8, 6:39 pm, Richard <richar...@gmail.com> wrote:
> In case you missed it Massimo is considering making the manual
> available online in HTML:
>
> On Feb 9, 3:33 am, mdipierro <mdipie...@cs.depaul.edu> wrote:
>
> > I am considering posting most of the book on line in HTML. This may be
> > possible with a disclaimer about "do not reproduce in print". The main
> > issue is that the book is in latex and not easy to convert.
>
> http://groups.google.com/group/web2py/browse_thread/thread/ce1c7614ce...
Jonathan Lundell
> If people know of a good tool to convert latex to wiki format and vice
> versa, I could use that.
http://hutchinson.belmont.ma.us/tth/ looks like the best bet for latex to html; you could probably get from there to wiki. Back again? I could be wrong, but I think you're dreaming....
mdipierro
that does not look at all like the original.
On Feb 8, 7:22 pm, Jonathan Lundell <jlund...@pobox.com> wrote:
> On Feb 8, 2010, at 4:58 PM, mdipierro wrote:
>
> > If people know of a good tool to convert latex to wiki format and vice
> > versa, I could use that.
>
> http://hutchinson.belmont.ma.us/tth/looks like the best bet for latex to html; you could probably get from there to wiki. Back again? I could be wrong, but I think you're dreaming....
Jonathan Lundell
> I just tried pandoc (latex->rst>latex) and I end up with something
> that does not look at all like the original.
It's the Second Law of Thermodynamics. Latex and rst (or html) are not equivalent, and conversions in either direction are lossy (unless you manage to use only the compatible intersection of their features).
You couldn't convert your PDF back to Latex, either, without losing a lot.
mdipierro
On Feb 8, 7:43 pm, Jonathan Lundell <jlund...@pobox.com> wrote:
> On Feb 8, 2010, at 5:33 PM, mdipierro wrote:
>
> > I just tried pandoc (latex->rst>latex) and I end up with something
> > that does not look at all like the original.
>
> It's the Second Law of Thermodynamics. Latex and rst (or html) are not equivalent, and conversions in either direction are lossy (unless you manage to use only the compatible intersection of their features).
>
> You couldn't convert your PDF back to Latex, either, without losing a lot.
>
>
>
> > On Feb 8, 7:22 pm, Jonathan Lundell <jlund...@pobox.com> wrote:
> >> On Feb 8, 2010, at 4:58 PM, mdipierro wrote:
>
> >>> If people know of a good tool to convert latex to wiki format and vice
> >>> versa, I could use that.
>
> >>http://hutchinson.belmont.ma.us/tth/lookslike the best bet for latex to html; you could probably get from there to wiki. Back again? I could be wrong, but I think you're dreaming....
>
>
Richard
> I am not sure this is something people should vote on.
to clarify, I wasn't calling for a vote on what to do with the manual
- I acknowledge it is your IP. But ideas and feedback might be helpful.
Mariano Reingart
are working in several features, including wyswyg editing and pdf
output, to organize and translate some kind of manual (and other minor
updates to make the wiki more user friendly).
To convert html to reST, using html2rst.py seems to work (but some
minor fixes are needed with preformated blocks).
And, here in Argentina, rst2pdf was used to make the pdf from the
translated official python tutorial (who is in reST):
- http://docs.python.org.ar/tutorial/contenido.html
- http://python.org.ar/pyar/Tutorial?action=AttachFile&do=get&target=TutorialPython.pdf
Indeed, the spanish python tutorial was finally printed (in paper with
a soft cover) as a nice and cheap book.
IMHO, a user-friendly wiki is a good way to do this work, and fixing
web2py-wiki is a must.
Regards
Mariano Reingart
> --
> You received this message because you are subscribed to the Google Groups "web2py-users" group.
> To post to this group, send email to web...@googlegroups.com.
> To unsubscribe from this group, send email to web2py+un...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
>
>
Alexandre Andrade
I never discuss about my clients needs. I just understand it and make the specification.
1. Documentation about web2py is poor. Everyone agree.
2. One reason for this is Massimo defines the new versions, and there is no roadmap. New features are added 'ad hoc'
3. Since Massimo decides what will be in new versions and when, only him know about the new functionalities.
4. Since anyone is talking about roadmaps and planned versions, and colaborative developing, documentation depends almost of Massimo
5. So, what him want is what we have.
He wants a tool/script to convert latex/wiki and wiki/latex.
Talk, talk, talk, is no resolving anything.
My sugestion is:
1. Can someone make a budget do develop this tool (wiki in web2py and conversion latex/wiki/latex)?
2. Who agrees to donate (and how much) do pay developing this?
To me, open source is not about 'not paid to develop', but once developed, be free to be used.
If someone can do it, and enough people agree the value need, we can advance by this way. If none, its time to search another solution.
--
You received this message because you are subscribed to the Google Groups "web2py-users" group.
To post to this group, send email to web...@googlegroups.com.
To unsubscribe from this group, send email to web2py+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
--
Atenciosamente
--
=========================
Alexandre Andrade
Hipercenter.com
Beerc
mdipierro
None of the tools suggested here worked in converting my Latex to wiki
but I only used my own Latex macros so I stayed awake last night and
wrote my own tool (works only with my own latex but works much better
than anything else). I am letting you know so that we do not overlap.
I will keep you posted...
Massimo
On Feb 9, 6:06 am, Alexandre Andrade <alexandrema...@gmail.com> wrote:
> Well,
> I never discuss about my clients needs. I just understand it and make the
> specification.
>
> 1. Documentation about web2py is poor. Everyone agree.
> 2. One reason for this is Massimo defines the new versions, and there is no
> roadmap. New features are added 'ad hoc'
> 3. Since Massimo decides what will be in new versions and when, only him
> know about the new functionalities.
> 4. Since anyone is talking about roadmaps and planned versions, and
> colaborative developing, documentation depends almost of Massimo
> 5. So, what him want is what we have.
>
> He wants a tool/script to convert latex/wiki and wiki/latex.
>
> Talk, talk, talk, is no resolving anything.
>
> My sugestion is:
>
> 1. Can someone make a budget do develop this tool (wiki in web2py and
> conversion latex/wiki/latex)?
> 2. Who agrees to donate (and how much) do pay developing this?
>
> To me, open source is not about 'not paid to develop', but once developed,
> be free to be used.
>
> If someone can do it, and enough people agree the value need, we can advance
> by this way. If none, its time to search another solution.
>
> 2010/2/8 mdipierro <mdipie...@cs.depaul.edu>
> > web2py+un...@googlegroups.com<web2py%2Bunsu...@googlegroups.com>
Jason Brower
amazing. +1 Your a great guy Massimo.
---
Warmest Regards,
Jason Brower
DenesL
BTW I am working on improving the web2py wiki app, maybe it will be
done today.
On Feb 8, 11:43 pm, Mariano Reingart <reing...@gmail.com> wrote:
> For the web2py spanish documentation wiki (btw using web2py-wiki) we
> are working in several features, including wyswyg editing and pdf
> output, to organize and translate some kind of manual (and other minor
> updates to make the wiki more user friendly).
>
> To convert html to reST, using html2rst.py seems to work (but some
> minor fixes are needed with preformated blocks).
>
> And, here in Argentina, rst2pdf was used to make the pdf from the
> translated official python tutorial (who is in reST):
>
> -http://docs.python.org.ar/tutorial/contenido.html
> -http://python.org.ar/pyar/Tutorial?action=AttachFile&do=get&target=Tu...
selecta
document my own code with it
Richard
problems, so do you think its worth allowing anonymous edits, like
wikipedia permits?
Mariano Reingart
- No anonymous edits, but changed
@auth.requires_membership('developer') to requires_login()
- Fixed create_page bug
- Full internationalization
- Spanish translation
Denes is working on more radical changes, and I'm working on timeline,
wyswyg & pdf output.
Thadeus Burgess
it going up
-Thadeus
Jonathan Lundell
> No anonymous edits... Django fanboys will deface it within minutes of
> it going up
I think that's best. Wikipedia expends an awful lot of effort cleaning up after defacers.
Thadeus Burgess
django users.
I am referring to the time when web2py vs django comparison was
editable, there were many django users who would edit it and deface
it.
And we also know about those same django users trying to get web2py
flagged is spam across the internet.
Aside from this, openly allowing edits leaves ANYBODY to deface it,
regardless of if they like web2py or not, they just like defacing
things.
-Thadeus