workflow for non-developers? about discovermeteor_ja HOT 8 OPEN

Wow that's awesome! But if people have access to the repo they can actually
edit markdown files right inside GitHub and commit them through the UI
without having to learn anything about Git itself. So I think that's
already a pretty good solution?

On Thu, Oct 9, 2014 at 1:38 PM, dc [email protected] wrote:

@SachaG https://github.com/SachaG I had a couple of people email me and
someone has made huge progress with the japanese translation.

https://drive.google.com/folderview?id=0B3NKQUsJ7bKsZ0l3YmxuaTlJR1k&usp=gmail

however, they aren't developers so not sure of the whole workflow with
pull requests etc.

I'm sure you considered this but is there too much overhead in setting up
a web based UI for managing the crowd-sourced translations? this would
significantly lower the barrier for non-devs to contribute a few strings
here and there, and also not step on each other's work.

For meteor I've seen Gadi's https://github.com/gadicc/meteor-messageformat
project which gives a way to manage all the strings like this:
http://messageformat.meteor.com/translate
It also tracks updates etc.

There maybe other tools out there (non meteor) too and I guess various
platforms that are also free to use for open source:

http://www.quora.com/Are-there-any-good-open-source-collaborative-translation-apps

—
Reply to this email directly or view it on GitHub
#4.

from discovermeteor_ja.

OK, i'll suggest that. it does still make it a little bit of work to pick out the translatable text from the rest, but i guess it's a lot of work to isolate the strings.

from discovermeteor_ja.

cc @nwilkes FYI

from discovermeteor_ja.

What do you mean by "isolate the strings"? Which strings?

On Thu, Oct 9, 2014 at 4:01 PM, dc [email protected] wrote:

cc @nwilkes https://github.com/nwilkes FYI

—
Reply to this email directly or view it on GitHub
#4 (comment)
.

from discovermeteor_ja.

isolate the strings as in picking out just the parts that need to be translated. for example here:

<%= screenshot "mongo-shell", "The Mongo Shell" %>

would be

<%= screenshot "mongo-shell", tr("The Mongo Shell") %>

(I'm assuming that's the only part needing translation as the first mongo-shell param links to a filename and the second part is the caption text?)

so then capturing the params of all the calls to the tr() method, we could provide a simple spreadsheet like list of items to translate. but yeah, that's a lot of work upfront.

from discovermeteor_ja.

I'm afraid that's not technically possible… Plus I'm not sure if
translating individual strings without the context of the rest of the book
would work very well?

On Sat, Oct 11, 2014 at 1:52 PM, dc [email protected] wrote:

isolate the strings as in picking out just the parts that need to be
translated. for example here:

<%= screenshot "mongo-shell", "The Mongo Shell" %>

would be

<%= screenshot "mongo-shell", tr("The Mongo Shell") %>

so then someone would get a simple spreadsheet like list of items to
translate.

—
Reply to this email directly or view it on GitHub
#4 (comment)
.

from discovermeteor_ja.

Hi DC and Sacha,

In the first Email coming from Matsumoto-san, It was not clearly mentioned
that we can use Matsumoto-san's translation work on behalf of him. I let
him to decide how he wants; He needs help for setting up Git hub or letting
us to use his translation work. I hope I can hear from him soon.

I experienced on translation of "Isolating the strings" using "crowd in".
It was difficult for a translator not knowing what is the context of the
story.(It was also for programming.) Using Git Hub make sense to me, since
Meteor is for developers or/and potential developers. It is going to be a
part of learning.

I have similar frustlation with DC that there is only few of volunteers for
Japanese translator not only for Meteor but else where.

Thanks,

Naoko

On Tue, Oct 14, 2014 at 5:43 PM, Sacha Greif [email protected]
wrote:

I'm afraid that's not technically possible… Plus I'm not sure if
translating individual strings without the context of the rest of the book
would work very well?

On Sat, Oct 11, 2014 at 1:52 PM, dc [email protected] wrote:

isolate the strings as in picking out just the parts that need to be
translated. for example here:

<%= screenshot "mongo-shell", "The Mongo Shell" %>

would be

<%= screenshot "mongo-shell", tr("The Mongo Shell") %>

so then someone would get a simple spreadsheet like list of items to
translate.

—
Reply to this email directly or view it on GitHub
<
https://github.com/DiscoverMeteor/DiscoverMeteor_Jp/issues/4#issuecomment-58738196>

.

—
Reply to this email directly or view it on GitHub
#4 (comment)
.

Azul Technology
Naoko Hasegawa Wilkes
Cell 080-3939-4071

from discovermeteor_ja.

@nwilkes if matsumoto san created all those translations, I'm sure it was with the intent they should be contributed to the project? i think he was just confused how to use github. I didn't see any further mail with him and don't think he even has a github ID. i guess he translated from the downloaded PDF of the book or something... ? また連絡取ってますか？

そうですね。エンジニアじゃないと、どの部分を翻訳すべきか、もしくは触らない方がいいのか、分かりづらいっすね。

from discovermeteor_ja.