Re: buildout coredev and language translation in docs folder

to make that a bit more concrete, it's about the folders 'es' and 'pt_BR' at
https://github.com/plone/buildout.coredev/tree/4.3/docs

(as well as other branches, like 5.0).

Proposal would be to lose them for the 4.3 and 5.0 branches. These
translations are not update any more; and this method is not very
scalable to begin with.

translating (parts of) the buildout.coredev via docs.plone.org has all
the niceties of transifex built in; and doesn't upset the other tools
we're bringing in like spellchecking the docs.

On 13-10-14 15:08, sven wrote:
> Hi,
> 
> do we have to keep the translations in the docs folder, I mean I can see
> the point why it was done like that, but since we are moving docs and
> also implementing/now using translations via transifex, they are a bit
> 'in the way'.
> 
> One other 'issue' is that papyrus has now a spell check included to make
> sure, docs are getting better, these spell checks are not running [yet]
> for other languages, what results in lots of false positive, which is
> not ideal since we a busy to connect papyrus to jenkins.
> 
> One more thing, we are fetching buildout coredevs docs and including
> them now already since some time into docs.plone.org to have all docs on
> one place.
> 
> So it would be nice if the maintainer of these docs on rtd, could close
> them on rtd.
> 
> Cheers,
> 
> Sven
> 




------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://p.sf.net/sfu/Zoho