<div dir='auto'><div dir="auto">That looks great. It's nice to see the formula variables formatted properly in the text. I agree that LaTeX embedded in markdown is a good choice!</div><br><div class="gmail_extra" dir="auto"><br><div class="gmail_quote">On 7 Apr 2018 2:11 a.m., Bill Lorensen <bill.lorensen@gmail.com> wrote:<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">More progress.I found a great online tool to generate Latex formulas.
<br>
With no previous Latex experience,I was able to generate all of the
<br>
equations for Chapter 3. I can embed Latex in the markdown. The
<br>
equations are rendered by MathJax.
<br>
<br>
Here is the online website:
<br>
http://www.hostmath.com/
<br>
<br>
and here is the updated Chapter 3:
<br>
<br>
https://lorensen.github.io/VTKExamples/site/VTKBook/Chapter3/
<br>
<br>
Bill
<br>
<br>
On Fri, Apr 6, 2018 at 6:28 AM, David Cole via vtk-developers
<br>
<vtk-developers@vtk.org> wrote:
<br>
> "I ignore whether Markdown/reStrucuredText support for
<br>
> tools to have proper printed texts is likely to be improved."
<br>
>
<br>
> I have become a big fan of "print to pdf using the Chrome browser" to
<br>
> get a printed copy of web content these days. It's actually not a bad
<br>
> way to go if you don't need to refer to page numbers within the text.
<br>
>
<br>
>
<br>
> And now, this is just my opinion, so take with yet another grain of salt:
<br>
>
<br>
> The available "writer pool" for LaTeX is far far smaller than that for
<br>
> markdown. If the math stuff must be in LaTeX, I'd very strongly prefer
<br>
> to see it as embedded chunks of LaTeX than have the whole thing be in
<br>
> LaTeX.
<br>
>
<br>
>
<br>
> Nice work, as usual Bill.
<br>
>
<br>
>
<br>
> Thanks,
<br>
> David C.
<br>
>
<br>
>
<br>
>
<br>
> On Fri, Apr 6, 2018 at 2:20 AM, Jon Haitz Legarreta
<br>
> <jhlegarreta@vicomtech.org> wrote:
<br>
>> Bill, Andrew, simply brilliant.
<br>
>>
<br>
>> I've spot some parts in the Chapters 3 and 6 strawmans that were
<br>
>> already mentioned by you and Todd whose transition has some errors
<br>
>> (links that are missing, missing cross-reference links to VTK classes,
<br>
>> examples or bibliography, etc.).
<br>
>>
<br>
>> How can we contribute to fix them? Are you still working on the
<br>
>> transition tools to improve the output, or you want us to manually try
<br>
>> to fix them?
<br>
>>
<br>
>> I can help with/do all the Maths in LaTeX Bill. However, if the tool
<br>
>> you found works or the transition will be automatic, I do not see
<br>
>> where to help at this stage. Please, let me know.
<br>
>>
<br>
>> Otherwise, it's looking awesome.
<br>
>>
<br>
>> As for the LaTeX vs. Markdown/reStrucuredText discussion:
<br>
>>
<br>
>> I've contributed with some patches to the ITK SW Guide written in
<br>
>> LaTeX. I guess at the time it was written Markdown and reStrucuredText
<br>
>> were not available, so I think the choice was fair.
<br>
>>
<br>
>> Having said that, I admit that the learning curve for LaTeX may be
<br>
>> higher than that for Markdown or reStrucuredText. The latter are
<br>
>> tailored for web navigation, which is most people expect. And times
<br>
>> have changed. I ignore whether Markdown/reStrucuredText support for
<br>
>> tools to have proper printed texts is likely to be improved.
<br>
>>
<br>
>> I guess the ITK SW Guide requiring to be compiled (both the examples
<br>
>> to generate the figures and LaTeX itself) is not a downside, since VTK
<br>
>> Cxx examples used in this book need so.
<br>
>>
<br>
>> I guess having a first version for both cases (LaTeX and
<br>
>> Markdown/reStrucuredText) is somehow costly at the beginning.
<br>
>> Maintaining/sync'ing them once that is done every time there is a
<br>
>> change may not effortless also. But that may be the price to pay.
<br>
>>
<br>
>> The ITK SW Guide keeps being maintained. I ignore whether the ITK
<br>
>> folks at Kitware have considered to transition to Markdown or
<br>
>> reStrucuredText.
<br>
>>
<br>
>> JON HAITZ
<br>
>>
<br>
>> --
<br>
>>
<br>
>>
<br>
>> On 6 April 2018 at 01:05, Todd via vtk-developers
<br>
>> <vtk-developers@vtk.org> wrote:
<br>
>>> Fantastic. I think Latex is definitely the way to go, although I'm no expert
<br>
>>> in writing it.
<br>
>>>
<br>
>>> _______________________________________________
<br>
>>> Powered by www.kitware.com
<br>
>>>
<br>
>>> Visit other Kitware open-source projects at
<br>
>>> http://www.kitware.com/opensource/opensource.html
<br>
>>>
<br>
>>> Search the list archives at: http://markmail.org/search/?q=vtk-developers
<br>
>>>
<br>
>>> Follow this link to subscribe/unsubscribe:
<br>
>>> https://vtk.org/mailman/listinfo/vtk-developers
<br>
>>>
<br>
>>>
<br>
>> _______________________________________________
<br>
>> Powered by www.kitware.com
<br>
>>
<br>
>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
<br>
>>
<br>
>> Search the list archives at: http://markmail.org/search/?q=vtk-developers
<br>
>>
<br>
>> Follow this link to subscribe/unsubscribe:
<br>
>> https://vtk.org/mailman/listinfo/vtk-developers
<br>
>>
<br>
> _______________________________________________
<br>
> Powered by www.kitware.com
<br>
>
<br>
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
<br>
>
<br>
> Search the list archives at: http://markmail.org/search/?q=vtk-developers
<br>
>
<br>
> Follow this link to subscribe/unsubscribe:
<br>
> https://vtk.org/mailman/listinfo/vtk-developers
<br>
>
<br>
<br>
<br>
<br>
--
<br>
Unpaid intern in BillsParadise at noware dot com
<br>
_______________________________________________
<br>
Powered by www.kitware.com
<br>
<br>
Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
<br>
<br>
Please keep messages on-topic and check the VTK FAQ at: http://www.vtk.org/Wiki/VTK_FAQ
<br>
<br>
Search the list archives at: http://markmail.org/search/?q=vtkusers
<br>
<br>
Follow this link to subscribe/unsubscribe:
<br>
https://vtk.org/mailman/listinfo/vtkusers
<br>
</p>
</blockquote></div><br></div></div>