Re: [FFmpeg-devel] [PATCH] conversion of FFV1 specification from lyx to markdown

[Michael Niedermayer]

On Tue, Jul 21, 2015 at 10:37:30AM -0400, Dave Rice wrote:
> 
> > On Jul 21, 2015, at 10:24 AM, Michael Niedermayer  
> > wrote:
> > 
> > On Mon, Jul 20, 2015 at 11:55:41PM -0400, Dave Rice wrote:
> >> 
> >>> On Jul 20, 2015, at 8:52 PM, Michael Niedermayer  
> >>> wrote:
> >>> 
> >>> On Tue, Jul 21, 2015 at 02:14:11AM +0200, Michael Niedermayer wrote:
> >>> [...]
>  ill take another quick look and then will probably push your changes
>  its probably easier to work on top of it then wait with pushing until
>  its perfect
> >>> 
> >>> pushed it
> >>> 
> >>> btw please remove trailing whitespace unless some of it is required
> >>> for the formating or something
> >> 
> >> Send this pull request to clean up white spaces, indentation, and trailing 
> >> slashes. https://github.com/FFmpeg/FFV1/pull/12
> >> 
> >>> also, it seems github doesnt render all parts of the file well, some
> >>> look quite broken (found by jamrial)
> >> 
> >> Github's markdown rendering is a little different than pandoc's rendering. 
> >> Some table updates were done here: https://github.com/FFmpeg/FFV1/pull/11 
> >> . There's still the header which 
> >> starts with percent signs, this is a workaround to get pandoc to render 
> >> that as a header but to not include it within the table of contents.
> >> 
> >> Unless I'm missing something, Github doesn't seem to support rendering 
> >> latex style equations in markdown (although pandoc does) so we may not be 
> >> able to have a markdown that can be fully rendered by Github alone (unless 
> >> we remove the need for latex). Perhaps the ffv1.md could occasionally be 
> >> rendered (via the makefile) with the outputs updated on ffmpeg.org 
> >> . Then within the README of the FFV1 repo we could 
> >> link to the rendered copy on ffmpeg.org .
> > 
> > ive uploaded a temporary version to
> > http://ffmpeg.org/~michael/ffv1-markdown/ffv1.html
> > http://ffmpeg.org/~michael/ffv1-markdown/ffv1.pdf 
> > 
> 
> Thanks.
> 

> > these are created with pandoc 1.13.2.1 locally
> > the huffman/suffix/example tables still are wrong, that could be
> > worked aroun by placing one of the magic non breaking or whatever spaces
> > before the tables
> 
> I'm not sure I understand why they are 'wrong'.

ive the suspicion something is smart and associates the title
with teh tables by putting them below the tables (which is not
uncommon for tables to have the associated text below them)
but this is guessing by someone who knows 0 about this stuff
so iam likely wrong

[...]

-- 
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

You can kill me, but you cannot change the truth.


signature.asc
Description: Digital signature
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH] conversion of FFV1 specification from lyx to markdown

[Dave Rice]

> On Jul 21, 2015, at 10:24 AM, Michael Niedermayer  
> wrote:
> 
> On Mon, Jul 20, 2015 at 11:55:41PM -0400, Dave Rice wrote:
>> 
>>> On Jul 20, 2015, at 8:52 PM, Michael Niedermayer  
>>> wrote:
>>> 
>>> On Tue, Jul 21, 2015 at 02:14:11AM +0200, Michael Niedermayer wrote:
>>> [...]
 ill take another quick look and then will probably push your changes
 its probably easier to work on top of it then wait with pushing until
 its perfect
>>> 
>>> pushed it
>>> 
>>> btw please remove trailing whitespace unless some of it is required
>>> for the formating or something
>> 
>> Send this pull request to clean up white spaces, indentation, and trailing 
>> slashes. https://github.com/FFmpeg/FFV1/pull/12
>> 
>>> also, it seems github doesnt render all parts of the file well, some
>>> look quite broken (found by jamrial)
>> 
>> Github's markdown rendering is a little different than pandoc's rendering. 
>> Some table updates were done here: https://github.com/FFmpeg/FFV1/pull/11 
>> . There's still the header which 
>> starts with percent signs, this is a workaround to get pandoc to render that 
>> as a header but to not include it within the table of contents.
>> 
>> Unless I'm missing something, Github doesn't seem to support rendering latex 
>> style equations in markdown (although pandoc does) so we may not be able to 
>> have a markdown that can be fully rendered by Github alone (unless we remove 
>> the need for latex). Perhaps the ffv1.md could occasionally be rendered (via 
>> the makefile) with the outputs updated on ffmpeg.org . 
>> Then within the README of the FFV1 repo we could link to the rendered copy 
>> on ffmpeg.org .
> 
> ive uploaded a temporary version to
> http://ffmpeg.org/~michael/ffv1-markdown/ffv1.html
> http://ffmpeg.org/~michael/ffv1-markdown/ffv1.pdf 
> 

Thanks.

> these are created with pandoc 1.13.2.1 locally
> the huffman/suffix/example tables still are wrong, that could be
> worked aroun by placing one of the magic non breaking or whatever spaces
> before the tables

I'm not sure I understand why they are 'wrong'.

> also the html lost its left border/margin which looks odd

Agreed. For HTML we're using http://elyxer.nongnu.org/lyx.css 
 which uses "margin: 0". For a number of 
reasons I think we'll need to use a custom css, will send a PR for that later.

[...]

Dave

___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH] conversion of FFV1 specification from lyx to markdown

[Michael Niedermayer]

On Mon, Jul 20, 2015 at 11:55:41PM -0400, Dave Rice wrote:
> 
> > On Jul 20, 2015, at 8:52 PM, Michael Niedermayer  
> > wrote:
> > 
> > On Tue, Jul 21, 2015 at 02:14:11AM +0200, Michael Niedermayer wrote:
> > [...]
> >> ill take another quick look and then will probably push your changes
> >> its probably easier to work on top of it then wait with pushing until
> >> its perfect
> > 
> > pushed it
> > 
> > btw please remove trailing whitespace unless some of it is required
> > for the formating or something
> 
> Send this pull request to clean up white spaces, indentation, and trailing 
> slashes. https://github.com/FFmpeg/FFV1/pull/12
> 
> > also, it seems github doesnt render all parts of the file well, some
> > look quite broken (found by jamrial)
> 
> Github's markdown rendering is a little different than pandoc's rendering. 
> Some table updates were done here: https://github.com/FFmpeg/FFV1/pull/11 
> . There's still the header which 
> starts with percent signs, this is a workaround to get pandoc to render that 
> as a header but to not include it within the table of contents.
> 
> Unless I'm missing something, Github doesn't seem to support rendering latex 
> style equations in markdown (although pandoc does) so we may not be able to 
> have a markdown that can be fully rendered by Github alone (unless we remove 
> the need for latex). Perhaps the ffv1.md could occasionally be rendered (via 
> the makefile) with the outputs updated on ffmpeg.org . 
> Then within the README of the FFV1 repo we could link to the rendered copy on 
> ffmpeg.org .

ive uploaded a temporary version to
http://ffmpeg.org/~michael/ffv1-markdown/ffv1.html
http://ffmpeg.org/~michael/ffv1-markdown/ffv1.pdf

these are created with pandoc 1.13.2.1 locally
the huffman/suffix/example tables still are wrong, that could be
worked aroun by placing one of the magic non breaking or whatever spaces
before the tables

also the html lost its left border/margin which looks odd

pandoc on the server would be older so i dont think generating it
per cronjob on the server makes much sense ATM

[...]
-- 
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Concerning the gods, I have no means of knowing whether they exist or not
or of what sort they may be, because of the obscurity of the subject, and
the brevity of human life -- Protagoras


signature.asc
Description: Digital signature
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH] conversion of FFV1 specification from lyx to markdown

[Dave Rice]

> On Jul 20, 2015, at 8:52 PM, Michael Niedermayer  
> wrote:
> 
> On Tue, Jul 21, 2015 at 02:14:11AM +0200, Michael Niedermayer wrote:
> [...]
>> ill take another quick look and then will probably push your changes
>> its probably easier to work on top of it then wait with pushing until
>> its perfect
> 
> pushed it
> 
> btw please remove trailing whitespace unless some of it is required
> for the formating or something

Send this pull request to clean up white spaces, indentation, and trailing 
slashes. https://github.com/FFmpeg/FFV1/pull/12

> also, it seems github doesnt render all parts of the file well, some
> look quite broken (found by jamrial)

Github's markdown rendering is a little different than pandoc's rendering. Some 
table updates were done here: https://github.com/FFmpeg/FFV1/pull/11 
. There's still the header which starts 
with percent signs, this is a workaround to get pandoc to render that as a 
header but to not include it within the table of contents.

Unless I'm missing something, Github doesn't seem to support rendering latex 
style equations in markdown (although pandoc does) so we may not be able to 
have a markdown that can be fully rendered by Github alone (unless we remove 
the need for latex). Perhaps the ffv1.md could occasionally be rendered (via 
the makefile) with the outputs updated on ffmpeg.org . Then 
within the README of the FFV1 repo we could link to the rendered copy on 
ffmpeg.org .

[...]

Best Regards,
Dave Rice
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH] conversion of FFV1 specification from lyx to markdown

[Michael Niedermayer]

On Tue, Jul 21, 2015 at 02:14:11AM +0200, Michael Niedermayer wrote:
[...]
> ill take another quick look and then will probably push your changes
> its probably easier to work on top of it then wait with pushing until
> its perfect

pushed it

btw please remove trailing whitespace unless some of it is required
for the formating or something

also, it seems github doesnt render all parts of the file well, some
look quite broken (found by jamrial)

[...]

-- 
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

The worst form of inequality is to try to make unequal things equal.
-- Aristotle


signature.asc
Description: Digital signature
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH] conversion of FFV1 specification from lyx to markdown

[Michael Niedermayer]

