Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (athena.apache.org: domain of agrieve@google.com designates
 209.85.160.47 as permitted sender)
MIME-Version: 1.0
Sender: agrieve@google.com
In-Reply-To: 
 <OFA6F0E859.DFCD843A-ON87257C89.00588959-85257C89.00592E6B@us.ibm.com>
References: 
 <OFA6F0E859.DFCD843A-ON87257C89.00588959-85257C89.00592E6B@us.ibm.com>
From: Andrew Grieve <agrieve@chromium.org>
Date: Mon, 24 Feb 2014 12:32:36 -0500
Message-ID: 
 <CABiQX1XCSoZ8XtU=-n4Yyzdk7we=C1nk6EzYFDba=aHEmEFe=g@mail.gmail.com>
Subject: Re: [Input request] Rethinking Plugin docs
To: dev <dev@cordova.apache.org>
Content-Type: multipart/alternative; boundary=047d7b33c8deb21c5c04f32a5cbc

--047d7b33c8deb21c5c04f32a5cbc
Content-Type: text/plain; charset=UTF-8

My thoughts here:

1.
- We may also want to include README.md files in the translations.
- I like not having a subdir for en/ so as to differentiate it as the one
the others are based off of
- We don't need the version in the directory since we can use git tags to
find old versions

maybe:
doc/index.md
doc/fr/index.md
doc/fr/README.md
doc/es/index.md
doc/es/README.md

2.
The plan is to render these on plugins.cordova.io, so we can certainly add
logic there to maintain language pref.


On Mon, Feb 24, 2014 at 11:13 AM, Lisa Seacat DeLuca <ldeluca@us.ibm.com>wrote:

> I noticed for the 3.4 release that the documentation for each of the
> plugins redirects to the github repository for each plugin and a document
> under doc/index.md
>
>
> http://cordova.apache.org/docs/en/3.4.0/cordova_plugins_pluginapis.md.html#Plugin%20APIs
>
> If we want to have translations for each of the plugins then we're going
> to need to rethink this a little.  Here are two options:
>
> 1. similar to the cordova-docs dir, we could have a language directory as
> the parent.
> ex. doc/en/index.md
> and while we're at it we probably need the version as well
> ex. doc/en/3.4.0/index.md
>
> If we do this then at least we can have the documentation for each
> language.  But that doesn't solve the problem of the user being always
> redirected to the english version of the documentation and not their
> specific language.
>
> 2. Is it hard to do a build of the index.md for each plugin similar to
> how we build the cordova-doc md files into html files?  If it were seamless
> and part of the other documentation it would make my life
> *coughTranslationcough* so much easier.  Plus it won't be as confusing on
> end users having to choose their language more than one time.
>
> It'd be nice to get some input from everyone before I start writing a
> complicated automated script for the plugin translations.
>
>
> Lisa
>
> Lisa Seacat DeLuca
> Mobile Engineer | t: +415.787.4589 | *ldeluca@apache.org*<ldeluca@apache.org>| |
> *ldeluca@us.ibm.com* <ldeluca@us.ibm.com> | *lisaseacat.com*<http://www.lisaseacat.com/>| [image:
> follow @LisaSeacat on twitter] <http://www.twitter.com/LisaSeacat>| [image:
> follow Lisa Seacat DeLuca on linkedin]<http://www.linkedin.com/in/lisaseacat>
>
>

--047d7b33c8deb21c5c04f32a5cbc--