SmartCookieWeb: [Bug] SmartCookieWeb v10.x Bugs

I’ll try and look at ways to optimise the app animations.

I’ll fix the string now.

For large pages, I’m mostly a bit worried that I’ll run out of translate credit (I’ve got ~2 million characters/month). I might change it so that text selected from web pages (in a future release) or reading mode pages (in 11.0.0) shows a ‘translate’ button above it which translates the text in-place instead of taking you to an external app. I’ll see what I can do with full-page translation.

Yeah, there’s only a fee if you’re intergrating the translation into your own application. The database is mainly so that if you reload a page it doesn’t all translate again, and if someone else has been to the same page before, the translations are remembered so accuracy should be the same as a normal translation. I’m not too worried about the size at the moment - hosting it should be cheaper than just translating things again - but I’ll have to think of a plan for further down the road when lots of people are using the translate extension.

I’ve got a basic version of the extension working between English and French, so I’m hoping that I can get a beta done in 1-2 weeks to test out.

Yeah, DeepL is great, the main issue is that the API is fairly expensive (€5/month + €20/million characters), but I was thinking of storing already translated sentences in a database to cut down on costs so translating a website twice will only cost the price of one translation. I know that doing that isn’t allowed with Google Translate, but there doesn’t seem to be any restriction on DeepL. I could always contact sales as well and see what they can do.

I’m uploading a fixed APK now, but unfortunately I had to correct the export process too so old exports won’t fully work. I modified yours to the correct format in case you want to keep it:

{“blockCookieDialogs”=“true”, “thirdParty”=“true”, “link2”=“https://crowdin.com”, “blackStatusBar”=“false”, “suggNum”=“0”, “search”=“7”, “clearWebStorageExit”=“true”, “Theme”=“1”, “textsize”=“4”, “secondBar”=“false”, “link4”=“https://www.deepl.com/translator”, “searchSuggestionsChoice”=“1”, “link1”=“https://github.com”, “ssl”=“true”, “startPageTheme”=“false”, “textreflow”=“true”, “readingTextSize”=“2”, “invertColors”=“true”, “noAmp”=“true”, “darkmode”=“true”, “firstLaunch”=“false”, “cache”=“true”, “downloadLocation”=“/storage/emulated/0/Download”, “incognitocookies”=“false”, “stopIntent”=“true”, “link3”=“https://weblate.org”, “translate”=“true”, “clearHistoryExit”=“true”, “dize”=“2”}

@CookieJarApps My settings, maybe this will help with something.

{blockCookieDialogs=true, thirdParty=true, link2=https://crowdin.com, blackStatusBar=false, suggNum=0, search=7, clearWebStorageExit=true, Theme=1, textsize=4, secondBar=false, link4=https://www.deepl.com/translator, searchSuggestionsChoice=1, link1=https://github.com, ssl=true, startPageTheme=false, textreflow=true, readingTextSize=2, invertColors=true, noAmp=true, darkmode=true, firstLaunch=false, cache=true, downloadLocation=/storage/emulated/0/Download, incognitocookies=false, stopIntent=true, link3=https://weblate.org, translate=true, clearHistoryExit=true, dize=2}

Thanks, that did help. It seems like 1) if the backup is named anything other than SettingsExport and then any numbers, and 2) if you have any settings that involve entering text into a field, the import fails. I’ll add a fix for text settings as soon as possible in the next beta.

@CookieJarApps The homepage of incognito mode looks like this in v10.1.0-beta1, in addition the incognito mode takes a long time to open the first time (in fact it has always been so, at least since the v8.x).

I’ve just published beta 2, in theory it should fix the incognito homepage

I’ll make some more improvements in the next update. I completely forgot about the first launch page - thanks for reminding me 😃

Oh ok sure, thanks. I’ll fix the overlap now.

@CookieJarApps Translation extension bugs:

1. Does not detect the language of the phone: In fact the app in general has problems with this, because as seen in #148, the Onboarding page only appears when the app is in English as well.

2. Sometimes does not load the images of the translated site.

3. You can’t log in or continue to log in to a translated website: This is an app bug because the same thing happens with google translator. The correct would be the login part not to import at the time of translation and only the texts of the sites be translated. This is a seemingly common bug in privacy and security-focused browsers such as SCW and Bromite.

I think when these bugs are resolved the extension will be perfect because currently it is already working very well.

For the first issue, I think the issue with auto device detection only occurs on languages like pt-BR that have a second part to the language code (I tested French and it seemed to work correctly) - should be pretty easy to fix. I forgot to enable onboarding for all languages after translations were added, all I have to do is whitelist languages with translations for it in the next update.

For the other 2 issues, the best option would probably be for me to create some sort of web program where every block of text on the site can be sent to it for translation and then returned and replaced on the page. This’d probably be a nice solution too because people would be able to self-host so they know that the visited sites aren’t being stored anywhere and you’d be able to choose the translation API.

Ok, I know what’s probably wrong there, thanks for the bug reports, I’ll release a fixed update this week.