couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Lehnardt <...@apache.org>
Subject Re: start translation of the docs into German language
Date Mon, 14 Oct 2013 19:18:18 GMT
+100 to all of this :D

Great initiative Andy!

Let me know if you need any help :)

Best
Jan
-- 

On Oct 12, 2013, at 21:31 , Andy Wenk <andy@nms.de> wrote:

> Hi Octavian,
> 
> actually it's just me ;-). I thought the same like you - since there is now
> this awesome documentation, we should translate it. I want to let the stone
> roll with my post. If there are already people you know, you can point them
> to me. I guess we need to setup all this very concise - especially the
> translation process - to encourage people to participate. So this is just
> the starting point now. Finally, more people will use CouchDB ;-)
> 
> What do you think about having an own translation list and a public place
> for topics regarding I18n ?
> 
> Cheers
> 
> Andy
> 
> 
> On 12 October 2013 21:24, Octavian Damiean <odamiean@linux.com> wrote:
> 
>> Hello Andy,
>> 
>> This is good news! I always wanted to start doing that but that was before
>> Alexander put together our new awesome docs. Now that everything is bundled
>> I believe it the time is right.
>> 
>> Do you already have other people interested in translating or is it just
>> you so far?
>> 
>> 
>> On Sat, Oct 12, 2013 at 4:53 PM, Andy Wenk <andy@nms.de> wrote:
>> 
>>> Hi all,
>>> 
>>> as the documentation has found it's way into Futon and after having met
>> Jan
>>> at JSConf.eu with a short talk about how to participate in the project, I
>>> am thinking about starting to translate the docs into German. I
>> understood,
>>> that the documentation source files are placed in /share/doc/src . Am I
>>> right, that the only language available is English for now? If so, what
>>> would be a good idea to start with multilingual docs? An idea would be to
>>> have
>>> 
>>> /share/doc/src/en-GB
>>> /share/doc/src/de-DE
>>> 
>>> and so on. Any thoughts about this?
>>> 
>>> Further more. What is the best way to compile the whole documentation? Is
>>> there a best way to do or a good process?
>>> 
>>> Any ideas and help is highly appreciated.
>>> 
>>> Cheers
>>> 
>>> Andy
>>> 
>>> 
>>> --
>>> Andy Wenk
>>> Hamburg - Germany
>>> RockIt!
>>> 
>> 
>> 
>> 
>> --
>> Octavian Damiean
>> 
>> GitHub: https://github.com/mainerror
>> 
> 
> 
> 
> -- 
> Andy Wenk
> Hamburg - Germany
> RockIt!
> 
> "CouchDB - Das Praxisbuch für Entwickler und Administratoren"
> http://www.galileocomputing.de/2462
> http://www.couchdb-buch.de
> 
> "PostgreSQL 8.4: Das Praxisbuch"
> http://www.galileocomputing.de/2008
> http://www.pg-praxisbuch.de
> 
> -----BEGIN PGP PUBLIC KEY BLOCK-----
> Version: OpenPGP.js v.1.20130712
> Comment: http://openpgpjs.org
> 
> xo0EUeJpHgED/34kUBUQNNT+3fcc621CLjzQZsuwYajo7Pj1hxtTcPbOo6Ci
> UbyGOlIhlSDBaiXGXsFKxtdp4z/os7NdFQstzh6QpHzppjbGzGkv/om49jJM
> SYLYkXyMDquhEQO47ovgOQUwJeO5qSzKE5fxftJQUjzHY1K673aA9D80uREM
> Jc1tABEBAAHNF0FuZHkgV2VuayA8YW5keUBubXMuZGU+wpwEEAEIABAFAlHi
> aR8JEAhxaGu1XIB2AAAfuAP/ZJXbv5wxAGCPridI/8Za9fXcccM0GmsG5ciH
> bkhE9bakLlexclv3Jb+iQ2Cyp2FFo1wzLSADRRMEz1EvFFUoDo/Wj2SUQnaq
> LNA8tKkRBuW0tUf88aK66TcdRINghhAcEqVJtwRIXF7fI5Arv6N+ql8heD3O
> 4/jA6c/8iExS0dE=
> =6ftE
> -----END PGP PUBLIC KEY BLOCK-----


Mime
View raw message