I'm not sure that it's fully correct russian translation. In russian language correct term for "follow" is "следить" or "читать", but I choose term "подписаться" (correct translation for "подписаться" is "subscribe") because it sounds better in russian language.

Also translation's for "object_type_" choosed in assumption that "object_type_" strings would be used only in

%1$s %2$s %3$s %1$s %2$s %3$s in reply to %4$s

messages. Because "Somebody create collection" translate in russian as "Кто-то создал коллеки_ю_", but "collection" translates as "коллекци_я_" (see to last char of word "коллекци_я_").

But despite this problems I use this translation.

I created the comment_meta_at to preserve the “at” in English, while allowing languages that have no such preposition for dates (such as Czech) to use a comma.

Now I realized English doesn't need this either. You don't say “comment by Evan Prodromou at 28 April 2014”. “At” would only be used for times of the day. And other languages will have their own specifics. So why not just use the comma to avoid confusing translators with all this “\u0020at” business?

Plus a backslash that is now required before an apostrophe.

When you stop following a user, the standard verb of this activity (used by other clients) is “stop-following” (according to http://activitystrea.ms/head/activity-schema.html#verbs), but impeller posts it as “unfollow”, which is not included in ms_verbStrings for localization.

So we are in a curious situation where Impeller doesn't understand it's own activities.

We could either add “unfollow” to ms_verbStrings and point it to the same localized string as “stop-following”, or we can change it to “stop-following” comply with the activitystrea.ms standard. I would say this solution has the advantage of compatibility with other pump.io clients. Introducing new verbs for the same action would add more complexity other developers will have to deal with if they want to parse actions or implement i18n in their applications.

I want pump.io to become widely adopted in my country, and for that, we need a good client in Czech, because language barrier is a serious obstacle for most people here. Please pull the extended i18n (#1) too, this localization needs it to be fully functional.

Problem: If you start writing a comment, and you tilt your smartphone to the side before you send it, your text will be lost and you have to start typing it again. This could be annoying if a user is forced to retype a long reply.

Cause: Reply text is not saved in the instance state. Automatic saving mechanism doesn't see the EditText field, probably because we create it dynamically.

Solution: Explicitly keep the unfinished reply text in instance state to avoid loosing it on screen rotation.

Transifex doesn't support this special form of string values written as attributes, it just says no values were found - I had to change this file to normal format to import it. This means that the automatic webhook importing mechanism will overlook any strings written in that attribute form.