# Nokogiri (1.5.9)
---
nokogiri: 1.5.9
libxml:
loaded: 2.7.8
binding: extension
compiled: 2.7.8
warnings: []
ruby:
description: ruby 1.8.7 (2012-02-08 patchlevel 358) [universal-darwin12.0]
platform: universal-darwin12.0
engine: mri
version: 1.8.7
joDoc
b64f9841e95eedcbdfaf3cb2e9817e6a00a032e2
MD5 (/usr/local/bin/markdown) = c1609b303b7fe654435380a168d78acf
From: Andrew Grieve <agri...@chromium.org<mailto:agri...@chromium.org>>
Date: Wednesday, July 31, 2013 4:07 PM
To: Andrew Grieve <agri...@chromium.org<mailto:agri...@chromium.org>>, Steven
Gill <stev...@adobe.com<mailto:stev...@adobe.com>>
Cc: dev <dev@cordova.apache.org<mailto:dev@cordova.apache.org>>
Subject: Re: Generating Docs with minimal changes
WAIT!!! Steve - It's *you* that generated the version of the docs that's
currently checked in! I had just assumed it was Michael.
Steve - tell me your version of nokogiri, your hash of joDoc, and the md5 of
your markdown.
On Wed, Jul 31, 2013 at 6:56 PM, Andrew Grieve
<agri...@chromium.org<mailto:agri...@chromium.org>> wrote:
Okay, just tried with the exact same joDoc, and exact same nokogiri version.
Even have the same ruby version (although I switched to linux after giving up
trying to got nokogiri working on osx).
*STILL* getting diffs all over:
-<strong>honorificPrefix</strong>: The contact's prefix (example <em>Mr.</em>
or <em>Dr.</em>) <em>(DOMString)</em>
-</li>
-<li>
-<strong>honorificSuffix</strong>: The contact's suffix (example
<em>Esq.</em>). <em>(DOMString)</em>
-</li>
+<li><p><strong>formatted</strong>: The complete name of the contact.
<em>(DOMString)</em></p></li>
+<li><p><strong>familyName</strong>: The contact's family name.
<em>(DOMString)</em></p></li>
+<li><p><strong>givenName</strong>: The contact's given name.
<em>(DOMString)</em></p></li>
+<li><p><strong>middleName</strong>: The contact's middle name.
<em>(DOMString)</em></p></li>
Still suspect it's Markdown.pl that's the problem. could you send me your
version of it?
On Tue, Jul 30, 2013 at 3:07 PM, Michael Brooks
<mich...@michaelbrooks.ca<mailto:mich...@michaelbrooks.ca>> wrote:
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<mailto: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<mailto: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<mailto: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.
>>>
>>
>>
>
