Lineflyer

I have read somewhere over here, that it is difficult to upgrade the support. But ..just asking: To me it looks like the original author just took 1:1 the mapsforge...

Correct as @eddiemuc posted it. I am asking myself: The current mapsforge implementation in WhereYouGo somehow looks like some "default" 1to1 copied from Mapsforge. Can that be the case? If...

Its a language code mapping on Crowdin. I could set this up easily, but what to do with brazilian then? 

For comparison, that is what we use for c:geo: 

Its not bound to Github integration but a generic setting for the Crowdin project, you can find it in the settings in the section "export" behind "language mapping": 

> The pt_BR should stay unchanged, like zh_TW for c:geo. That would mean I simply remove the pt to pr_rPT mapping then. However there was a reason I did that...need...

In https://github.com/cgeo/WhereYouGo/issues/23#issuecomment-610352494 I noted down, that without this `rPT` theere is something missing from Crowdin....but we can try what happens. Not sure if it will work as I also mention...

@moving-bits Do you remember from c:geo how to define a proper accent color throughout? I guess it somehow need to be injected into the material theme somewhere...

> Monterra devices are still running on Ice Cream Sandwich (Android 4.0.4, API level 15). Same problem as in c:geo. Say goodbye to those unmaintained devices...its a real shame for...

That should be no problem: We have a legacy branch, which is equal to 0.9.3. So we just need to push the https fix commit on top of that.The question...