On 21.02.20 21:05, Rainer Müller wrote:
> On 17.02.20 23:13, Mojca Miklavec wrote:
>> I didn't yet check how the latest conversion looks like, so I cannot
>> really make a good informed decision, but I would vote for proceeding
>> with .adoc.
>
> For comparison, I just put the AsciiDoc based guide
On 17.02.20 23:13, Mojca Miklavec wrote:
> I didn't yet check how the latest conversion looks like, so I cannot
> really make a good informed decision, but I would vote for proceeding
> with .adoc.
For comparison, I just put the AsciiDoc based guide online here:
https://guide-test.macports.org/
>
On Mon, 17 Feb 2020 at 21:05, Clemens Lang wrote:
>
> Hi,
>
> On Sat, Feb 15, 2020 at 01:52:44AM +0100, Rainer Müller wrote:
> > It has been almost two years... I would like to suggest we finally
> > decide on a flag day on which I will do a final conversion of the
> > DocBook to AsciiDoc and afte
Hi,
On Sat, Feb 15, 2020 at 01:52:44AM +0100, Rainer Müller wrote:
> It has been almost two years... I would like to suggest we finally
> decide on a flag day on which I will do a final conversion of the
> DocBook to AsciiDoc and after that only the AsciiDoc version is kept
> in the repository. Al
On 25.04.18 04:35, Rainer Müller wrote:
> On 2018-04-22 09:29, Mojca Miklavec wrote:
>> As requested during yesterday's meeting, here's the result of
>> automatic conversion of our guide from xml (docbook) to asciidoc:
>>
>> https://github.com/macports/macports-guide/tree/master/guide/adoc
>>
>
On 2018-04-22 09:29, Mojca Miklavec wrote:
> As requested during yesterday's meeting, here's the result of
> automatic conversion of our guide from xml (docbook) to asciidoc:
>
> https://github.com/macports/macports-guide/tree/master/guide/adoc
>
> This was initially explored by Aljaž and giv
On Apr 23, 2018, at 6:23 PM, Rainer Müller wrote:
> $ sudo gem2.5 install nokogiri -- --use-system-libraries
> …
> pkg-config could not be used to find libxml-2.0
> …
> "pkg-config --exists libxml-2.0"
> dyld: Symbol not found: __cg_jpeg_resync_to_restart
> Referenced from:
> /System/Library/Fra
Hi,
On 23 April 2018 at 17:42, Rainer Müller wrote:
>
> Ruby and gems are really strange...
>
> Apparently, installing nokogiri with bundle fails
Wasn't it you who said that we don't need a port for it as it's just a
one-time conversion? :)
(I'm honestly not sure who said that.)
Looking at how e
On Apr 23, 2018, at 6:23 PM, Rainer Müller wrote:
>
> On 2018-04-23 20:35, Andrew Moore wrote:
>> You might try:
>>
>> $ sudo gem update —system
>>
>> which should install the latest version of bundler (you really want that),
>> and go from there.
>> In the particular case of nokogiri, you mig
On 2018-04-23 20:35, Andrew Moore wrote:
> You might try:
>
> $ sudo gem update —system
>
> which should install the latest version of bundler (you really want that),
> and go from there.
> In the particular case of nokogiri, you might also try running `gem install
> nokogiri` as user root.
I
On Apr 23, 2018, at 3:46 PM, Jan Stary wrote:
>
> On Apr 23 16:26:13, rai...@macports.org wrote:
>> On 2018-04-23 14:27, Jan Stary wrote:
These quirks are added by DocBook XSLT and are apparently required to
make the output compatible. If you disagree with that, talk to DocBook
why
On Apr 23, 2018, at 14:46, Jan Stary wrote:
Man, you sure love to argue about stuff.
> The asciidoc is what you don't see on you terminal.
> The resulting man(7) page is what you see, rendered
> by either groff (typically) or mandoc.
Asciidoc is what we see in an editor when we edit the manual
On Apr 23 16:26:13, rai...@macports.org wrote:
> On 2018-04-23 14:27, Jan Stary wrote:
> >> These quirks are added by DocBook XSLT and are apparently required to
> >> make the output compatible. If you disagree with that, talk to DocBook
> >> why they added them.
> >
> > You don't care that a 2008
On Apr 23, 2018, at 11:42 AM, Rainer Müller wrote:
>
> On 2018-04-22 09:29, Mojca Miklavec wrote:
>> Hi,
>>
>> As requested during yesterday's meeting, here's the result of
>> automatic conversion of our guide from xml (docbook) to asciidoc:
>>
>>https://github.com/macports/macports-guide/t
On 2018-04-22 09:29, Mojca Miklavec wrote:
> Hi,
>
> As requested during yesterday's meeting, here's the result of
> automatic conversion of our guide from xml (docbook) to asciidoc:
>
> https://github.com/macports/macports-guide/tree/master/guide/adoc
>
> This was initially explored by Alja
On 2018-04-23 14:27, Jan Stary wrote:
>> These quirks are added by DocBook XSLT and are apparently required to
>> make the output compatible. If you disagree with that, talk to DocBook
>> why they added them.
>
> You don't care that a 2008 workaround to a Debian bug
> is included in every manpage
On Apr 23 13:17:10, rai...@macports.org wrote:
> On 2018-04-23 10:12, Jan Stary wrote:
> >>> We are already using the AsciiDoc format for our man pages,
> >>
> >> Manpages are supposed to be written in mdoc(7), the language of
> >> manpages, just like e.g. /usr/share/man/man1/ls.1 is.
> >>
> >> The
On 2018-04-23 10:42, Jan Stary wrote:
> Also, having manpages written in asciidoc means we need
> the abominable docbook to actually produce the man(7) pages, right?
> At least that's what it says at the end of install:
>
> * Warning: Using pre-generated man pages only.
> * asciidoc, x
On 2018-04-23 10:12, Jan Stary wrote:
>>> We are already using the AsciiDoc format for our man pages,
>>
>> Manpages are supposed to be written in mdoc(7), the language of
>> manpages, just like e.g. /usr/share/man/man1/ls.1 is.
>>
>> The current port-* manpages are horrible
>> (not talking about c
On Apr 23 10:09:06, mo...@macports.org wrote:
> On 23 April 2018 at 09:42, Jan Stary wrote:
> > On Apr 22 09:29:53, mo...@macports.org wrote:
> >> As requested during yesterday's meeting, here's the result of
> >> automatic conversion of our guide from xml (docbook) to asciidoc:
> >>
> >> http
On Apr 23 10:12:06, h...@stare.cz wrote:
> > > We are already using the AsciiDoc format for our man pages,
> >
> > Manpages are supposed to be written in mdoc(7), the language of
> > manpages, just like e.g. /usr/share/man/man1/ls.1 is.
> >
> > The current port-* manpages are horrible
> > (not ta
> > We are already using the AsciiDoc format for our man pages,
>
> Manpages are supposed to be written in mdoc(7), the language of
> manpages, just like e.g. /usr/share/man/man1/ls.1 is.
>
> The current port-* manpages are horrible
> (not talking about content, but markup).
>
> Look at e.g. por
On 23 April 2018 at 09:42, Jan Stary wrote:
> On Apr 22 09:29:53, mo...@macports.org wrote:
>> As requested during yesterday's meeting, here's the result of
>> automatic conversion of our guide from xml (docbook) to asciidoc:
>>
>> https://github.com/macports/macports-guide/tree/master/guide/a
On Apr 22 09:29:53, mo...@macports.org wrote:
> As requested during yesterday's meeting, here's the result of
> automatic conversion of our guide from xml (docbook) to asciidoc:
>
> https://github.com/macports/macports-guide/tree/master/guide/adoc
>
> This was initially explored by Aljaž and
On 2018-04-22 09:44, Andrew Moore wrote:
> Just to be clear, asciidoc is the format, but asciidoctor is the text
> processor (a superset of python asciidoc). Is that correct?
Yes. AsciiDoc is both the name of the format and also the name of the
original reference implementation in Python, but de
Just to be clear, asciidoc is the format, but asciidoctor is the text processor
(a superset of python asciidoc). Is that correct?
-AM
> On Apr 22, 2018, at 3:29 AM, Mojca Miklavec wrote:
>
> Hi,
>
> As requested during yesterday's meeting, here's the result of
> automatic conversion of our gu
Hi,
As requested during yesterday's meeting, here's the result of
automatic conversion of our guide from xml (docbook) to asciidoc:
https://github.com/macports/macports-guide/tree/master/guide/adoc
This was initially explored by Aljaž and gives quite nice results
out-of-the-box, but there ar
27 matches
Mail list logo
