ui - View the - context is needed

[Tobias Blue]

Hi, 

can someone explain the context of the »View the« string in the ui number 432.

»the« can be in german »der,die,das« or some other forms.

thanks, Tobias

[Ox Cart]

It precedes "page to find out more about ways to help" and refers to "page", so I guess it would be "die" as in "die Seite".

Cheers,

Ox

-----------------------------------------------------------------------------------------

"I love people who harness themselves, an ox to a heavy cart,

who pull like water buffalo, with massive patience,

who strain in the mud and the muck to move things forward,

who do what has to be done, again and again."

- Marge Piercy

--
You received this message because you are subscribed to the Google Groups "lantern-i18n" 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/groups/opt_out.

[_pa...@getlantern.org]

(Copying lantern-i18n)

Sorry for the delay, and sorry for the confusion. This is clearer in the source translation file due to the order of the strings, but it's possible Transifex doesn't preserve the order when using their editor.

In other places we do exactly as Tobias recommends and just include the html markup as part of the translated string[1]. However, in this case the markup works like this:

        {{ 'VIEW_THE' | i18n }}
        <a ng-click="openExternal(EXTERNAL_URL.getInvolved)">{{ 'GET_INVOLVED' | i18n }}</a>
        {{ 'GET_INVOLVED_CONTINUED' | i18n }}

Since we use <a ng-click...> there rather than <a href...>[2], if we moved everything into the translated string, the ng-click would non longer work, i.e. clicking the button wouldn't do anything.

It'd be nice to find a way around this, but in the meantime, I've added comments in Transifex for each of the three strings in question:

https://www.transifex.com/projects/p/lantern/translate/#sq/ui/15722819?comment=view_the

And I'll paste the comment here too:

This is one of three strings that, put together, make up a complete sentence:

"VIEW_THE": "View the",
"GET_INVOLVED": "Get Involved",
"GET_INVOLVED_CONTINUED": "page to find out more about ways to help.",

i.e. "View the «Get Involved» page to find out more about ways to help."

This occurs on the "About" screen that appears when you click the "About" link at the bottom of Lantern's UI. A demo UI is available at https://lantern-ui.nodejitsu.com/app/index.html so translators can see strings in context.

Hopefully that should make it clear in the meantime. As always, please don't hesitate to write to the lantern-i18n mailing list with any future questions.

[1] It should be noted that some translators continue to have trouble preserving the correct syntax of the html when including it in their translations, so this approach has its drawbacks too.

[2] to get the link to be opened in the system's default browser.

On Thu, Jan 2, 2014 at 10:54 AM, Ox Cart <o...@getlantern.org> wrote:

Yup, I'm with you.  The challenge is how to integrate that with the development workflow.  We can't put specific anchorsinto Transifex because the implementation is subject to change.  One potential option would be to use some sort of markdown syntax in Transifex like this:

View the [Get Involved] page to find out more about ways to help.

The application could then associate the markdown link [Get Involved] with the actual link in the app.

Reginald - any thoughts on this?

Cheers,

Ox

-----------------------------------------------------------------------------------------

"I love people who harness themselves, an ox to a heavy cart,

who pull like water buffalo, with massive patience,

who strain in the mud and the muck to move things forward,

who do what has to be done, again and again."

- Marge Piercy

On Thu, Dec 26, 2013 at 5:07 PM, Tobias Blue <toba...@gmail.com> wrote:

Thanks for Info. I don't why it is not posted in the forum.(bad interface)

Id would be better for all translators using complete sentences to build correct translated sentences.

Like:

»View the <a href="">Get Involved</a> page to find out more about ways to help.«

2013/12/13 Ox Cart <o...@getlantern.org>

Well, in the UI there's a link that goes between the two :)  Here's the English version:

Cheers,

Ox

-----------------------------------------------------------------------------------------

"I love people who harness themselves, an ox to a heavy cart,

who pull like water buffalo, with massive patience,

who strain in the mud and the muck to move things forward,

who do what has to be done, again and again."

- Marge Piercy

2013/12/13 Tobias Blue <toba...@gmail.com>

Thanks for the info.

Why not using one string for those two? It is better to translate if it is a complete sentence.

»View the« »page to find out more about ways to help«

»Ansehen, der« »Seite, um mehr über die Möglichkeiten der Mithilfe herauszufinden.« 

If it is a complete String 

»Die Seite ansehen, um mehr über die Möglichkeiten der Mithilfe herauszufinden.«

--
You received this message because you are subscribed to the Google Groups "Lantern Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lantern-deve...@googlegroups.com.
Visit this group at http://groups.google.com/group/lantern-devel.

[_pa...@getlantern.org]

On Fri, Jan 24, 2014 at 6:51 PM, toba <toba...@gmail.com> wrote:

Hi,

thank you two.

I don't know how the code works on Transifex.
But I think the comment in the translation helps every translator.

Same here. Thanks again for asking about this.

 

I change, in my translation, the words a little bit in the three strings. So the sentence looks better for me.

Looks like it now reads "Sehen Sie sich die Mitmachenseite an, um mehr über die Möglichkeiten der Mithilfe herauszufinden." As long as it looks good to Ox, it looks good to me :)

 

Thanks for your work.

Thank you for your contributions!

Since we use <a ng-click...> there rather than <a href...>[2], if we
moved everything into the translated string, the ng-click would non
longer work, i.e. clicking the button wouldn't do anything.

It'd be nice to find a way around this

I recently did implement an Angular directive that allows this to work. Here's a new example string that takes advantage of it:

https://www.transifex.com/projects/p/lantern/viewstrings/#en_US/ui/20658281?q=ng-click

I didn't go back and combine the "view the" / "get involved" / "page..." strings yet though now that we can, since they're already translated and working. Can do in a future pass though when it makes sense.

Best,

_pants

[Ox Cart]

All sounds good to me!

Cheers,

Ox

-----------------------------------------------------------------------------------------

"I love people who harness themselves, an ox to a heavy cart,

who pull like water buffalo, with massive patience,

who strain in the mud and the muck to move things forward,

who do what has to be done, again and again."

- Marge Piercy