Concluding on HTML rendering
I would like to conclude a bit on this interesting dialogue about HTML
renderring.
We have talked about that groff low-level-markup is not so suitable for
converting to SGML variants because groff markup does not follow a pattern
that harmonizes well with SGML and rel
Hi Mikkel,
mikkel meinike wrote on Tue, Aug 22, 2017 at 03:17:17PM +0200:
> Ingo wrote:
>> So technically, the best way to transform groff_mom (7) documents
>> Into HTML would be to parse a high-level MOM node tree and convert
>> That directly to HTML, without going through troff (1) at all, like
Hello again
Now I have read all your answers and answers to each other's answers and I
have done some treing and testing.
Ingo wrote:
> So technically, the best way to transform groff_mom (7) documents
> Into HTML would be to parse a high-level MOM node tree and convert
> That directly to HTML, w
On Fri, Aug 18, 2017, Werner Lemberg wrote:
> Well, as you correctly state, lilypond's main target is engraving.
> However, I invite you as a MIDI expert to help improve lilypond's MIDI
> capabilities :-)
When I finish fighting with the MuseScore developers over the same
issue. :)
--
Peter Schaf
>> The world is small – I'm one of the lilypond developers...
>
> I was aware. The paper doesn't discuss lilypond at all since it
> isn't germane--sort of a shame since lilypond hands down beats
> everything else out there when it comes to engraving.
Well, as you correctly state, lilypond's mai
On Fri, Aug 18, 2017, Werner Lemberg wrote:
>
> > The formatted paper is online at
> >
> > http://www.schaffter.ca/pdf/linux-midi-orchestration.pdf
>
> The world is small – I'm one of the lilypond developers...
I was aware. The paper doesn't discuss lilypond at all since it
isn't germane--so
> The formatted paper is online at
>
> http://www.schaffter.ca/pdf/linux-midi-orchestration.pdf
The world is small – I'm one of the lilypond developers...
Werner
On Fri, Aug 18, 2017, Steve Izma wrote:
> It seems to me this argument implies a desire for a
> general-purpose markup language for creating typeset documents,
> which I think is an impossible goal.
A couple of years ago I was consulted by a programmer tackling the
"perfect markup language" proble
Ingo Schwarze wrote:
>
> ...
>
> Converting markdown into acceptable
> roff input is just not feasible - not only because there is no tool
> to do it, but also because markdown is just not powerful enough,
> even if you were willing to write a new program to do that.
>
> Besides, i hate the myt
On Fri, Aug 18, 2017 at 12:33:12AM +0200, Ingo Schwarze wrote:
> Subject: Re: [Groff] Regarding HTML rendering
>
> Steve Izma wrote on Thu, Aug 17, 2017 at 04:52:56PM -0400:
>
> > A relatively simple notation like Markdown would also work,
>
> I agree with all yo
Hi Steve,
Steve Izma wrote on Thu, Aug 17, 2017 at 04:52:56PM -0400:
> A relatively simple notation like Markdown would also work,
I agree with all you are saying except this.
The OP is certainly better off writing his documents in proper
roff(7) or groff_mom(7) and living with slighly quirky H
On Wed, Aug 16, 2017 at 08:28:53PM +0200, Ingo Schwarze wrote:
> Subject: Re: [Groff] Regarding HTML rendering
> ...
> The roff language is a poor fit for what HTML excels in,
> namely, hierarchical representation of information and semantic
> markup. The HTML language is a poor fit
Hi Mikkel,
Peter wrote:
> Ingo wrote:
> > So technically, the best way to transform groff_mom(7) documents
> > into HTML would be to parse a high-level MOM node tree and convert
> > that directly to HTML, without going through troff(1) at all, like
> > mandoc(1) does it for the mdoc(7) language.
>
Hi Mikkel,
> As you can see, there is also a mistake with the colors. I would also
> like to receive suggestions for how this error can be eliminated in
> the HTML rendering.
Here's how I worked out what the problem was.
$ printf '%s\n' \
> 'rod\m[red]knight\m[]rod' \
> 'rod\
On Wed, Aug 16, 2017, Ingo Schwarze wrote:
> Peter Schaffter wrote on Wed, Aug 16, 2017 at 01:37:17PM -0400:
> > On Wed, Aug 16, 2017, Mikkel wrote:
>
> >> I can see that nobody has replied. Pleas don't worry about it. It's not
> >> anything critical to me it's just sometimes nice to have a little
Hi,
Peter Schaffter wrote on Wed, Aug 16, 2017 at 01:37:17PM -0400:
> On Wed, Aug 16, 2017, Mikkel wrote:
>> I can see that nobody has replied. Pleas don't worry about it. It's not
>> anything critical to me it's just sometimes nice to have a little input
>> from others. I think that tbl is the r
Mikkel --
On Wed, Aug 16, 2017, Mikkel wrote:
> Hi
>
> I can see that nobody has replied. Pleas don't worry about it. It's not
> anything critical to me it's just sometimes nice to have a little input
> from others. I think that tbl is the route go for me. But don't worry about
> giving an answer
Hi
I can see that nobody has replied. Pleas don't worry about it. It's not
anything critical to me it's just sometimes nice to have a little input
from others. I think that tbl is the route go for me. But don't worry about
giving an answer unless you feel inspired to do so :-). Greetings Mikkel
D
18 matches
Mail list logo
