t;
> Am Do., 16. Mai 2019 um 07:19 Uhr schrieb Dmitry Blotsky
> :
> >
> > Ok, if that’s reality, then it’s reality. Then, if we’re on the topic of
> dropping translations, let’s revisit the whole commitment.
> >
> > I’d be interested to know:
> > 1. Do we want to
hen, if we’re on the topic of
> dropping translations, let’s revisit the whole commitment.
>
> I’d be interested to know:
> 1. Do we want to keep the Crowdin account?
> 2. How many versions of docs are we keeping? Maybe we can prune some.
> 3. Do we want to keep support for transl
Ok, if that’s reality, then it’s reality. Then, if we’re on the topic of
dropping translations, let’s revisit the whole commitment.
I’d be interested to know:
1. Do we want to keep the Crowdin account?
2. How many versions of docs are we keeping? Maybe we can prune some.
3. Do we want to keep
On Wed, May 15, 2019 at 9:24 AM Dmitry Blotsky wrote:
>
> Would anyone that works on Cordova full-time be up to prioritise this?
As far as I know, there has been nobody working full-time on Cordova
for the past year. There are a few companies putting some dev time
against the project, but it's al
Crowdin translations into the
codebase.
That change isn’t technically complex, but just needs to get the time and
effort dedicated. I estimate it would take 2 weeks of full-time work to get
working seamlessly. Would anyone that works on Cordova full-time be up to
prioritise this? If so, I can work
ny and have read the some parts of the german docs, only one
> time.
> The quality was poor and not well translated, because maybe some
> translations were made automatically or by a person without the knowledge
> of every technical aspect of cordova.
> So I suggest to put the man
+1
I'm from germany and have read the some parts of the german docs, only one time.
The quality was poor and not well translated, because maybe some translations
were made automatically or by a person without the knowledge of every technical
aspect of cordova.
So I suggest to put the man
m while
>> keeping a
>> > good/high quality.
>> >
>> >> On Wed, May 15, 2019 at 10:24 AM wrote:
>> >>
>> >> Doc translations are not being actively maintained and are thus
>> outdated.
>> >> Furthermore, at least some of
> >
> > Personally I've got the feeling that we can't maintain them while
> keeping a
> > good/high quality.
> >
> >> On Wed, May 15, 2019 at 10:24 AM wrote:
> >>
> >> Doc translations are not being actively maintained and are thus
&g
gt;> On Wed, May 15, 2019 at 10:24 AM wrote:
>>
>> Doc translations are not being actively maintained and are thus outdated.
>> Furthermore, at least some of the existing translations seem to be really
>> bad too. Consequently I propose to remove all translations from
+1 for removing them
Personally I've got the feeling that we can't maintain them while keeping a
good/high quality.
On Wed, May 15, 2019 at 10:24 AM wrote:
> Doc translations are not being actively maintained and are thus outdated.
> Furthermore, at least some of the existing t
Doc translations are not being actively maintained and are thus outdated.
Furthermore, at least some of the existing translations seem to be really
bad too. Consequently I propose to remove all translations from the docs
(cordova-docs as well as any other repos).
I checked the guide entry page
f them are active anymore. It would be nice to figure this out
> and
> >> >> fully document it.
> >> >>
> >> >>
> >> >>
> >> >> On Thu, Sep 1, 2016 at 12:12 PM, julio cesar sanchez <
> >> >> jcesarmob...@gm
document it.
>> >>
>> >>
>> >>
>> >> On Thu, Sep 1, 2016 at 12:12 PM, julio cesar sanchez <
>> >> jcesarmob...@gmail.com
>> >> > wrote:
>> >>
>> >> > Hello everyone.
>> >> >
>>
gt; > Hello everyone.
> >> >
> >> > I'm writing again because I wrote on another thread 3 months ago and
> >> nobody
> >> > answered me (http://markmail.org/message/aafqb42q2sc5awve)
> >> >
> >> > So asking again, are
gt; > Hello everyone.
>> >
>> > I'm writing again because I wrote on another thread 3 months ago and
>> nobody
>> > answered me (http://markmail.org/message/aafqb42q2sc5awve)
>> >
>> > So asking again, are we still using Crowdin for translatio
gt;
> > I'm writing again because I wrote on another thread 3 months ago and
> nobody
> > answered me (http://markmail.org/message/aafqb42q2sc5awve)
> >
> > So asking again, are we still using Crowdin for translations?
> > In affirmative case, do we hav
at 12:12 PM, julio cesar sanchez <
> jcesarmob...@gmail.com
> > wrote:
>
> > Hello everyone.
> >
> > I'm writing again because I wrote on another thread 3 months ago and
> nobody
> > answered me (http://markmail.org/message/aafqb42q2sc5awve)
> >
>
t; Hello everyone.
>
> I'm writing again because I wrote on another thread 3 months ago and nobody
> answered me (http://markmail.org/message/aafqb42q2sc5awve)
>
> So asking again, are we still using Crowdin for translations?
> In affirmative case, do we have any project manag
Hello everyone.
I'm writing again because I wrote on another thread 3 months ago and nobody
answered me (http://markmail.org/message/aafqb42q2sc5awve)
So asking again, are we still using Crowdin for translations?
In affirmative case, do we have any project manager on the project?
Do we
I'm resurrecting this topic because I've just created this issue
https://issues.apache.org/jira/browse/CB-11414
Are we still using crowdin for the translations, right?
What I talk on the issue about marking parts of the docs as hidden to not
be translated can only be done by "P
ntation site. I think the
> ideal goal is to have the docs site generate JSDoc pages for plugins and
> display them in style with translations and all; once that is possible, I
> think we should remove docs from README.md and encourage people to read
> docs on the site.
>
> Kindly,
goal is
to have the docs site generate JSDoc pages for plugins and display them in
style with translations and all; once that is possible, I think we should
remove docs from README.md and encourage people to read docs on the site.
Kindly,
Dmitry
> On Apr 22, 2016, at 6:24 PM, Jesse wr
But people also read it at github.com and npmjs.org, at least the English
versions
> On Apr 22, 2016, at 5:56 PM, Dmitry Blotsky wrote:
>
> I think the plan is to have the docs, as well as their translations, live on
> docs.cordova.io. The docs source is in each plugin's
I think the plan is to have the docs, as well as their translations, live on
docs.cordova.io. The docs source is in each plugin's source code, but the
formatted and translated output that people should be reading is on the docs
website.
Kindly,
Dmitry
-Original Message-
From:
isingj.com
On Fri, Apr 22, 2016 at 5:24 PM, Dmitry Blotsky
wrote:
> From what I understand, the process was to upload the files to Crowdin,
> and then download the translations generated by Crowdin and commit them
> back to the repo.
>
> Now the plugin READMEs are pulled in to t
From what I understand, the process was to upload the files to Crowdin, and
then download the translations generated by Crowdin and commit them back to the
repo.
Now the plugin READMEs are pulled in to the website build, and get translated
along with it. So, those individual language-specific
As far as I know, the translations are created in crowdin (
https://crowdin.com/project/cordova)
It creates the index.md, I have no idea about the README.md.
According to the mails on the list, Victor Sosa was the one taking care of
it but he didn't have enough time and Andrey Kurdumov took
First off, I apologize for not being up to date in how we handle
translation of plugin docs.
Second, I want to thank whoever has been.
So, looking thru the docs folder of the device-orientation plugin, I see
some very similar files ... each language folder appears to contain an
index.md and a READ
Hi Ian.
Yes, I'll look at it. Thanks for working on this
2014-10-06 13:48 GMT-05:00 Ian Clelland :
> I'm working on these now -- they should be mostly done by the end of the
> day today.
>
> Victor -- there were already some changes proposed to the spanish
> translat
I'm working on these now -- they should be mostly done by the end of the
day today.
Victor -- there were already some changes proposed to the spanish
translations in the Device plugin here:
https://github.com/apache/cordova-plugin-device/pull/17 -- some of them are
independent of your ch
Thanks for the introduction Lisa!
Happy to help the community a little bit :-D
2014-10-06 8:13 GMT-05:00 Lisa Seacat DeLuca :
> Team, just as an FYI, you should have been seeing some pull requests from
> Victor Adrian Sosa Herrera for the translation effort. I am mentoring him
> through helping
Team, just as an FYI, you should have been seeing some pull requests from
Victor Adrian Sosa Herrera for the translation effort. I am mentoring him
through helping out with translation so there will be someone else who
knows how the process works besides me. He is not yet a committer so
unfor
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-docs/pull/192
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature i
ions. We are using a crowd
> translation tool called Crowdin. The Portuguese translations can be found
> here: https://crowdin.net/project/cordova/pt-BR. If you have any
> questions on using the tool let me know. Basically you create a free
> account with Crowdin and then you'll
Bruno~
You can reach out to me for translation questions. We are using a crowd
translation tool called Crowdin. The Portuguese translations can be found
here: https://crowdin.net/project/cordova/pt-BR. If you have any
questions on using the tool let me know. Basically you create a free
up.
>
>
>
>
> On Tue, Feb 25, 2014 at 10:11 AM, Michael Brooks
> wrote:
>
> > Steve, I fixed the SL generation issue. The translations were missing the
> > config.json.
> >
> >
> > On Tue, Feb 25, 2014 at 6:12 AM, Lisa Seacat DeLuca > >wrote:
Thanks Michael! I will post them up.
On Tue, Feb 25, 2014 at 10:11 AM, Michael Brooks
wrote:
> Steve, I fixed the SL generation issue. The translations were missing the
> config.json.
>
>
> On Tue, Feb 25, 2014 at 6:12 AM, Lisa Seacat DeLuca >wrote:
>
> > Thank you
Steve, I fixed the SL generation issue. The translations were missing the
config.json.
On Tue, Feb 25, 2014 at 6:12 AM, Lisa Seacat DeLuca wrote:
> Thank you Steven. I am working on a new structure for the crowdin files
> and an automated script right now. It should be good by the end
Thank you Steven. I am working on a new structure for the crowdin files
and an automated script right now. It should be good by the end of the
week and we can also add the translations for each of the plugins.
I still need to figure out my rake issue so I can do the upload as well.
I'll
I have uploaded 3.4.0 docs for all of the languages except SL. SL doesn't
want to bin/generate on my machine.
On Fri, Feb 21, 2014 at 2:30 PM, Steven Gill wrote:
> Hey Lisa,
>
> I can look into this. I haven't actually done a version release for
> translations before.
Hey Lisa,
I can look into this. I haven't actually done a version release for
translations before. Should I update all of the languages?
The list of supported languages:
* de
* es
* fr
* it
* ja
* ko
* ru
* sl
* zh
If you (or anyone else) are interested in learning how to create new
ver
Even though the English documentation appears to be updated, the other
languages haven't been updated on our site since the 3.1 release.
http://cordova.apache.org/docs/en/edge/index.html
I know the documentation files have changed for the plugins and the
individual plugins themselves haven't
dev Digest 2 Oct 2013 17:49:05 - Issue 1635
> ------
>
>
>
>
>
>
> - Message from Marcel Kinard on Wed, 2 Oct 2013
> 11:43:24 -0400 -
> *To:*
> dev@cordova.apache.org
> *Subject:*
> Re: Translations
>
> The other t
1635
- Message from Marcel Kinard on Wed, 2 Oct 2013
11:43:24 -0400 -
To:
dev@cordova.apache.org
Subject:
Re: Translations
The other thing I mentioned in
https://issues.apache.org/jira/browse/CB-4964 is that (upon trivial
inspection) it appears that the translations sitting in the
The other thing I mentioned in https://issues.apache.org/jira/browse/CB-4964 is
that (upon trivial inspection) it appears that the translations sitting in the
edge dir actually are translations of 3.0, not 3.1.
- should those translations be published as 3.0 docs? (I'm tempted to say yes)
Chat: ldel...@us.ibm.com
Find me on: and within IBM on:
100 East Pratt St 21-2212
Baltimore, MD 21202-1009
United States
From: Andrew Grieve
To: Michael Brooks , Lisa Seacat DeLuca/San
Francisco/IBM@IBMUS
Cc: dev
Date: 10/02/2013 10:08 AM
Subject:Translations
Sent by:
Guys - should we be generating some non-english docs for 3.1.0?
1.0 Translations
> -
>
> Key: CB-2104
> URL: https://issues.apache.org/jira/browse/CB-2104
> Project: Apache Cordova
> Issue Type: Improvement
> Components: Docs
>
eiko!
Merged pull request as [commit
c988fa|https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;a=commit;h=c988fa6a72b053a77a36b87740a6acea7502f3b0].
> Pull Request #41: Japanese 2.1.0 Translations
> -
>
>
[
https://issues.apache.org/jira/browse/CB-2104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brooks resolved CB-2104.
Resolution: Fixed
Fix Version/s: 2.1.0
> Pull Request #41: Japanese 2.1.0 Translati
Keiko Oda created CB-2104:
-
Summary: Pull Request #41: Japanese 2.1.0 Translations
Key: CB-2104
URL: https://issues.apache.org/jira/browse/CB-2104
Project: Apache Cordova
Issue Type: Improvement
52 matches
Mail list logo