On Mon, Jul 20, 2015 at 02:18:18PM -0400, Dave Rice wrote:
> Hi Michael,
> 
> > On Jul 20, 2015, at 7:52 AM, Michael Niedermayer  
> > wrote:
> > 
> > On Sat, Jul 18, 2015 at 11:23:16AM -0400, Dave Rice wrote:
> >> 
> >>> On Jul 10, 2015, at 4:55 PM, Michael Niedermayer  
> >>> wrote:
> >>> 
> >>> On Fri, Jul 10, 2015 at 04:19:41PM -0400, Dave Rice wrote:
>  
> > On Jul 10, 2015, at 3:51 PM, Michael Niedermayer 
> >  wrote:
> > 
> > On Fri, Jul 10, 2015 at 03:47:45PM -0400, Dave Rice wrote:
> >> 
> >>> On Jul 10, 2015, at 2:06 PM, Michael Niedermayer 
> >>>  wrote:
> >>> 
> >>> On Fri, Jul 10, 2015 at 07:51:20PM +0200, Michael Niedermayer wrote:
>  On Fri, Jul 10, 2015 at 07:47:46PM +0200, Michael Niedermayer wrote:
> > On Fri, Jul 10, 2015 at 11:52:24AM +0200, Michael Niedermayer wrote:
> >> On Thu, Jul 09, 2015 at 02:14:36PM -0400, Dave Rice wrote:
> >>> 
>  On Jul 9, 2015, at 1:53 PM, Michael Niedermayer 
>   wrote:
>  
>  On Tue, Jul 07, 2015 at 11:03:39AM -0400, Dave Rice wrote:
> > Hi,
> > 
> >> On Jul 7, 2015, at 10:35 AM, Michael Niedermayer 
> >>  wrote:
> >> 
> >> On Thu, Jul 02, 2015 at 09:50:21AM -0400, Dave Rice wrote:
> >>> Hi all,
> >>> Last month I posted a draft of the FFV1 specification 
> >>> formatted in Markdown [1], whereas it currently lives in lyx. 
> >>> From that post there were responses in favor of the use of 
> >>> Markdown formatting and suggestions to not use mathml within 
> >>> a draft targeting an RFC specification and suggestions to 
> >>> update a few urls. I propose to proceed with a format 
> >>> conversion of the FFV1 specification from lyx to Markdown and 
> >>> then I'll file tickets or patches to explore simplifying the 
> >>> mathml expressions and updating the urls. Attached is a patch 
> >>> to convert the formatting (but not meaning) of the FFV1 
> >>> specification from lyx to markdown.
> >>> 
> >>> Best Regards,
> >>> Dave Rice
> >>> 
> >>> [1] 
> >>> http://comments.gmane.org/gmane.comp.video.ffmpeg.devel/193851
> >>> 
> >> 
> >> how can this be edited and converted ?
> > 
> > Via pandoc you can get outputs that are close to the current 
> > ffv1.html and ffv1.pdf outputs of ffv1.lyx.
> > 
> > pandoc --mathml -s --number-sections ../ffv1.md -c lyx.css -o 
> > ffv1.html
> > pandoc -s --number-sections ../ffv1.md --latex-engine=xelatex 
> > -V geometry:margin=1in -o ffv1.pdf
> > 
> > I can move this info to a readme.
>  
>  please do
> >>> 
> >>> Sure. Would you prefer a patch on ffmpeg-devel or a PR in github?
> >> 
> >> whatever you prefer
> > 
> > generated files like pdf should not be checked into git.
> > instead add a Makefile to generate them, so a simple
> > make
> > or
> > make ffv1.pdf
> > generates the file
>  
>  also the readme should document which version of markdown/pandoc
>  this needs
>  and something should check for that version ideally so the user
>  is nt left wondering why "make" produces broken tables
> >>> 
> >>> reviewing the pull req
> >>> 
> >>> The conventions section 3.
> >>> lacks vertical alignment
> >> 
> >> Fixed in 
> >> https://github.com/MediaArea/FFV1/commit/d25fb39f7514547f72cbc13ef3851f3c9d9c0c5f
> >> 
> >>> theres an empty line after
> >>> for(i=0;i >> 
> >> Fixed in 
> >> https://github.com/MediaArea/FFV1/commit/1291e6c3e90ea6816b543a9e12c08d1cbbc1f31c
> >> 
> > 
> >>> 4.6.2.5:
> >>> log2_run[41]={JPEGLS.
> >>> 0,0,0,0,1,1,1,1,
> >>> 
> >>> that JPEGLS is supposed to be a link/reference/whatever but its a
> >>> litteral word
> >> 
> >> I'm having trouble getting a footnote to work within a codeblock. It 
> >> is feasible to use this footnote in a reference to JPEGLS in a 
> >> sentence above the codeblock?
> > 
> > of course
> > whatever works
>  
>  I don't understand the relationship between the function and the 
>  reference to JPEG-LS. I could simply move the footnote reference to 
>  JPEGLS to outside of the codeblock, but it would be better to also 
>  explain the relationship at the same time. Could you provide some 
>  background as to why JPEGLS is referenced here.
> >>> 
> >>> This table is also used by jpegls, see ff_log2_run in libavcodec
> >>> 
> >>> 
> >>> some othe

Re: [FFmpeg-devel] [PATCH] conversion of FFV1 specification from lyx to markdown

[Dave Rice]

Hi Michael,

> On Jul 20, 2015, at 7:52 AM, Michael Niedermayer  
> wrote:
> 
> On Sat, Jul 18, 2015 at 11:23:16AM -0400, Dave Rice wrote:
>> 
>>> On Jul 10, 2015, at 4:55 PM, Michael Niedermayer  
>>> wrote:
>>> 
>>> On Fri, Jul 10, 2015 at 04:19:41PM -0400, Dave Rice wrote:
 
> On Jul 10, 2015, at 3:51 PM, Michael Niedermayer  
> wrote:
> 
> On Fri, Jul 10, 2015 at 03:47:45PM -0400, Dave Rice wrote:
>> 
>>> On Jul 10, 2015, at 2:06 PM, Michael Niedermayer 
>>>  wrote:
>>> 
>>> On Fri, Jul 10, 2015 at 07:51:20PM +0200, Michael Niedermayer wrote:
 On Fri, Jul 10, 2015 at 07:47:46PM +0200, Michael Niedermayer wrote:
> On Fri, Jul 10, 2015 at 11:52:24AM +0200, Michael Niedermayer wrote:
>> On Thu, Jul 09, 2015 at 02:14:36PM -0400, Dave Rice wrote:
>>> 
 On Jul 9, 2015, at 1:53 PM, Michael Niedermayer  
 wrote:
 
 On Tue, Jul 07, 2015 at 11:03:39AM -0400, Dave Rice wrote:
> Hi,
> 
>> On Jul 7, 2015, at 10:35 AM, Michael Niedermayer 
>>  wrote:
>> 
>> On Thu, Jul 02, 2015 at 09:50:21AM -0400, Dave Rice wrote:
>>> Hi all,
>>> Last month I posted a draft of the FFV1 specification formatted 
>>> in Markdown [1], whereas it currently lives in lyx. From that 
>>> post there were responses in favor of the use of Markdown 
>>> formatting and suggestions to not use mathml within a draft 
>>> targeting an RFC specification and suggestions to update a few 
>>> urls. I propose to proceed with a format conversion of the FFV1 
>>> specification from lyx to Markdown and then I'll file tickets 
>>> or patches to explore simplifying the mathml expressions and 
>>> updating the urls. Attached is a patch to convert the 
>>> formatting (but not meaning) of the FFV1 specification from lyx 
>>> to markdown.
>>> 
>>> Best Regards,
>>> Dave Rice
>>> 
>>> [1] 
>>> http://comments.gmane.org/gmane.comp.video.ffmpeg.devel/193851
>>> 
>> 
>> how can this be edited and converted ?
> 
> Via pandoc you can get outputs that are close to the current 
> ffv1.html and ffv1.pdf outputs of ffv1.lyx.
> 
> pandoc --mathml -s --number-sections ../ffv1.md -c lyx.css -o 
> ffv1.html
> pandoc -s --number-sections ../ffv1.md --latex-engine=xelatex -V 
> geometry:margin=1in -o ffv1.pdf
> 
> I can move this info to a readme.
 
 please do
>>> 
>>> Sure. Would you prefer a patch on ffmpeg-devel or a PR in github?
>> 
>> whatever you prefer
> 
> generated files like pdf should not be checked into git.
> instead add a Makefile to generate them, so a simple
> make
> or
> make ffv1.pdf
> generates the file
 
 also the readme should document which version of markdown/pandoc
 this needs
 and something should check for that version ideally so the user
 is nt left wondering why "make" produces broken tables
>>> 
>>> reviewing the pull req
>>> 
>>> The conventions section 3.
>>> lacks vertical alignment
>> 
>> Fixed in 
>> https://github.com/MediaArea/FFV1/commit/d25fb39f7514547f72cbc13ef3851f3c9d9c0c5f
>> 
>>> theres an empty line after
>>> for(i=0;i> 
>> Fixed in 
>> https://github.com/MediaArea/FFV1/commit/1291e6c3e90ea6816b543a9e12c08d1cbbc1f31c
>> 
> 
>>> 4.6.2.5:
>>> log2_run[41]={JPEGLS.
>>> 0,0,0,0,1,1,1,1,
>>> 
>>> that JPEGLS is supposed to be a link/reference/whatever but its a
>>> litteral word
>> 
>> I'm having trouble getting a footnote to work within a codeblock. It is 
>> feasible to use this footnote in a reference to JPEGLS in a sentence 
>> above the codeblock?
> 
> of course
> whatever works
 
 I don't understand the relationship between the function and the reference 
 to JPEG-LS. I could simply move the footnote reference to JPEGLS to 
 outside of the codeblock, but it would be better to also explain the 
 relationship at the same time. Could you provide some background as to why 
 JPEGLS is referenced here.
>>> 
>>> This table is also used by jpegls, see ff_log2_run in libavcodec
>>> 
>>> 
>>> some other things
>>> nested TOC and numbering in TOC is lost
>> 
>> Switching here to use pandoc's TOC features instead of maintaining them 
>> manually. 
>> https://github.com/MediaArea/FFV1/commit/64f643534c10ac6d680b63c75fa1b7cb670bd9c4
>> 
>>> in "4.6.1.4 State transition table" there should be a newline
>>> b

Re: [FFmpeg-devel] [PATCH] conversion of FFV1 specification from lyx to markdown

[Michael Niedermayer]

On Sat, Jul 18, 2015 at 11:23:16AM -0400, Dave Rice wrote:
> 
> > On Jul 10, 2015, at 4:55 PM, Michael Niedermayer  
> > wrote:
> > 
> > On Fri, Jul 10, 2015 at 04:19:41PM -0400, Dave Rice wrote:
> >> 
> >>> On Jul 10, 2015, at 3:51 PM, Michael Niedermayer  
> >>> wrote:
> >>> 
> >>> On Fri, Jul 10, 2015 at 03:47:45PM -0400, Dave Rice wrote:
>  
> > On Jul 10, 2015, at 2:06 PM, Michael Niedermayer 
> >  wrote:
> > 
> > On Fri, Jul 10, 2015 at 07:51:20PM +0200, Michael Niedermayer wrote:
> >> On Fri, Jul 10, 2015 at 07:47:46PM +0200, Michael Niedermayer wrote:
> >>> On Fri, Jul 10, 2015 at 11:52:24AM +0200, Michael Niedermayer wrote:
>  On Thu, Jul 09, 2015 at 02:14:36PM -0400, Dave Rice wrote:
> > 
> >> On Jul 9, 2015, at 1:53 PM, Michael Niedermayer  
> >> wrote:
> >> 
> >> On Tue, Jul 07, 2015 at 11:03:39AM -0400, Dave Rice wrote:
> >>> Hi,
> >>> 
>  On Jul 7, 2015, at 10:35 AM, Michael Niedermayer 
>   wrote:
>  
>  On Thu, Jul 02, 2015 at 09:50:21AM -0400, Dave Rice wrote:
> > Hi all,
> > Last month I posted a draft of the FFV1 specification formatted 
> > in Markdown [1], whereas it currently lives in lyx. From that 
> > post there were responses in favor of the use of Markdown 
> > formatting and suggestions to not use mathml within a draft 
> > targeting an RFC specification and suggestions to update a few 
> > urls. I propose to proceed with a format conversion of the FFV1 
> > specification from lyx to Markdown and then I'll file tickets 
> > or patches to explore simplifying the mathml expressions and 
> > updating the urls. Attached is a patch to convert the 
> > formatting (but not meaning) of the FFV1 specification from lyx 
> > to markdown.
> > 
> > Best Regards,
> > Dave Rice
> > 
> > [1] 
> > http://comments.gmane.org/gmane.comp.video.ffmpeg.devel/193851
> > 
>  
>  how can this be edited and converted ?
> >>> 
> >>> Via pandoc you can get outputs that are close to the current 
> >>> ffv1.html and ffv1.pdf outputs of ffv1.lyx.
> >>> 
> >>> pandoc --mathml -s --number-sections ../ffv1.md -c lyx.css -o 
> >>> ffv1.html
> >>> pandoc -s --number-sections ../ffv1.md --latex-engine=xelatex -V 
> >>> geometry:margin=1in -o ffv1.pdf
> >>> 
> >>> I can move this info to a readme.
> >> 
> >> please do
> > 
> > Sure. Would you prefer a patch on ffmpeg-devel or a PR in github?
>  
>  whatever you prefer
> >>> 
> >>> generated files like pdf should not be checked into git.
> >>> instead add a Makefile to generate them, so a simple
> >>> make
> >>> or
> >>> make ffv1.pdf
> >>> generates the file
> >> 
> >> also the readme should document which version of markdown/pandoc
> >> this needs
> >> and something should check for that version ideally so the user
> >> is nt left wondering why "make" produces broken tables
> > 
> > reviewing the pull req
> > 
> > The conventions section 3.
> > lacks vertical alignment
>  
>  Fixed in 
>  https://github.com/MediaArea/FFV1/commit/d25fb39f7514547f72cbc13ef3851f3c9d9c0c5f
>  
> > theres an empty line after
> >  for(i=0;i  
>  Fixed in 
>  https://github.com/MediaArea/FFV1/commit/1291e6c3e90ea6816b543a9e12c08d1cbbc1f31c
>  
> >>> 
> > 4.6.2.5:
> >  log2_run[41]={JPEGLS.
> >  0,0,0,0,1,1,1,1,
> > 
> > that JPEGLS is supposed to be a link/reference/whatever but its a
> > litteral word
>  
>  I'm having trouble getting a footnote to work within a codeblock. It is 
>  feasible to use this footnote in a reference to JPEGLS in a sentence 
>  above the codeblock?
> >>> 
> >>> of course
> >>> whatever works
> >> 
> >> I don't understand the relationship between the function and the reference 
> >> to JPEG-LS. I could simply move the footnote reference to JPEGLS to 
> >> outside of the codeblock, but it would be better to also explain the 
> >> relationship at the same time. Could you provide some background as to why 
> >> JPEGLS is referenced here.
> > 
> > This table is also used by jpegls, see ff_log2_run in libavcodec
> > 
> > 
> > some other things
> > nested TOC and numbering in TOC is lost
> 
> Switching here to use pandoc's TOC features instead of maintaining them 
> manually. 
> https://github.com/MediaArea/FFV1/commit/64f643534c10ac6d680b63c75fa1b7cb670bd9c4
> 
> > in "4.6.1.4 State transition table" there should be a newline
> > before one_statei = ...
> 
> Added here: 
> https://github.com/MediaArea/FFV1/commit

Re: [FFmpeg-devel] [PATCH] conversion of FFV1 specification from lyx to markdown

[Dave Rice]

> On Jul 10, 2015, at 4:55 PM, Michael Niedermayer  
> wrote:
> 
> On Fri, Jul 10, 2015 at 04:19:41PM -0400, Dave Rice wrote:
>> 
>>> On Jul 10, 2015, at 3:51 PM, Michael Niedermayer  
>>> wrote:
>>> 
>>> On Fri, Jul 10, 2015 at 03:47:45PM -0400, Dave Rice wrote:
 
> On Jul 10, 2015, at 2:06 PM, Michael Niedermayer  
> wrote:
> 
> On Fri, Jul 10, 2015 at 07:51:20PM +0200, Michael Niedermayer wrote:
>> On Fri, Jul 10, 2015 at 07:47:46PM +0200, Michael Niedermayer wrote:
>>> On Fri, Jul 10, 2015 at 11:52:24AM +0200, Michael Niedermayer wrote:
 On Thu, Jul 09, 2015 at 02:14:36PM -0400, Dave Rice wrote:
> 
>> On Jul 9, 2015, at 1:53 PM, Michael Niedermayer  
>> wrote:
>> 
>> On Tue, Jul 07, 2015 at 11:03:39AM -0400, Dave Rice wrote:
>>> Hi,
>>> 
 On Jul 7, 2015, at 10:35 AM, Michael Niedermayer 
  wrote:
 
 On Thu, Jul 02, 2015 at 09:50:21AM -0400, Dave Rice wrote:
> Hi all,
> Last month I posted a draft of the FFV1 specification formatted 
> in Markdown [1], whereas it currently lives in lyx. From that 
> post there were responses in favor of the use of Markdown 
> formatting and suggestions to not use mathml within a draft 
> targeting an RFC specification and suggestions to update a few 
> urls. I propose to proceed with a format conversion of the FFV1 
> specification from lyx to Markdown and then I'll file tickets or 
> patches to explore simplifying the mathml expressions and 
> updating the urls. Attached is a patch to convert the formatting 
> (but not meaning) of the FFV1 specification from lyx to markdown.
> 
> Best Regards,
> Dave Rice
> 
> [1] http://comments.gmane.org/gmane.comp.video.ffmpeg.devel/193851
> 
 
 how can this be edited and converted ?
>>> 
>>> Via pandoc you can get outputs that are close to the current 
>>> ffv1.html and ffv1.pdf outputs of ffv1.lyx.
>>> 
>>> pandoc --mathml -s --number-sections ../ffv1.md -c lyx.css -o 
>>> ffv1.html
>>> pandoc -s --number-sections ../ffv1.md --latex-engine=xelatex -V 
>>> geometry:margin=1in -o ffv1.pdf
>>> 
>>> I can move this info to a readme.
>> 
>> please do
> 
> Sure. Would you prefer a patch on ffmpeg-devel or a PR in github?
 
 whatever you prefer
>>> 
>>> generated files like pdf should not be checked into git.
>>> instead add a Makefile to generate them, so a simple
>>> make
>>> or
>>> make ffv1.pdf
>>> generates the file
>> 
>> also the readme should document which version of markdown/pandoc
>> this needs
>> and something should check for that version ideally so the user
>> is nt left wondering why "make" produces broken tables
> 
> reviewing the pull req
> 
> The conventions section 3.
> lacks vertical alignment
 
 Fixed in 
 https://github.com/MediaArea/FFV1/commit/d25fb39f7514547f72cbc13ef3851f3c9d9c0c5f
 
> theres an empty line after
>  for(i=0;i>>> 
 Fixed in 
 https://github.com/MediaArea/FFV1/commit/1291e6c3e90ea6816b543a9e12c08d1cbbc1f31c
 
>>> 
> 4.6.2.5:
>  log2_run[41]={JPEGLS.
>  0,0,0,0,1,1,1,1,
> 
> that JPEGLS is supposed to be a link/reference/whatever but its a
> litteral word
 
 I'm having trouble getting a footnote to work within a codeblock. It is 
 feasible to use this footnote in a reference to JPEGLS in a sentence above 
 the codeblock?
>>> 
>>> of course
>>> whatever works
>> 
>> I don't understand the relationship between the function and the reference 
>> to JPEG-LS. I could simply move the footnote reference to JPEGLS to outside 
>> of the codeblock, but it would be better to also explain the relationship at 
>> the same time. Could you provide some background as to why JPEGLS is 
>> referenced here.
> 
> This table is also used by jpegls, see ff_log2_run in libavcodec
> 
> 
> some other things
> nested TOC and numbering in TOC is lost

Switching here to use pandoc's TOC features instead of maintaining them 
manually. 
https://github.com/MediaArea/FFV1/commit/64f643534c10ac6d680b63c75fa1b7cb670bd9c4

> in "4.6.1.4 State transition table" there should be a newline
> before one_statei = ...

Added here: 
https://github.com/MediaArea/FFV1/commit/701edaf67ad1f0933cac1fc74f4921a209461164

> 4.6.2 Huffman coding mode
> the content and headings seem to mismatch
> the prefix table is above the prefix heading
> the examples empty

Can you review again in git master. I've already made changes in this section 
according to Timothy Gu's comments.

> the stuff inside
> ConfigurationRecord()
> lo

Re: [FFmpeg-devel] [PATCH] conversion of FFV1 specification from lyx to markdown

[Dave Rice]

> On Jul 10, 2015, at 3:51 PM, Michael Niedermayer  
> wrote:
> 
> On Fri, Jul 10, 2015 at 03:47:45PM -0400, Dave Rice wrote:
>> 
>>> On Jul 10, 2015, at 2:06 PM, Michael Niedermayer  
>>> wrote:
>>> 
>>> On Fri, Jul 10, 2015 at 07:51:20PM +0200, Michael Niedermayer wrote:
 On Fri, Jul 10, 2015 at 07:47:46PM +0200, Michael Niedermayer wrote:
> On Fri, Jul 10, 2015 at 11:52:24AM +0200, Michael Niedermayer wrote:
>> On Thu, Jul 09, 2015 at 02:14:36PM -0400, Dave Rice wrote:
>>> 
 On Jul 9, 2015, at 1:53 PM, Michael Niedermayer  
 wrote:
 
 On Tue, Jul 07, 2015 at 11:03:39AM -0400, Dave Rice wrote:
> Hi,
> 
>> On Jul 7, 2015, at 10:35 AM, Michael Niedermayer  
>> wrote:
>> 
>> On Thu, Jul 02, 2015 at 09:50:21AM -0400, Dave Rice wrote:
>>> Hi all,
>>> Last month I posted a draft of the FFV1 specification formatted in 
>>> Markdown [1], whereas it currently lives in lyx. From that post 
>>> there were responses in favor of the use of Markdown formatting and 
>>> suggestions to not use mathml within a draft targeting an RFC 
>>> specification and suggestions to update a few urls. I propose to 
>>> proceed with a format conversion of the FFV1 specification from lyx 
>>> to Markdown and then I'll file tickets or patches to explore 
>>> simplifying the mathml expressions and updating the urls. Attached 
>>> is a patch to convert the formatting (but not meaning) of the FFV1 
>>> specification from lyx to markdown.
>>> 
>>> Best Regards,
>>> Dave Rice
>>> 
>>> [1] http://comments.gmane.org/gmane.comp.video.ffmpeg.devel/193851
>>> 
>> 
>> how can this be edited and converted ?
> 
> Via pandoc you can get outputs that are close to the current 
> ffv1.html and ffv1.pdf outputs of ffv1.lyx.
> 
> pandoc --mathml -s --number-sections ../ffv1.md -c lyx.css -o 
> ffv1.html
> pandoc -s --number-sections ../ffv1.md --latex-engine=xelatex -V 
> geometry:margin=1in -o ffv1.pdf
> 
> I can move this info to a readme.
 
 please do
>>> 
>>> Sure. Would you prefer a patch on ffmpeg-devel or a PR in github?
>> 
>> whatever you prefer
> 
> generated files like pdf should not be checked into git.
> instead add a Makefile to generate them, so a simple
> make
> or
> make ffv1.pdf
> generates the file
 
 also the readme should document which version of markdown/pandoc
 this needs
 and something should check for that version ideally so the user
 is nt left wondering why "make" produces broken tables
>>> 
>>> reviewing the pull req
>>> 
>>> The conventions section 3.
>>> lacks vertical alignment
>> 
>> Fixed in 
>> https://github.com/MediaArea/FFV1/commit/d25fb39f7514547f72cbc13ef3851f3c9d9c0c5f
>> 
>>> theres an empty line after
>>>   for(i=0;i> 
>> Fixed in 
>> https://github.com/MediaArea/FFV1/commit/1291e6c3e90ea6816b543a9e12c08d1cbbc1f31c
>> 
> 
>>> 4.6.2.5:
>>>   log2_run[41]={JPEGLS.
>>>   0,0,0,0,1,1,1,1,
>>> 
>>> that JPEGLS is supposed to be a link/reference/whatever but its a
>>> litteral word
>> 
>> I'm having trouble getting a footnote to work within a codeblock. It is 
>> feasible to use this footnote in a reference to JPEGLS in a sentence above 
>> the codeblock?
> 
> of course
> whatever works

updated here 
https://github.com/MediaArea/FFV1/commit/0c2ab02152e61a5a59e1e003b8c8b7f0acb1a70c
 


[...]

Dave Rice
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH] conversion of FFV1 specification from lyx to markdown

[Michael Niedermayer]

On Fri, Jul 10, 2015 at 04:19:41PM -0400, Dave Rice wrote:
> 
> > On Jul 10, 2015, at 3:51 PM, Michael Niedermayer  
> > wrote:
> > 
> > On Fri, Jul 10, 2015 at 03:47:45PM -0400, Dave Rice wrote:
> >> 
> >>> On Jul 10, 2015, at 2:06 PM, Michael Niedermayer  
> >>> wrote:
> >>> 
> >>> On Fri, Jul 10, 2015 at 07:51:20PM +0200, Michael Niedermayer wrote:
>  On Fri, Jul 10, 2015 at 07:47:46PM +0200, Michael Niedermayer wrote:
> > On Fri, Jul 10, 2015 at 11:52:24AM +0200, Michael Niedermayer wrote:
> >> On Thu, Jul 09, 2015 at 02:14:36PM -0400, Dave Rice wrote:
> >>> 
>  On Jul 9, 2015, at 1:53 PM, Michael Niedermayer  
>  wrote:
>  
>  On Tue, Jul 07, 2015 at 11:03:39AM -0400, Dave Rice wrote:
> > Hi,
> > 
> >> On Jul 7, 2015, at 10:35 AM, Michael Niedermayer 
> >>  wrote:
> >> 
> >> On Thu, Jul 02, 2015 at 09:50:21AM -0400, Dave Rice wrote:
> >>> Hi all,
> >>> Last month I posted a draft of the FFV1 specification formatted 
> >>> in Markdown [1], whereas it currently lives in lyx. From that 
> >>> post there were responses in favor of the use of Markdown 
> >>> formatting and suggestions to not use mathml within a draft 
> >>> targeting an RFC specification and suggestions to update a few 
> >>> urls. I propose to proceed with a format conversion of the FFV1 
> >>> specification from lyx to Markdown and then I'll file tickets or 
> >>> patches to explore simplifying the mathml expressions and 
> >>> updating the urls. Attached is a patch to convert the formatting 
> >>> (but not meaning) of the FFV1 specification from lyx to markdown.
> >>> 
> >>> Best Regards,
> >>> Dave Rice
> >>> 
> >>> [1] http://comments.gmane.org/gmane.comp.video.ffmpeg.devel/193851
> >>> 
> >> 
> >> how can this be edited and converted ?
> > 
> > Via pandoc you can get outputs that are close to the current 
> > ffv1.html and ffv1.pdf outputs of ffv1.lyx.
> > 
> > pandoc --mathml -s --number-sections ../ffv1.md -c lyx.css -o 
> > ffv1.html
> > pandoc -s --number-sections ../ffv1.md --latex-engine=xelatex -V 
> > geometry:margin=1in -o ffv1.pdf
> > 
> > I can move this info to a readme.
>  
>  please do
> >>> 
> >>> Sure. Would you prefer a patch on ffmpeg-devel or a PR in github?
> >> 
> >> whatever you prefer
> > 
> > generated files like pdf should not be checked into git.
> > instead add a Makefile to generate them, so a simple
> > make
> > or
> > make ffv1.pdf
> > generates the file
>  
>  also the readme should document which version of markdown/pandoc
>  this needs
>  and something should check for that version ideally so the user
>  is nt left wondering why "make" produces broken tables
> >>> 
> >>> reviewing the pull req
> >>> 
> >>> The conventions section 3.
> >>> lacks vertical alignment
> >> 
> >> Fixed in 
> >> https://github.com/MediaArea/FFV1/commit/d25fb39f7514547f72cbc13ef3851f3c9d9c0c5f
> >> 
> >>> theres an empty line after
> >>>   for(i=0;i >> 
> >> Fixed in 
> >> https://github.com/MediaArea/FFV1/commit/1291e6c3e90ea6816b543a9e12c08d1cbbc1f31c
> >> 
> > 
> >>> 4.6.2.5:
> >>>   log2_run[41]={JPEGLS.
> >>>   0,0,0,0,1,1,1,1,
> >>> 
> >>> that JPEGLS is supposed to be a link/reference/whatever but its a
> >>> litteral word
> >> 
> >> I'm having trouble getting a footnote to work within a codeblock. It is 
> >> feasible to use this footnote in a reference to JPEGLS in a sentence above 
> >> the codeblock?
> > 
> > of course
> > whatever works
> 
> I don't understand the relationship between the function and the reference to 
> JPEG-LS. I could simply move the footnote reference to JPEGLS to outside of 
> the codeblock, but it would be better to also explain the relationship at the 
> same time. Could you provide some background as to why JPEGLS is referenced 
> here.

This table is also used by jpegls, see ff_log2_run in libavcodec


some other things
nested TOC and numbering in TOC is lost

in "4.6.1.4 State transition table" there should be a newline
before one_statei = ...

4.6.2 Huffman coding mode
the content and headings seem to mismatch
the prefix table is above the prefix heading
the examples empty

the stuff inside
ConfigurationRecord()
lost 1 level indention

in
QuantizationTable( i ) {

scale = 1 is indented diferently than the next line

above review based on "pandoc 1.12.4.2" output, you might want to
update the needed version numbers

"Propering PDF and HTML rendering has been tested with requires pandoc version 
1.13.2.1 and higher."
IMHO something like:
PDF and HTML rendering has been tested with pandoc version ..., some older 
versions are known to produce very poor output, please ensure your pandoc is 

Re: [FFmpeg-devel] [PATCH] conversion of FFV1 specification from lyx to markdown

[Dave Rice]

> On Jul 10, 2015, at 3:51 PM, Michael Niedermayer  
> wrote:
> 
> On Fri, Jul 10, 2015 at 03:47:45PM -0400, Dave Rice wrote:
>> 
>>> On Jul 10, 2015, at 2:06 PM, Michael Niedermayer  
>>> wrote:
>>> 
>>> On Fri, Jul 10, 2015 at 07:51:20PM +0200, Michael Niedermayer wrote:
 On Fri, Jul 10, 2015 at 07:47:46PM +0200, Michael Niedermayer wrote:
> On Fri, Jul 10, 2015 at 11:52:24AM +0200, Michael Niedermayer wrote:
>> On Thu, Jul 09, 2015 at 02:14:36PM -0400, Dave Rice wrote:
>>> 
 On Jul 9, 2015, at 1:53 PM, Michael Niedermayer  
 wrote:
 
 On Tue, Jul 07, 2015 at 11:03:39AM -0400, Dave Rice wrote:
> Hi,
> 
>> On Jul 7, 2015, at 10:35 AM, Michael Niedermayer  
>> wrote:
>> 
>> On Thu, Jul 02, 2015 at 09:50:21AM -0400, Dave Rice wrote:
>>> Hi all,
>>> Last month I posted a draft of the FFV1 specification formatted in 
>>> Markdown [1], whereas it currently lives in lyx. From that post 
>>> there were responses in favor of the use of Markdown formatting and 
>>> suggestions to not use mathml within a draft targeting an RFC 
>>> specification and suggestions to update a few urls. I propose to 
>>> proceed with a format conversion of the FFV1 specification from lyx 
>>> to Markdown and then I'll file tickets or patches to explore 
>>> simplifying the mathml expressions and updating the urls. Attached 
>>> is a patch to convert the formatting (but not meaning) of the FFV1 
>>> specification from lyx to markdown.
>>> 
>>> Best Regards,
>>> Dave Rice
>>> 
>>> [1] http://comments.gmane.org/gmane.comp.video.ffmpeg.devel/193851
>>> 
>> 
>> how can this be edited and converted ?
> 
> Via pandoc you can get outputs that are close to the current 
> ffv1.html and ffv1.pdf outputs of ffv1.lyx.
> 
> pandoc --mathml -s --number-sections ../ffv1.md -c lyx.css -o 
> ffv1.html
> pandoc -s --number-sections ../ffv1.md --latex-engine=xelatex -V 
> geometry:margin=1in -o ffv1.pdf
> 
> I can move this info to a readme.
 
 please do
>>> 
>>> Sure. Would you prefer a patch on ffmpeg-devel or a PR in github?
>> 
>> whatever you prefer
> 
> generated files like pdf should not be checked into git.
> instead add a Makefile to generate them, so a simple
> make
> or
> make ffv1.pdf
> generates the file
 
 also the readme should document which version of markdown/pandoc
 this needs
 and something should check for that version ideally so the user
 is nt left wondering why "make" produces broken tables
>>> 
>>> reviewing the pull req
>>> 
>>> The conventions section 3.
>>> lacks vertical alignment
>> 
>> Fixed in 
>> https://github.com/MediaArea/FFV1/commit/d25fb39f7514547f72cbc13ef3851f3c9d9c0c5f
>> 
>>> theres an empty line after
>>>   for(i=0;i> 
>> Fixed in 
>> https://github.com/MediaArea/FFV1/commit/1291e6c3e90ea6816b543a9e12c08d1cbbc1f31c
>> 
> 
>>> 4.6.2.5:
>>>   log2_run[41]={JPEGLS.
>>>   0,0,0,0,1,1,1,1,
>>> 
>>> that JPEGLS is supposed to be a link/reference/whatever but its a
>>> litteral word
>> 
>> I'm having trouble getting a footnote to work within a codeblock. It is 
>> feasible to use this footnote in a reference to JPEGLS in a sentence above 
>> the codeblock?
> 
> of course
> whatever works

I don't understand the relationship between the function and the reference to 
JPEG-LS. I could simply move the footnote reference to JPEGLS to outside of the 
codeblock, but it would be better to also explain the relationship at the same 
time. Could you provide some background as to why JPEGLS is referenced here.

[...]

Dave Rice
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH] conversion of FFV1 specification from lyx to markdown

[Michael Niedermayer]

On Fri, Jul 10, 2015 at 03:47:45PM -0400, Dave Rice wrote:
> 
> > On Jul 10, 2015, at 2:06 PM, Michael Niedermayer  
> > wrote:
> > 
> > On Fri, Jul 10, 2015 at 07:51:20PM +0200, Michael Niedermayer wrote:
> >> On Fri, Jul 10, 2015 at 07:47:46PM +0200, Michael Niedermayer wrote:
> >>> On Fri, Jul 10, 2015 at 11:52:24AM +0200, Michael Niedermayer wrote:
>  On Thu, Jul 09, 2015 at 02:14:36PM -0400, Dave Rice wrote:
> > 
> >> On Jul 9, 2015, at 1:53 PM, Michael Niedermayer  
> >> wrote:
> >> 
> >> On Tue, Jul 07, 2015 at 11:03:39AM -0400, Dave Rice wrote:
> >>> Hi,
> >>> 
>  On Jul 7, 2015, at 10:35 AM, Michael Niedermayer  
>  wrote:
>  
>  On Thu, Jul 02, 2015 at 09:50:21AM -0400, Dave Rice wrote:
> > Hi all,
> > Last month I posted a draft of the FFV1 specification formatted in 
> > Markdown [1], whereas it currently lives in lyx. From that post 
> > there were responses in favor of the use of Markdown formatting and 
> > suggestions to not use mathml within a draft targeting an RFC 
> > specification and suggestions to update a few urls. I propose to 
> > proceed with a format conversion of the FFV1 specification from lyx 
> > to Markdown and then I'll file tickets or patches to explore 
> > simplifying the mathml expressions and updating the urls. Attached 
> > is a patch to convert the formatting (but not meaning) of the FFV1 
> > specification from lyx to markdown.
> > 
> > Best Regards,
> > Dave Rice
> > 
> > [1] http://comments.gmane.org/gmane.comp.video.ffmpeg.devel/193851
> > 
>  
>  how can this be edited and converted ?
> >>> 
> >>> Via pandoc you can get outputs that are close to the current 
> >>> ffv1.html and ffv1.pdf outputs of ffv1.lyx.
> >>> 
> >>> pandoc --mathml -s --number-sections ../ffv1.md -c lyx.css -o 
> >>> ffv1.html
> >>> pandoc -s --number-sections ../ffv1.md --latex-engine=xelatex -V 
> >>> geometry:margin=1in -o ffv1.pdf
> >>> 
> >>> I can move this info to a readme.
> >> 
> >> please do
> > 
> > Sure. Would you prefer a patch on ffmpeg-devel or a PR in github?
>  
>  whatever you prefer
> >>> 
> >>> generated files like pdf should not be checked into git.
> >>> instead add a Makefile to generate them, so a simple
> >>> make
> >>> or
> >>> make ffv1.pdf
> >>> generates the file
> >> 
> >> also the readme should document which version of markdown/pandoc
> >> this needs
> >> and something should check for that version ideally so the user
> >> is nt left wondering why "make" produces broken tables
> > 
> > reviewing the pull req
> > 
> > The conventions section 3.
> > lacks vertical alignment
> 
> Fixed in 
> https://github.com/MediaArea/FFV1/commit/d25fb39f7514547f72cbc13ef3851f3c9d9c0c5f
> 
> > theres an empty line after
> >for(i=0;i 
> Fixed in 
> https://github.com/MediaArea/FFV1/commit/1291e6c3e90ea6816b543a9e12c08d1cbbc1f31c
> 

> > 4.6.2.5:
> >log2_run[41]={JPEGLS.
> >0,0,0,0,1,1,1,1,
> > 
> > that JPEGLS is supposed to be a link/reference/whatever but its a
> > litteral word
> 
> I'm having trouble getting a footnote to work within a codeblock. It is 
> feasible to use this footnote in a reference to JPEGLS in a sentence above 
> the codeblock?

of course
whatever works


[...]
-- 
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Old school: Use the lowest level language in which you can solve the problem
conveniently.
New school: Use the highest level language in which the latest supercomputer
can solve the problem without the user falling asleep waiting.


signature.asc
Description: Digital signature
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH] conversion of FFV1 specification from lyx to markdown

[Dave Rice]

> On Jul 10, 2015, at 2:06 PM, Michael Niedermayer  
> wrote:
> 
> On Fri, Jul 10, 2015 at 07:51:20PM +0200, Michael Niedermayer wrote:
>> On Fri, Jul 10, 2015 at 07:47:46PM +0200, Michael Niedermayer wrote:
>>> On Fri, Jul 10, 2015 at 11:52:24AM +0200, Michael Niedermayer wrote:
 On Thu, Jul 09, 2015 at 02:14:36PM -0400, Dave Rice wrote:
> 
>> On Jul 9, 2015, at 1:53 PM, Michael Niedermayer  wrote:
>> 
>> On Tue, Jul 07, 2015 at 11:03:39AM -0400, Dave Rice wrote:
>>> Hi,
>>> 
 On Jul 7, 2015, at 10:35 AM, Michael Niedermayer  
 wrote:
 
 On Thu, Jul 02, 2015 at 09:50:21AM -0400, Dave Rice wrote:
> Hi all,
> Last month I posted a draft of the FFV1 specification formatted in 
> Markdown [1], whereas it currently lives in lyx. From that post there 
> were responses in favor of the use of Markdown formatting and 
> suggestions to not use mathml within a draft targeting an RFC 
> specification and suggestions to update a few urls. I propose to 
> proceed with a format conversion of the FFV1 specification from lyx 
> to Markdown and then I'll file tickets or patches to explore 
> simplifying the mathml expressions and updating the urls. Attached is 
> a patch to convert the formatting (but not meaning) of the FFV1 
> specification from lyx to markdown.
> 
> Best Regards,
> Dave Rice
> 
> [1] http://comments.gmane.org/gmane.comp.video.ffmpeg.devel/193851
> 
 
 how can this be edited and converted ?
>>> 
>>> Via pandoc you can get outputs that are close to the current ffv1.html 
>>> and ffv1.pdf outputs of ffv1.lyx.
>>> 
>>> pandoc --mathml -s --number-sections ../ffv1.md -c lyx.css -o ffv1.html
>>> pandoc -s --number-sections ../ffv1.md --latex-engine=xelatex -V 
>>> geometry:margin=1in -o ffv1.pdf
>>> 
>>> I can move this info to a readme.
>> 
>> please do
> 
> Sure. Would you prefer a patch on ffmpeg-devel or a PR in github?
 
 whatever you prefer
>>> 
>>> generated files like pdf should not be checked into git.
>>> instead add a Makefile to generate them, so a simple
>>> make
>>> or
>>> make ffv1.pdf
>>> generates the file
>> 
>> also the readme should document which version of markdown/pandoc
>> this needs
>> and something should check for that version ideally so the user
>> is nt left wondering why "make" produces broken tables
> 
> reviewing the pull req
> 
> The conventions section 3.
> lacks vertical alignment

Fixed in 
https://github.com/MediaArea/FFV1/commit/d25fb39f7514547f72cbc13ef3851f3c9d9c0c5f

> theres an empty line after
>for(i=0;ihttps://github.com/MediaArea/FFV1/commit/1291e6c3e90ea6816b543a9e12c08d1cbbc1f31c

> 4.6.2.5:
>log2_run[41]={JPEGLS.
>0,0,0,0,1,1,1,1,
> 
> that JPEGLS is supposed to be a link/reference/whatever but its a
> litteral word

I'm having trouble getting a footnote to work within a codeblock. It is 
feasible to use this footnote in a reference to JPEGLS in a sentence above the 
codeblock?

[...]

Dave Rice

___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH] conversion of FFV1 specification from lyx to markdown

[Dave Rice]

> On Jul 10, 2015, at 1:51 PM, Michael Niedermayer  
> wrote:
> 
> On Fri, Jul 10, 2015 at 07:47:46PM +0200, Michael Niedermayer wrote:
>> On Fri, Jul 10, 2015 at 11:52:24AM +0200, Michael Niedermayer wrote:
>>> On Thu, Jul 09, 2015 at 02:14:36PM -0400, Dave Rice wrote:
 
> On Jul 9, 2015, at 1:53 PM, Michael Niedermayer  wrote:
> 
> On Tue, Jul 07, 2015 at 11:03:39AM -0400, Dave Rice wrote:
>> Hi,
>> 
>>> On Jul 7, 2015, at 10:35 AM, Michael Niedermayer  
>>> wrote:
>>> 
>>> On Thu, Jul 02, 2015 at 09:50:21AM -0400, Dave Rice wrote:
 Hi all,
 Last month I posted a draft of the FFV1 specification formatted in 
 Markdown [1], whereas it currently lives in lyx. From that post there 
 were responses in favor of the use of Markdown formatting and 
 suggestions to not use mathml within a draft targeting an RFC 
 specification and suggestions to update a few urls. I propose to 
 proceed with a format conversion of the FFV1 specification from lyx to 
 Markdown and then I'll file tickets or patches to explore simplifying 
 the mathml expressions and updating the urls. Attached is a patch to 
 convert the formatting (but not meaning) of the FFV1 specification 
 from lyx to markdown.
 
 Best Regards,
 Dave Rice
 
 [1] http://comments.gmane.org/gmane.comp.video.ffmpeg.devel/193851
 
>>> 
>>> how can this be edited and converted ?
>> 
>> Via pandoc you can get outputs that are close to the current ffv1.html 
>> and ffv1.pdf outputs of ffv1.lyx.
>> 
>> pandoc --mathml -s --number-sections ../ffv1.md -c lyx.css -o ffv1.html
>> pandoc -s --number-sections ../ffv1.md --latex-engine=xelatex -V 
>> geometry:margin=1in -o ffv1.pdf
>> 
>> I can move this info to a readme.
> 
> please do
 
 Sure. Would you prefer a patch on ffmpeg-devel or a PR in github?
>>> 
>>> whatever you prefer
>> 
>> generated files like pdf should not be checked into git.
>> instead add a Makefile to generate them, so a simple
>> make
>> or
>> make ffv1.pdf
>> generates the file
> 
> also the readme should document which version of markdown/pandoc
> this needs
> and something should check for that version ideally so the user
> is nt left wondering why "make" produces broken tables

I added a warning to both the Makefile and the README, squashed, and updated 
the PR. Not sure how to test the installed version in the Makefile.
Dave Rice

___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH] conversion of FFV1 specification from lyx to markdown

[Dave Rice]

> On Jul 10, 2015, at 1:47 PM, Michael Niedermayer  
> wrote:
> 
> On Fri, Jul 10, 2015 at 11:52:24AM +0200, Michael Niedermayer wrote:
>> On Thu, Jul 09, 2015 at 02:14:36PM -0400, Dave Rice wrote:
>>> 
 On Jul 9, 2015, at 1:53 PM, Michael Niedermayer  wrote:
 
 On Tue, Jul 07, 2015 at 11:03:39AM -0400, Dave Rice wrote:
> Hi,
> 
>> On Jul 7, 2015, at 10:35 AM, Michael Niedermayer  
>> wrote:
>> 
>> On Thu, Jul 02, 2015 at 09:50:21AM -0400, Dave Rice wrote:
>>> Hi all,
>>> Last month I posted a draft of the FFV1 specification formatted in 
>>> Markdown [1], whereas it currently lives in lyx. From that post there 
>>> were responses in favor of the use of Markdown formatting and 
>>> suggestions to not use mathml within a draft targeting an RFC 
>>> specification and suggestions to update a few urls. I propose to 
>>> proceed with a format conversion of the FFV1 specification from lyx to 
>>> Markdown and then I'll file tickets or patches to explore simplifying 
>>> the mathml expressions and updating the urls. Attached is a patch to 
>>> convert the formatting (but not meaning) of the FFV1 specification from 
>>> lyx to markdown.
>>> 
>>> Best Regards,
>>> Dave Rice
>>> 
>>> [1] http://comments.gmane.org/gmane.comp.video.ffmpeg.devel/193851
>>> 
>> 
>> how can this be edited and converted ?
> 
> Via pandoc you can get outputs that are close to the current ffv1.html 
> and ffv1.pdf outputs of ffv1.lyx.
> 
> pandoc --mathml -s --number-sections ../ffv1.md -c lyx.css -o ffv1.html
> pandoc -s --number-sections ../ffv1.md --latex-engine=xelatex -V 
> geometry:margin=1in -o ffv1.pdf
> 
> I can move this info to a readme.
 
 please do
>>> 
>>> Sure. Would you prefer a patch on ffmpeg-devel or a PR in github?
>> 
>> whatever you prefer
> 
> generated files like pdf should not be checked into git.
> instead add a Makefile to generate them, so a simple
> make
> or
> make ffv1.pdf
> generates the file

I drafted a makefile and updated the PR: 
https://github.com/MediaArea/FFV1/commit/45e2ba67078e4efe06e9453cef2627e4888a5cec
Dave
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH] conversion of FFV1 specification from lyx to markdown

[Michael Niedermayer]

On Fri, Jul 10, 2015 at 07:51:20PM +0200, Michael Niedermayer wrote:
> On Fri, Jul 10, 2015 at 07:47:46PM +0200, Michael Niedermayer wrote:
> > On Fri, Jul 10, 2015 at 11:52:24AM +0200, Michael Niedermayer wrote:
> > > On Thu, Jul 09, 2015 at 02:14:36PM -0400, Dave Rice wrote:
> > > > 
> > > > > On Jul 9, 2015, at 1:53 PM, Michael Niedermayer  
> > > > > wrote:
> > > > > 
> > > > > On Tue, Jul 07, 2015 at 11:03:39AM -0400, Dave Rice wrote:
> > > > >> Hi,
> > > > >> 
> > > > >>> On Jul 7, 2015, at 10:35 AM, Michael Niedermayer  
> > > > >>> wrote:
> > > > >>> 
> > > > >>> On Thu, Jul 02, 2015 at 09:50:21AM -0400, Dave Rice wrote:
> > > >  Hi all,
> > > >  Last month I posted a draft of the FFV1 specification formatted in 
> > > >  Markdown [1], whereas it currently lives in lyx. From that post 
> > > >  there were responses in favor of the use of Markdown formatting 
> > > >  and suggestions to not use mathml within a draft targeting an RFC 
> > > >  specification and suggestions to update a few urls. I propose to 
> > > >  proceed with a format conversion of the FFV1 specification from 
> > > >  lyx to Markdown and then I'll file tickets or patches to explore 
> > > >  simplifying the mathml expressions and updating the urls. Attached 
> > > >  is a patch to convert the formatting (but not meaning) of the FFV1 
> > > >  specification from lyx to markdown.
> > > >  
> > > >  Best Regards,
> > > >  Dave Rice
> > > >  
> > > >  [1] http://comments.gmane.org/gmane.comp.video.ffmpeg.devel/193851
> > > >  
> > > > >>> 
> > > > >>> how can this be edited and converted ?
> > > > >> 
> > > > >> Via pandoc you can get outputs that are close to the current 
> > > > >> ffv1.html and ffv1.pdf outputs of ffv1.lyx.
> > > > >> 
> > > > >> pandoc --mathml -s --number-sections ../ffv1.md -c lyx.css -o 
> > > > >> ffv1.html
> > > > >> pandoc -s --number-sections ../ffv1.md --latex-engine=xelatex -V 
> > > > >> geometry:margin=1in -o ffv1.pdf
> > > > >> 
> > > > >> I can move this info to a readme.
> > > > > 
> > > > > please do
> > > > 
> > > > Sure. Would you prefer a patch on ffmpeg-devel or a PR in github?
> > > 
> > > whatever you prefer
> > 
> > generated files like pdf should not be checked into git.
> > instead add a Makefile to generate them, so a simple
> > make
> > or
> > make ffv1.pdf
> > generates the file
> 
> also the readme should document which version of markdown/pandoc
> this needs
> and something should check for that version ideally so the user
> is nt left wondering why "make" produces broken tables

reviewing the pull req

The conventions section 3.
lacks vertical alignment

theres an empty line after
for(i=0;i

signature.asc
Description: Digital signature
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH] conversion of FFV1 specification from lyx to markdown

[Michael Niedermayer]

On Fri, Jul 10, 2015 at 07:47:46PM +0200, Michael Niedermayer wrote:
> On Fri, Jul 10, 2015 at 11:52:24AM +0200, Michael Niedermayer wrote:
> > On Thu, Jul 09, 2015 at 02:14:36PM -0400, Dave Rice wrote:
> > > 
> > > > On Jul 9, 2015, at 1:53 PM, Michael Niedermayer  
> > > > wrote:
> > > > 
> > > > On Tue, Jul 07, 2015 at 11:03:39AM -0400, Dave Rice wrote:
> > > >> Hi,
> > > >> 
> > > >>> On Jul 7, 2015, at 10:35 AM, Michael Niedermayer  
> > > >>> wrote:
> > > >>> 
> > > >>> On Thu, Jul 02, 2015 at 09:50:21AM -0400, Dave Rice wrote:
> > >  Hi all,
> > >  Last month I posted a draft of the FFV1 specification formatted in 
> > >  Markdown [1], whereas it currently lives in lyx. From that post 
> > >  there were responses in favor of the use of Markdown formatting and 
> > >  suggestions to not use mathml within a draft targeting an RFC 
> > >  specification and suggestions to update a few urls. I propose to 
> > >  proceed with a format conversion of the FFV1 specification from lyx 
> > >  to Markdown and then I'll file tickets or patches to explore 
> > >  simplifying the mathml expressions and updating the urls. Attached 
> > >  is a patch to convert the formatting (but not meaning) of the FFV1 
> > >  specification from lyx to markdown.
> > >  
> > >  Best Regards,
> > >  Dave Rice
> > >  
> > >  [1] http://comments.gmane.org/gmane.comp.video.ffmpeg.devel/193851
> > >  
> > > >>> 
> > > >>> how can this be edited and converted ?
> > > >> 
> > > >> Via pandoc you can get outputs that are close to the current ffv1.html 
> > > >> and ffv1.pdf outputs of ffv1.lyx.
> > > >> 
> > > >> pandoc --mathml -s --number-sections ../ffv1.md -c lyx.css -o ffv1.html
> > > >> pandoc -s --number-sections ../ffv1.md --latex-engine=xelatex -V 
> > > >> geometry:margin=1in -o ffv1.pdf
> > > >> 
> > > >> I can move this info to a readme.
> > > > 
> > > > please do
> > > 
> > > Sure. Would you prefer a patch on ffmpeg-devel or a PR in github?
> > 
> > whatever you prefer
> 
> generated files like pdf should not be checked into git.
> instead add a Makefile to generate them, so a simple
> make
> or
> make ffv1.pdf
> generates the file

also the readme should document which version of markdown/pandoc
this needs
and something should check for that version ideally so the user
is nt left wondering why "make" produces broken tables

[...]
-- 
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Rewriting code that is poorly written but fully understood is good.
Rewriting code that one doesnt understand is a sign that one is less smart
then the original author, trying to rewrite it will not make it better.


signature.asc
Description: Digital signature
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH] conversion of FFV1 specification from lyx to markdown

[Michael Niedermayer]

On Fri, Jul 10, 2015 at 11:52:24AM +0200, Michael Niedermayer wrote:
> On Thu, Jul 09, 2015 at 02:14:36PM -0400, Dave Rice wrote:
> > 
> > > On Jul 9, 2015, at 1:53 PM, Michael Niedermayer  wrote:
> > > 
> > > On Tue, Jul 07, 2015 at 11:03:39AM -0400, Dave Rice wrote:
> > >> Hi,
> > >> 
> > >>> On Jul 7, 2015, at 10:35 AM, Michael Niedermayer  
> > >>> wrote:
> > >>> 
> > >>> On Thu, Jul 02, 2015 at 09:50:21AM -0400, Dave Rice wrote:
> >  Hi all,
> >  Last month I posted a draft of the FFV1 specification formatted in 
> >  Markdown [1], whereas it currently lives in lyx. From that post there 
> >  were responses in favor of the use of Markdown formatting and 
> >  suggestions to not use mathml within a draft targeting an RFC 
> >  specification and suggestions to update a few urls. I propose to 
> >  proceed with a format conversion of the FFV1 specification from lyx to 
> >  Markdown and then I'll file tickets or patches to explore simplifying 
> >  the mathml expressions and updating the urls. Attached is a patch to 
> >  convert the formatting (but not meaning) of the FFV1 specification 
> >  from lyx to markdown.
> >  
> >  Best Regards,
> >  Dave Rice
> >  
> >  [1] http://comments.gmane.org/gmane.comp.video.ffmpeg.devel/193851
> >  
> > >>> 
> > >>> how can this be edited and converted ?
> > >> 
> > >> Via pandoc you can get outputs that are close to the current ffv1.html 
> > >> and ffv1.pdf outputs of ffv1.lyx.
> > >> 
> > >> pandoc --mathml -s --number-sections ../ffv1.md -c lyx.css -o ffv1.html
> > >> pandoc -s --number-sections ../ffv1.md --latex-engine=xelatex -V 
> > >> geometry:margin=1in -o ffv1.pdf
> > >> 
> > >> I can move this info to a readme.
> > > 
> > > please do
> > 
> > Sure. Would you prefer a patch on ffmpeg-devel or a PR in github?
> 
> whatever you prefer

generated files like pdf should not be checked into git.
instead add a Makefile to generate them, so a simple
make
or
make ffv1.pdf
generates the file

[...]


-- 
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Many that live deserve death. And some that die deserve life. Can you give
it to them? Then do not be too eager to deal out death in judgement. For
even the very wise cannot see all ends. -- Gandalf


signature.asc
Description: Digital signature
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH] conversion of FFV1 specification from lyx to markdown

[Michael Niedermayer]

On Thu, Jul 09, 2015 at 02:14:36PM -0400, Dave Rice wrote:
> 
> > On Jul 9, 2015, at 1:53 PM, Michael Niedermayer  wrote:
> > 
> > On Tue, Jul 07, 2015 at 11:03:39AM -0400, Dave Rice wrote:
> >> Hi,
> >> 
> >>> On Jul 7, 2015, at 10:35 AM, Michael Niedermayer  wrote:
> >>> 
> >>> On Thu, Jul 02, 2015 at 09:50:21AM -0400, Dave Rice wrote:
>  Hi all,
>  Last month I posted a draft of the FFV1 specification formatted in 
>  Markdown [1], whereas it currently lives in lyx. From that post there 
>  were responses in favor of the use of Markdown formatting and 
>  suggestions to not use mathml within a draft targeting an RFC 
>  specification and suggestions to update a few urls. I propose to proceed 
>  with a format conversion of the FFV1 specification from lyx to Markdown 
>  and then I'll file tickets or patches to explore simplifying the mathml 
>  expressions and updating the urls. Attached is a patch to convert the 
>  formatting (but not meaning) of the FFV1 specification from lyx to 
>  markdown.
>  
>  Best Regards,
>  Dave Rice
>  
>  [1] http://comments.gmane.org/gmane.comp.video.ffmpeg.devel/193851
>  
> >>> 
> >>> how can this be edited and converted ?
> >> 
> >> Via pandoc you can get outputs that are close to the current ffv1.html and 
> >> ffv1.pdf outputs of ffv1.lyx.
> >> 
> >> pandoc --mathml -s --number-sections ../ffv1.md -c lyx.css -o ffv1.html
> >> pandoc -s --number-sections ../ffv1.md --latex-engine=xelatex -V 
> >> geometry:margin=1in -o ffv1.pdf
> >> 
> >> I can move this info to a readme.
> > 
> > please do
> 
> Sure. Would you prefer a patch on ffmpeg-devel or a PR in github?

whatever you prefer


> 
> > ive tried with
> > pandoc --version
> > pandoc 1.9.1.1
> 
> I'm using:
> pandoc --version
> pandoc 1.13.2.1
> 
> I'm only recently introduced to pandoc so I'm not well aware of the 
> difference from 1.9.1.1 to 1.13.3.1, but I do see a lot of references to 
> markdown and table bug fixes in http://pandoc.org/releases.html 
>  after 1.9.1.1.
> 
> > and it also fails (all tables messed up), the html in git looks good though
> 
> Could you give me access to your pdf so I can see the difference.

http://ffmpeg.org/~michael/broken_ffv1.pdf



> 
> > does this use features available only in recent pandoc ?
> 
> It seems so.
> Dave Rice
> 
> ___
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

-- 
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Complexity theory is the science of finding the exact solution to an
approximation. Benchmarking OTOH is finding an approximation of the exact


signature.asc
Description: Digital signature
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH] conversion of FFV1 specification from lyx to markdown

[Dave Rice]

> On Jul 9, 2015, at 1:53 PM, Michael Niedermayer  wrote:
> 
> On Tue, Jul 07, 2015 at 11:03:39AM -0400, Dave Rice wrote:
>> Hi,
>> 
>>> On Jul 7, 2015, at 10:35 AM, Michael Niedermayer  wrote:
>>> 
>>> On Thu, Jul 02, 2015 at 09:50:21AM -0400, Dave Rice wrote:
 Hi all,
 Last month I posted a draft of the FFV1 specification formatted in 
 Markdown [1], whereas it currently lives in lyx. From that post there were 
 responses in favor of the use of Markdown formatting and suggestions to 
 not use mathml within a draft targeting an RFC specification and 
 suggestions to update a few urls. I propose to proceed with a format 
 conversion of the FFV1 specification from lyx to Markdown and then I'll 
 file tickets or patches to explore simplifying the mathml expressions and 
 updating the urls. Attached is a patch to convert the formatting (but not 
 meaning) of the FFV1 specification from lyx to markdown.
 
 Best Regards,
 Dave Rice
 
 [1] http://comments.gmane.org/gmane.comp.video.ffmpeg.devel/193851
 
>>> 
>>> how can this be edited and converted ?
>> 
>> Via pandoc you can get outputs that are close to the current ffv1.html and 
>> ffv1.pdf outputs of ffv1.lyx.
>> 
>> pandoc --mathml -s --number-sections ../ffv1.md -c lyx.css -o ffv1.html
>> pandoc -s --number-sections ../ffv1.md --latex-engine=xelatex -V 
>> geometry:margin=1in -o ffv1.pdf
>> 
>> I can move this info to a readme.
> 
> please do

Sure. Would you prefer a patch on ffmpeg-devel or a PR in github?

> ive tried with
> pandoc --version
> pandoc 1.9.1.1

I'm using:
pandoc --version
pandoc 1.13.2.1

I'm only recently introduced to pandoc so I'm not well aware of the difference 
from 1.9.1.1 to 1.13.3.1, but I do see a lot of references to markdown and 
table bug fixes in http://pandoc.org/releases.html 
 after 1.9.1.1.

> and it also fails (all tables messed up), the html in git looks good though

Could you give me access to your pdf so I can see the difference.

> does this use features available only in recent pandoc ?

It seems so.
Dave Rice

___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH] conversion of FFV1 specification from lyx to markdown

[Michael Niedermayer]

On Tue, Jul 07, 2015 at 11:03:39AM -0400, Dave Rice wrote:
> Hi,
> 
> > On Jul 7, 2015, at 10:35 AM, Michael Niedermayer  wrote:
> > 
> > On Thu, Jul 02, 2015 at 09:50:21AM -0400, Dave Rice wrote:
> >> Hi all,
> >> Last month I posted a draft of the FFV1 specification formatted in 
> >> Markdown [1], whereas it currently lives in lyx. From that post there were 
> >> responses in favor of the use of Markdown formatting and suggestions to 
> >> not use mathml within a draft targeting an RFC specification and 
> >> suggestions to update a few urls. I propose to proceed with a format 
> >> conversion of the FFV1 specification from lyx to Markdown and then I'll 
> >> file tickets or patches to explore simplifying the mathml expressions and 
> >> updating the urls. Attached is a patch to convert the formatting (but not 
> >> meaning) of the FFV1 specification from lyx to markdown.
> >> 
> >> Best Regards,
> >> Dave Rice
> >> 
> >> [1] http://comments.gmane.org/gmane.comp.video.ffmpeg.devel/193851
> >> 
> > 
> > how can this be edited and converted ?
> 
> Via pandoc you can get outputs that are close to the current ffv1.html and 
> ffv1.pdf outputs of ffv1.lyx.
> 
> pandoc --mathml -s --number-sections ../ffv1.md -c lyx.css -o ffv1.html
> pandoc -s --number-sections ../ffv1.md --latex-engine=xelatex -V 
> geometry:margin=1in -o ffv1.pdf
> 
> I can move this info to a readme.

please do
ive tried with
pandoc --version
pandoc 1.9.1.1

and it also fails (all tables messed up), the html in git looks good though

does this use features available only in recent pandoc ?

[...]
-- 
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Rewriting code that is poorly written but fully understood is good.
Rewriting code that one doesnt understand is a sign that one is less smart
then the original author, trying to rewrite it will not make it better.


signature.asc
Description: Digital signature
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH] conversion of FFV1 specification from lyx to markdown

[Dave Rice]

Hi,

> On Jul 7, 2015, at 10:35 AM, Michael Niedermayer  wrote:
> 
> On Thu, Jul 02, 2015 at 09:50:21AM -0400, Dave Rice wrote:
>> Hi all,
>> Last month I posted a draft of the FFV1 specification formatted in Markdown 
>> [1], whereas it currently lives in lyx. From that post there were responses 
>> in favor of the use of Markdown formatting and suggestions to not use mathml 
>> within a draft targeting an RFC specification and suggestions to update a 
>> few urls. I propose to proceed with a format conversion of the FFV1 
>> specification from lyx to Markdown and then I'll file tickets or patches to 
>> explore simplifying the mathml expressions and updating the urls. Attached 
>> is a patch to convert the formatting (but not meaning) of the FFV1 
>> specification from lyx to markdown.
>> 
>> Best Regards,
>> Dave Rice
>> 
>> [1] http://comments.gmane.org/gmane.comp.video.ffmpeg.devel/193851
>> 
> 
> how can this be edited and converted ?

Via pandoc you can get outputs that are close to the current ffv1.html and 
ffv1.pdf outputs of ffv1.lyx.

pandoc --mathml -s --number-sections ../ffv1.md -c lyx.css -o ffv1.html
pandoc -s --number-sections ../ffv1.md --latex-engine=xelatex -V 
geometry:margin=1in -o ffv1.pdf

I can move this info to a readme.

> i tried retext but tables are shown totally messed up
> i tried markdown_py to convert to html but similar its largely messed
> up

We didn't test with markdown_py but were mostly working with pandoc.

> i tried remarkable and again tables are messed up, basically lacking
> linebreaks as in the others above, maybe its overall less broken then
> the others
> thats remarkable 1.41
> 
> and i tried markdown itself but again its all messed up
> looking like:
> 
> (i hope all the odd chars make it intact throug the mail)
> 
> | | | 
> |---|--|
>  | QuantizationTablePerContext(i, j, scale) { | type | |Â Â Â Â v = 0 | | |Â 
> Â Â Â for( k = 0; k \< 128; ) { | | |Â Â Â Â Â Â Â Â len - 1 | sr | |Â Â Â Â 
> Â Â Â Â for( a = 0; a \< len; a++ ) { | | |Â Â Â Â Â Â Â Â Â Â Â Â 
> quant_tables[ i ][ j ][ k ] = scale* v | | |Â Â Â Â Â Â Â Â Â Â Â Â k++ | | 
> |Â Â Â Â Â Â Â Â } | | |Â Â Â Â Â Â Â Â v++ | | |Â Â Â Â } | | |Â Â Â Â for( 
> k = 1; k \< 128; k++ ) { | | |Â Â Â Â Â Â Â Â quant_tables[ i ][ j ][ 256 - k 
> ] = -quant_tables[ i ][ j ][ k ] | | |Â Â Â Â } | | |Â Â Â Â quant_tables[ i 
> ][ j ][ 128 ] = -quant_tables[ i ][ j ][ 127 ] | | |Â Â Â Â len_count[ i ][ j 
> ] = v | | |} | |
> 
> 
> is this in git somewhere? maybe it got trashed through mail or me
> applying it

This is possible. Here is the markdown file: 
https://github.com/mediaarea/ffv1/tree/markdown 
.
Thanks much,
Dave Rice

___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH] conversion of FFV1 specification from lyx to markdown

[Michael Niedermayer]

On Thu, Jul 02, 2015 at 09:50:21AM -0400, Dave Rice wrote:
> Hi all,
> Last month I posted a draft of the FFV1 specification formatted in Markdown 
> [1], whereas it currently lives in lyx. From that post there were responses 
> in favor of the use of Markdown formatting and suggestions to not use mathml 
> within a draft targeting an RFC specification and suggestions to update a few 
> urls. I propose to proceed with a format conversion of the FFV1 specification 
> from lyx to Markdown and then I'll file tickets or patches to explore 
> simplifying the mathml expressions and updating the urls. Attached is a patch 
> to convert the formatting (but not meaning) of the FFV1 specification from 
> lyx to markdown.
> 
> Best Regards,
> Dave Rice
> 
> [1] http://comments.gmane.org/gmane.comp.video.ffmpeg.devel/193851
> 

how can this be edited and converted ?
i tried retext but tables are shown totally messed up
i tried markdown_py to convert to html but similar its largely messed
up
i tried remarkable and again tables are messed up, basically lacking
linebreaks as in the others above, maybe its overall less broken then
the others
thats remarkable 1.41

and i tried markdown itself but again its all messed up
looking like:

(i hope all the odd chars make it intact throug the mail)

| | | 
|---|--|
 | QuantizationTablePerContext(i, j, scale) { | type | |Â Â Â Â v = 0 | | |Â Â 
  for( k = 0; k \< 128; ) { | | |        len - 1 | sr | |      
  for( a = 0; a \< len; a++ ) { | | |            quant_tables[ i 
][ j ][ k ] = scale* v | | |Â Â Â Â Â Â Â Â Â Â Â Â k++ | | |Â Â Â Â Â Â Â Â } 
| | |Â Â Â Â Â Â Â Â v++ | | |Â Â Â Â } | | |Â Â Â Â for( k = 1; k \< 128; k++ 
) { | | |Â Â Â Â Â Â Â Â quant_tables[ i ][ j ][ 256 - k ] = -quant_tables[ i 
][ j ][ k ] | | |Â Â Â Â } | | |Â Â Â Â quant_tables[ i ][ j ][ 128 ] = 
-quant_tables[ i ][ j ][ 127 ] | | |Â Â Â Â len_count[ i ][ j ] = v | | |} | |


is this in git somewhere? maybe it got trashed through mail or me
applying it


[...]
-- 
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

The real ebay dictionary, page 3
"Rare item" - "Common item with rare defect or maybe just a lie"
"Professional" - "'Toy' made in china, not functional except as doorstop"
"Experts will know" - "The seller hopes you are not an expert"


signature.asc
Description: Digital signature
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel