Em Mon, 21 Nov 2016 16:44:28 +0100
Johannes Berg escreveu:
> > > > You had pointed me to this plugin before
> > > > https://pythonhosted.org/sphinxcontrib-aafig/
> > > >
> > > > but I don't think it can actually represent any of the pictures.
> > >
> > > No, but there are some ascii art image
On Mon, 2016-11-21 at 12:06 -0200, Mauro Carvalho Chehab wrote:
> Em Mon, 21 Nov 2016 11:39:41 +0100
> Johannes Berg escreveu:
> > On Sat, 2016-11-19 at 10:15 -0700, Jonathan Corbet wrote:
> >
> > > Rather than beating our heads against the wall trying to convert
> > > between various image forma
On Mon, 21 Nov 2016, Johannes Berg wrote:
> I had a hack elsewhere that would embed the fixed-width text if the
> plugin isn't present, which seemed like a decent compromise, but nobody
> is willing to let plugins be used in general to start with, it seems :)
FWIW I'm all for doing this stuff in
> > > You had pointed me to this plugin before
> > > https://pythonhosted.org/sphinxcontrib-aafig/
> > >
> > > but I don't think it can actually represent any of the pictures.
> >
> > No, but there are some ascii art images inside some txt/rst files
> > and inside some kernel-doc comments. We co
Em Mon, 21 Nov 2016 11:39:41 +0100
Johannes Berg escreveu:
> On Sat, 2016-11-19 at 10:15 -0700, Jonathan Corbet wrote:
> >
> > I don't know what the ultimate source of these images is (Mauro,
> > perhaps you could shed some light there?).
>
> I'd argue that it probably no longer matters. Whet
On Sat, 2016-11-19 at 10:15 -0700, Jonathan Corbet wrote:
>
> I don't know what the ultimate source of these images is (Mauro,
> perhaps you could shed some light there?).
I'd argue that it probably no longer matters. Whether it's xfig, svg,
graphviz originally etc. - the source is probably long
Em Sat, 19 Nov 2016 22:59:01 -
"David Woodhouse" escreveu:
> > I think that graphviz and svg are the reasonable modern formats. Let's
> > try to avoid bitmaps in today's world, except perhaps as intermediate
> > generated things for what we can't avoid.
Ok, I got rid of all bitmap images:
> On Sat, Nov 19, 2016 at 9:55 AM, David Woodhouse
> wrote:
>>
>> I know it's unfashionable these days, but TeX always used to be bloody
>> good at that kind of thing.
>
> You must have used a different TeX than I did.
>
> TeX is a horrible example. The moment you needed to insert anything
> that
On Sat, Nov 19, 2016 at 12:54 PM, Mauro Carvalho Chehab
wrote:
>
> I did some research on Friday trying to identify where those images
> came. It turns that, for the oldest images (before I took the media
> maintainership), PDF were actually their "source", as far as I could track,
> in the sense
Em Sat, 19 Nov 2016 10:15:43 -0700
Jonathan Corbet escreveu:
> On Thu, 17 Nov 2016 08:02:50 -0800
> Linus Torvalds wrote:
>
> > We have makefiles, but more importantly, few enough people actually
> > *generate* the documentation, that I think if it's an option to just
> > fix sphinx, we should
On Sat, Nov 19, 2016 at 9:55 AM, David Woodhouse wrote:
>
> I know it's unfashionable these days, but TeX always used to be bloody
> good at that kind of thing.
You must have used a different TeX than I did.
TeX is a horrible example. The moment you needed to insert anything
that TeX didn't know
On 11/19/16 09:15, Jonathan Corbet wrote:
> Might there be a tool or an extension out there that would allow us
> to express these diagrams in a text-friendly, editable form?
How about using the graphviz languages for generating diagrams that can
be described easily in one of the graphviz langua
On Sat, 2016-11-19 at 10:15 -0700, Jonathan Corbet wrote:
> Might there be a tool or an extension out there that
> would allow us to express these diagrams in a text-friendly, editable
> form?
I know it's unfashionable these days, but TeX always used to be bloody
good at that kind of thing.
--
d
> Rather than beating our heads against the wall trying to convert between
> various image formats, maybe we need to take a step back. We're trying
> to build better documentation, and there is certainly a place for
> diagrams and such in that documentation. Johannes was asking about it
> for the
On Thu, 17 Nov 2016 08:02:50 -0800
Linus Torvalds wrote:
> We have makefiles, but more importantly, few enough people actually
> *generate* the documentation, that I think if it's an option to just
> fix sphinx, we should do that instead. If it means that you have to
> have some development versi
On Fri, Nov 18, 2016 at 11:15:09AM +0200, Jani Nikula wrote:
> On Thu, 17 Nov 2016, Linus Torvalds wrote:
> > We have makefiles, but more importantly, few enough people actually
> > *generate* the documentation, that I think if it's an option to just
> > fix sphinx, we should do that instead. If i
On Thu, 17 Nov 2016, Linus Torvalds wrote:
> We have makefiles, but more importantly, few enough people actually
> *generate* the documentation, that I think if it's an option to just
> fix sphinx, we should do that instead. If it means that you have to
> have some development version of sphinx, s
On Thu, Nov 17, 2016 at 3:07 AM, Arnd Bergmann wrote:
>
> [adding Linus for clarification]
>
> I understood the concern as being about binary files that you cannot
> modify with classic 'patch', which is a separate issue.
No. That is how I *noticed* the issue. Those stupid pdf binary files
have b
On Thu, Nov 17, 2016 at 12:07:15PM +0100, Arnd Bergmann wrote:
> [adding Linus for clarification]
>
> I understood the concern as being about binary files that you cannot
> modify with classic 'patch', which is a separate issue.
I think the other complaint is that the image files aren't "source"
> So, the problem that remains is for those images whose source
> is a bitmap. If we want to stick with the Sphinx supported formats,
> we have only two options for bitmaps: jpg or png. We could eventually
> use uuencode or base64 to make sure that the patches won't use
> git binary diff extension
Hi Ted,
Em Thu, 17 Nov 2016 09:52:44 -0500
Theodore Ts'o escreveu:
> On Thu, Nov 17, 2016 at 12:07:15PM +0100, Arnd Bergmann wrote:
> > [adding Linus for clarification]
> >
> > I understood the concern as being about binary files that you cannot
> > modify with classic 'patch', which is a separ
Em Thu, 17 Nov 2016 13:28:29 +0200
Jani Nikula escreveu:
> On Thu, 17 Nov 2016, Arnd Bergmann wrote:
> > On Wednesday, November 16, 2016 6:26:33 PM CET Mauro Carvalho Chehab wrote:
> >
> >> Em Wed, 16 Nov 2016 17:03:47 +0100
> >> Arnd Bergmann escreveu:
> >>
> >> > On Tuesday, November 8,
Em Thu, 17 Nov 2016 12:07:15 +0100
Arnd Bergmann escreveu:
> On Wednesday, November 16, 2016 6:26:33 PM CET Mauro Carvalho Chehab wrote:
> > Em Wed, 16 Nov 2016 17:03:47 +0100
> > Arnd Bergmann escreveu:
> >
> > > On Tuesday, November 8, 2016 8:50:36 AM CET Mauro Carvalho Chehab wrote:
> >
On Thu, 2016-11-17 at 13:16 -0200, Mauro Carvalho Chehab wrote:
> Hi Ted,
>
> Em Thu, 17 Nov 2016 09:52:44 -0500
> Theodore Ts'o escreveu:
>
> > On Thu, Nov 17, 2016 at 12:07:15PM +0100, Arnd Bergmann wrote:
> > > [adding Linus for clarification]
> > >
> > > I understood the concern as being ab
On Thu, Nov 17, 2016 at 8:02 AM, Linus Torvalds
wrote:
>
> No. That is how I *noticed* the issue. Those stupid pdf binary files
> have been around forever, I just didn't notice until the Fedora people
> started complaining about the patches.
Side note: my release patches these days enable both "-
On Thu, 17 Nov 2016, Arnd Bergmann wrote:
> On Wednesday, November 16, 2016 6:26:33 PM CET Mauro Carvalho Chehab wrote:
>> Em Wed, 16 Nov 2016 17:03:47 +0100
>> Arnd Bergmann escreveu:
>>
>> > On Tuesday, November 8, 2016 8:50:36 AM CET Mauro Carvalho Chehab wrote:
>> > > It basically calls Imag
On Wednesday, November 16, 2016 6:26:33 PM CET Mauro Carvalho Chehab wrote:
> Em Wed, 16 Nov 2016 17:03:47 +0100
> Arnd Bergmann escreveu:
>
> > On Tuesday, November 8, 2016 8:50:36 AM CET Mauro Carvalho Chehab wrote:
> > > It basically calls ImageMagick "convert" tool for all png and
> > > pdf f
Hi Arnd,
Em Wed, 16 Nov 2016 17:03:47 +0100
Arnd Bergmann escreveu:
> On Tuesday, November 8, 2016 8:50:36 AM CET Mauro Carvalho Chehab wrote:
> > It basically calls ImageMagick "convert" tool for all png and
> > pdf files currently at the documentation (they're all at media,
> > ATM).
>
> It
On Tuesday, November 8, 2016 8:50:36 AM CET Mauro Carvalho Chehab wrote:
> > [...]
> > > And it may even require "--shell-escape" to be passed at the xelatex
> > > call if inkscape is not in the path, with seems to be a strong
> > > indication that SVG support is not native to texlive, but, instead
Em Sun, 13 Nov 2016 14:00:27 -0700
Jonathan Corbet escreveu:
> On Mon, 7 Nov 2016 09:46:48 -0200
> Mauro Carvalho Chehab wrote:
>
> > When running LaTeX in interactive mode, building just the media
> > PDF file with:
> >
> > $ cls;make cleandocs; make SPHINXOPTS="-j5" DOCBOOKS=""
> > SPHI
Em Sun, 13 Nov 2016 12:52:50 -0700
Jonathan Corbet escreveu:
> On Mon, 7 Nov 2016 07:55:24 -0200
> Mauro Carvalho Chehab wrote:
>
> > So, we have a few alternatives:
> >
> > 1) copy (or symlink) all rst files to Documentation/output (or to the
> >build dir specified via O= directive) and g
On Mon, 7 Nov 2016 09:46:48 -0200
Mauro Carvalho Chehab wrote:
> When running LaTeX in interactive mode, building just the media
> PDF file with:
>
> $ cls;make cleandocs; make SPHINXOPTS="-j5" DOCBOOKS=""
> SPHINXDIRS=media latexdocs
> $ PDFLATEX=xelatex LATEXOPTS="-interaction=in
On Mon, 7 Nov 2016 07:55:24 -0200
Mauro Carvalho Chehab wrote:
> So, we have a few alternatives:
>
> 1) copy (or symlink) all rst files to Documentation/output (or to the
>build dir specified via O= directive) and generate the *.pdf there,
>and produce those converted images via Makefile
Am 11.11.2016 um 12:22 schrieb Jani Nikula :
> On Thu, 10 Nov 2016, Jani Nikula wrote:
>> On Thu, 10 Nov 2016, Markus Heiser wrote:
>>> Could this POC persuade you, if so, I send a more elaborate RFC,
>>> what do you think about?
>>
>> Sorry, I do not wish to be part of this.
>
> That was unc
On Thu, 10 Nov 2016, Jani Nikula wrote:
> On Thu, 10 Nov 2016, Markus Heiser wrote:
>> Could this POC persuade you, if so, I send a more elaborate RFC,
>> what do you think about?
>
> Sorry, I do not wish to be part of this.
That was uncalled for, apologies.
Like I said, I don't think this is t
Em Wed, 09 Nov 2016 13:58:12 +0200
Jani Nikula escreveu:
> On Wed, 09 Nov 2016, Markus Heiser wrote:
> > Am 09.11.2016 um 12:16 schrieb Jani Nikula :
> >>> So I vote for :
> >>>
> 1) copy (or symlink) all rst files to Documentation/output (or to the
> build dir specified via O= di
On Thu, 10 Nov 2016, Markus Heiser wrote:
> Could this POC persuade you, if so, I send a more elaborate RFC,
> what do you think about?
Sorry, I do not wish to be part of this.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line "unsubs
On 09.11.2016 12:58, Jani Nikula wrote:
> On Wed, 09 Nov 2016, Markus Heiser wrote:
>> Am 09.11.2016 um 12:16 schrieb Jani Nikula :
So I vote for :
> 1) copy (or symlink) all rst files to Documentation/output (or to the
> build dir specified via O= directive) and generate the *
Em Mon, 07 Nov 2016 12:53:55 +0200
Jani Nikula escreveu:
> On Mon, 07 Nov 2016, Mauro Carvalho Chehab wrote:
> > Hi Jon,
> >
> > I'm trying to sort out the next steps to do after KS, with regards to
> > images included on RST files.
> >
> > The issue is that Sphinx image support highly depends o
On Wed, 09 Nov 2016, Markus Heiser wrote:
> Am 09.11.2016 um 12:16 schrieb Jani Nikula :
>>> So I vote for :
>>>
1) copy (or symlink) all rst files to Documentation/output (or to the
build dir specified via O= directive) and generate the *.pdf there,
and produce those converted ima
On Wed, 09 Nov 2016, Mauro Carvalho Chehab wrote:
> Em Wed, 09 Nov 2016 13:16:55 +0200
> Jani Nikula escreveu:
>
>> >> 1) copy (or symlink) all rst files to Documentation/output (or to the
>> >> build dir specified via O= directive) and generate the *.pdf there,
>> >> and produce those converte
Em Wed, 09 Nov 2016 13:16:55 +0200
Jani Nikula escreveu:
> >> 1) copy (or symlink) all rst files to Documentation/output (or to the
> >> build dir specified via O= directive) and generate the *.pdf there,
> >> and produce those converted images via Makefile.;
>
> We're supposed to solve prob
Am 09.11.2016 um 12:16 schrieb Jani Nikula :
>> So I vote for :
>>
>>> 1) copy (or symlink) all rst files to Documentation/output (or to the
>>> build dir specified via O= directive) and generate the *.pdf there,
>>> and produce those converted images via Makefile.;
>
> We're supposed to solve p
On Wed, 09 Nov 2016, Markus Heiser wrote:
> Am 07.11.2016 um 18:01 schrieb Josh Triplett :
>
>> On Mon, Nov 07, 2016 at 07:55:24AM -0200, Mauro Carvalho Chehab wrote:
>>> 2) add an Sphinx extension that would internally call ImageMagick and/or
>>> inkscape to convert the bitmap;
>>
>> This seems
Am 07.11.2016 um 18:01 schrieb Josh Triplett :
> On Mon, Nov 07, 2016 at 07:55:24AM -0200, Mauro Carvalho Chehab wrote:
>> 2) add an Sphinx extension that would internally call ImageMagick and/or
>> inkscape to convert the bitmap;
>
> This seems sensible; Sphinx should directly handle the sourc
Em Mon, 7 Nov 2016 09:05:05 -0800
Josh Triplett escreveu:
> On Mon, Nov 07, 2016 at 09:46:48AM -0200, Mauro Carvalho Chehab wrote:
> > That's said, PNG also doesn't seem to work fine on Sphinx 1.4.x.
> >
> > On my tests, I installed *all* texlive extensions on Fedora 24, to
> > be sure that the
On Mon, Nov 07, 2016 at 07:55:24AM -0200, Mauro Carvalho Chehab wrote:
> 2) add an Sphinx extension that would internally call ImageMagick and/or
>inkscape to convert the bitmap;
This seems sensible; Sphinx should directly handle the source format we
want to use for images/diagrams.
> 3) if p
On Mon, Nov 07, 2016 at 09:46:48AM -0200, Mauro Carvalho Chehab wrote:
> That's said, PNG also doesn't seem to work fine on Sphinx 1.4.x.
>
> On my tests, I installed *all* texlive extensions on Fedora 24, to
> be sure that the issue is not the lack of some extension[1], with:
>
> # dnf ins
Em Mon, 07 Nov 2016 12:53:55 +0200
Jani Nikula escreveu:
> On Mon, 07 Nov 2016, Mauro Carvalho Chehab wrote:
> > Hi Jon,
> >
> > I'm trying to sort out the next steps to do after KS, with regards to
> > images included on RST files.
> >
> > The issue is that Sphinx image support highly depends o
On Mon, 07 Nov 2016, Mauro Carvalho Chehab wrote:
> Hi Jon,
>
> I'm trying to sort out the next steps to do after KS, with regards to
> images included on RST files.
>
> The issue is that Sphinx image support highly depends on the output
> format. Also, despite TexLive support for svg and png imag
Hi Jon,
I'm trying to sort out the next steps to do after KS, with regards to
images included on RST files.
The issue is that Sphinx image support highly depends on the output
format. Also, despite TexLive support for svg and png images[1], Sphinx
doesn't produce the right LaTeX commands to use s
51 matches
Mail list logo
