nokogiri --version
# Nokogiri (1.5.9)
    ---
    warnings: []

    libxml:
      compiled: 2.7.7
      loaded: 2.7.7
      binding: extension
    nokogiri: 1.5.9
    ruby:
      description: ruby 1.8.7 (2012-02-08 patchlevel 358)
[universal-darwin11.0]
      version: 1.8.7
      engine: mri
      platform: universal-darwin11.0

jodoc
SHA b64f9841e95eedcbdfaf3cb2e9817e6a00a032e2


On Thu, Jul 25, 2013 at 11:42 AM, Andrew Grieve <agri...@chromium.org>wrote:

> Shoot, that's the same version that I have.
>
> $ md5 /usr/local/bin/markdown
> MD5 (/usr/local/bin/markdown) = c1609b303b7fe654435380a168d78acf
>
> Also have:
>
> nokogiri --version
> # Nokogiri (1.5.5)
>     ---
>     libxml:
>       compiled: 2.8.0
>       loaded: 2.8.0
>       binding: extension
>     warnings: []
>
>     ruby:
>       engine: mri
>       description: ruby 1.8.7 (2012-02-08 patchlevel 358)
> [universal-darwin12.0]
>       version: 1.8.7
>       platform: universal-darwin12.0
>     nokogiri: 1.5.5
>
>
>
> joDoc doesn't seem to report a version :(.
>
> Does your nokogiri version match?
>
>
>
> On Thu, Jul 25, 2013 at 2:26 PM, Michael Brooks 
> <mich...@michaelbrooks.ca>wrote:
>
>> $ markdown --version
>>
>> This is Markdown, version 1.0.1.
>> Copyright 2004 John Gruber
>> http://daringfireball.net/projects/markdown/
>>
>>
>> On Tue, Jul 23, 2013 at 11:19 AM, Andrew Grieve <agri...@chromium.org>wrote:
>>
>>> Working on CB-4360, and think I've got it mostly covered (use rsync
>>> instead of cp).
>>>
>>> Having this one issue though: When I update the files, they have
>>> whitespace differences:
>>>
>>> E.g.
>>>
>>> -<h2>
>>>> -<a name="Getting%20Started%20with%20WebOS_3_setup_new_project">3.
>>>> Setup New Project</a>
>>>> -</h2>
>>>> +<h2><a name="Getting%20Started%20with%20WebOS_3_setup_new_project">3.
>>>> Setup New Project</a></h2>
>>>
>>>
>>> One guess is that this is caused from using different versions of
>>> Markdown.pl.
>>>
>>> Michael - looks like you generated the 3.0.0 docs. Could you reply with
>>> your version of Markdown.pl and I'll see if it generates the same output on
>>> my machine? If so, I'll check the file into the repo so that we are all
>>> using the same version.
>>>
>>
>>
>

Reply via email to