moving-bits

> > If you are going to refactor in this area, maybe you can have a look at [#17040](https://github.com/cgeo/cgeo/issues/17040) and [#17041](https://github.com/cgeo/cgeo/issues/17041) (which seem to be related to offline translation)? Both...

Currently we split the input into small chunks of non-HTML and HTML-containing parts. Depending on the specific input this may lead to single words getting translated separately, with "half-sentence chunks"...

When I long-tap on some text, a small popup opens offering "select all" and "translate". The latter option opens Google translate in an overlay window. Those translations are ok for...

My 2 cents on it: - Main benefit of a separate block with "translate" button is accessibility (easy to reach) in visibility (making this feature being seen by the users)....

> > * […] add long-tap action on listing text / hint (+ maybe a menu entry for translation). > > Wouldn't that remove text selection? Fair point. Floating action...

@novw: > So: leave it up to the user to figure out if the listing is in Thai or Malay? Sound like user unfriendly behavior to me. It worked. Flawlessly....

Hey everybody, I just entered reading this discussion here and in other issues/PR related to markers' topic this morning. I have to admit that I find the language used currently...

This issue came up again on support recently, see #17005: > I remember having that discussion quite some time ago, but could not find the issue any more... (IIRC we...

Proposal: - let the user decide, which version they want to have downloaded as default (=> setting); default value for this is the "large" (640 px) version as a compromise...

If we want to avoid a setting at all costs, how about this: - download original version, if connected to WiFi, - download "large" (= 640px) version if connected to...