Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rating Dialog #1369

Merged
merged 1 commit into from
Nov 27, 2015
Merged

Rating Dialog #1369

merged 1 commit into from
Nov 27, 2015

Conversation

mfietz
Copy link
Contributor

@mfietz mfietz commented Nov 9, 2015

7 days after the first app start (or 7 days after the upgrade):

rating

If the user chooses remind me later, we wait another 7 days and show the dialog again.

@keunes
Copy link
Member

keunes commented Nov 10, 2015

Nice

@johnjohndoe
Copy link
Contributor

@mfietz Are you going to add translated strings for other languages?

@mfietz
Copy link
Contributor Author

mfietz commented Nov 19, 2015

@johnjohndoe After this has been merged, we will push the strings to Transifex where they will be translated.

@johnjohndoe
Copy link
Contributor

@mfietz Is it also possible to request stings from Transifex while you are on the branch? This would enable to collect all needed data first before it is merged into master?

@mfietz
Copy link
Contributor Author

mfietz commented Nov 20, 2015

@johnjohndoe Transifex is no automatic translation service (at least we are not using it that way). We upload the new strings (in english, only) and volunteers translate the strings manually via their web interface. Later, we pull the translations. (I could have added translations for German, but we would then have to merge my "local" changes with changes already made on Transifex - translations of so far untranslated strings or changes to the translation -, I don't see any use in making it any more complicated than it already is)

Transifex can make suggestions for a translations, but they are not reliable enough.

@johnjohndoe
Copy link
Contributor

Understood. Does this also work while you are on the branch?

@mfietz
Copy link
Contributor Author

mfietz commented Nov 20, 2015

Why shouldn't it?
In the repo, we are the only ones writing to the english strings, all the other languages are only ever updated by pulling translations from transifex. No conflicts.

@johnjohndoe
Copy link
Contributor

I was not thinking about conflicts, just about a complete feature branch. It appeared incomplete to me for being merged into master (where potentially automatic checks could run to approve that strings in all languages are present).

@mfietz
Copy link
Contributor Author

mfietz commented Nov 20, 2015

What would we gain from such checks?
Android won't complain, if a language lacks a translation, it just uses the english string.
What to do with the information that a language is incomplete? If there are not volunteers to translate a language or new strings, we just have to live with that

@johnjohndoe
Copy link
Contributor

Such a check could be used as an automated quality control. Running it via continuous integration (such as Travis CI) would warn you before the branch is merged. - On the other hand it is a matter of agreement of the project setup. If you already decided that a fallback to English is fine then this what we all should be aware of.

@keunes
Copy link
Member

keunes commented Nov 20, 2015

I guess automated quality control would be nice, but some flexibility as to not bothering developers if a few strings are missing would be a requirement (accepting English as a fallback, indeed). I.e. only show a warning if less than 75% of the strings are translated. But doubt that's easy to set up or even possible.
Note that some kind of check seems to be done by the developers themselves.

@TomHennen TomHennen added this to the 1.4.1 milestone Nov 27, 2015
TomHennen added a commit that referenced this pull request Nov 27, 2015
@TomHennen TomHennen merged commit 9dc80b1 into AntennaPod:develop Nov 27, 2015
@mfietz mfietz deleted the rating branch February 7, 2016 08:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants