Issue with updates to docs?

[Chris Holmes]

Not sure who else has got them, but we've had a user on transifex who's been submitting improvements to our docs.

He recently sent this message:

The ressources "Proxied sites" is now out of sequence and some strings have no start or no end after the last push to Transisfex.

Also there are many errors in the resources for which I created comments.

It looks like you changed that resource in github Todd? But it sounds like the automatic updating may have messed some things up in transifex? Any insight?

I'm going to try to go through the issues that the user submitted to fix some of them in the core docs.

C

[Chris Holmes]

More from him:

I manage many projects' translations but in Transifex not in GitHub, since it's the best way for me to manage the time I give to the community.
I'll review the responses you left to my comments. Ideally, when there is a comment in Transifex and something needs to be fixed, someone in the dev team should address and fix that. We all are very busy. But I'll take a look at the resource in Transifex. It's only 4 strings that don't make sense in Transifex for Proxied sites:

#7 "Lantern to Get Access, and is available through the globe icon in the"
String # 6 is a title "Proxied site" so this string # 7 has a missing start of sentence or is out of sequence.

#35 "likely work better for you than the default list that ships with"
"that ships with what"? The next string is an image and this sentence has no end!

#39 "proxy sites you don't need to."
This follows a title and has no start of sentence.

#171 2in your Lantern. Be sure you delete your existing list (or copy over it), so you don't get duplicates and don't"
This string is the last one ans has no end "and don't"???

cholmes a écrit :
> Hey Alain-Olivier, thanks so much for all your help!
> 
> Did you see my message as a comment on one of your
> comments?
> 
> We don't manage the actual docs in transifex, but
> instead on github, at
> https://github.com/getlantern/lantern-docs/tree/master/lantern/en/user
> 
> This probably lead to things being out of sort, as we
> don't have the process totally perfect yet.
> 
> But it's much better to manage the core docs in github
> directly, so for the issues you create if you want to
> help us further you could edit directly in github. I'll
> try to make a tutorial on how to do that soon.
> 
> Also, if you could introduce yourself on our
> translation list at
> https://groups.google.com/forum/#!forum/lantern-i18n
> that'd be great!

[Todd Blose]

Thanks for compiling these.

--
You received this message because you are subscribed to the Google Groups "Lantern Internationalization" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lantern-i18n...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Chris Holmes]

So it looks like most all his issues are places where a newline just cut off part of a sentence.

I only put the newlines in to keep things around 80 characters in the source file. But we don't need to do that.

If it helps things update better in transifex I think we could just have the source files be one sentence each. Shorter lines are a bit better for better diffs. But I think lines that are each one sentence could make good sense.

And it seems like it'd be better to have things update automatically? Like so we can easily just change the docs and don't have to do some manual fixing to keep things in sync. How did you originally put the strings in transifex? Like how what were the break points for how long each transifex string is?

[Todd Blose]

All I did was pull the documents out of the wiki and github and uploaded/organized them as separate Transifex resources.  Transifex automatically detected most of the strings accurately, but, as you point out, newlines caused several to be incorrectly parsed. I assumed the breakpoints had been pre-determined.

If we want to apply the changes the translator reported, we'd update the documents in the lantern-docs repo, but is there a way to automatically sync those changes with Transifex without having to re-upload/blow away previous strings that were already translated? Is there an easier way to synchronize Transifex resources directly with the documents in our github repo?

Thanks,
Todd

[Chris Holmes]

On Tue, Jun 3, 2014 at 12:08 PM, Todd Blose <to...@getlantern.org> wrote:

All I did was pull the documents out of the wiki and github and uploaded/organized them as separate Transifex resources.  Transifex automatically detected most of the strings accurately, but, as you point out, newlines caused several to be incorrectly parsed. I assumed the breakpoints had been pre-determined.

Cool.

 

If we want to apply the changes the translator reported, we'd update the documents in the lantern-docs repo, but is there a way to automatically sync those changes with Transifex without having to re-upload/blow away previous strings that were already translated? Is there an easier way to synchronize Transifex resources directly with the documents in our github repo?

Ah, I thought you had done this piece already. But yeah, there definitely is. I _think_ pants set it up for our other strings, like the UI. So may be some source code in there to borrow. I think the general strategy is to use the transifex tx client - http://support.transifex.com/customer/portal/articles/960804-overview and then hook it up to a continuous integration system. I have a friend who set these up a lot, so if pants can't help then can ask him for quick advice.

C

[Chris Holmes]

Oh, and the other thing we'll need to set up is to also sync from transifex back to the docs repository, for the other languages. French Canadian should now have lots of good stuff to test with.

[Chris Holmes]

Alright, I think I fixed all the formatting so breaks are at the periods. So things should show up better in transifex.

So we should update transifex. This will break some good work already done, but will make things easier for all the other coming translators. Todd, let me know when you get that done, as I want to get our Iranian friends on it.

And when are you pushing the docs to the website?

 And would be great to get the docs automatically updating to and from transifex. New english strings should auto-update the source in transifex, and new translations in transifex should automatically update our translation strings, like in https://github.com/getlantern/lantern-docs/tree/master/lantern/cn