Closed Ara-cole closed 9 months ago
The extension supports 172 different target languages. I'm not sure how many different languages it can detect for the translation to start automatically. Although so many languages are supported, I myself only access websites in 3 or 4 different languages.
When you access a website in a language that is not yet on your list, is it so difficult to click here?
Is the reason for it being " Unusable! " just for the hassle of clicking that button or is the extension really not working for you?
What is your browser and version?
Is the reason for it being " Unusable! " just for the hassle of clicking that button or is the extension really not working for you?
Yes, why do I need that hassle? do you like it? or do you just dump a list of lang codes from a variable or file extracted from locales to the configuration file of your addon (that I couldn't find and I shouldn't as an end user) on your everyday use? I wonder if you take the same hassle every time you debug it.
It works I think, I'm sorry, I'm a bit angry that you didn't add something as simple as a translate every language instead of forcing the user to pick each language one by one. As simple as read list from file at the bottom most.
Why did you do that?, have you typed all those language names by hand or have you generated them automatically from a locale list? Please add a select all languages button and I'll love your add on.
Also, there's lot of languages dying for lack of speakers. Your addon if better done would help for those languages to be writted in.
You only need to click once for each language. If you do this a couple of times, most of the websites you access should already be translated as soon as you access them. With only about 5 languages defined to always translate, it is enough for the vast majority of people. If the extension cannot detect the language, then in this case, there is no point in having 200 languages in that list as the translation will not start automatically.
If it's just that, it seems like free hate. Nothing will be done, I'm sorry.
With only about 5 languages defined to always translate, it is enough for the vast majority of people.
Not for me. I took the hassle of selecting 200 languages by hand and it works well in wikipedia at least. I'm happy now that i'm not language trapped anymore and I can read wikipedia in every language thank to you and... me.
Don't webpages have a language tag in the header? Is that much effort to add a select all button? I was not going to take the unnecesary hassle, so I was being sincere that for me it was going to be unusable and it will be in the future surely as I will have to reconfigure this again and again.
To avoid losing your settings when reinstalling the extension, simply make a backup and then restore it when needed. You can backup in storage settings.
And unless there is some search engine that you search in one language, and it shows results from sites in dozens of different languages, it seems unlikely that you will come across more than 5 different languages.
And unless there is some search engine that you search in one language, and it shows results from sites in dozens of different languages
That feature would be awsome but inluckly language barrier is something that internet remained ignorant since ever, so search engines get you locked in your language. As for reality, the most prominent use cases of my request is wikipedia, which has links to every existing language and dead ones.
I'd really like to write an add on to search in many languages as well, using common search engines like google. It's very simple to do in bash, though I don't know how to bypass the limitation of google translate requests, that closes if requests are done too often. The rest is just matter to convert the original search keyword to "
BTW, please tell me, where is the file where your add-on stores the languages to translate? In order to do cat lang_list>>conf_file next time.
Well that something, but i fear that if I type that adress I wont reach that page, how did you do that? At least now I know the variable name. let me do find | grep \"alwaysTranslateLangs:\" /s
`#!/bin/bash all_langcodes="aa af agr ak am an anp ar ayc az as ast be bem ber bg bhb bho bi bn bo br brx bs byn ca ce chr ckb cmn crh cs csb cv cy da de doi dsb dv dz el en eo UTF-8 es es es et eu fa ff fi fil fo fr fur fy ga gd gez gl gu gv ha hak he hi hif hne hr hsb ht hu hy ia id ig ik is it iu ja ka kab kk kl km kn ko kok ks ku kw ky lb lg li lij ln lo lt lv lzh mag mai mfe mg mhr mi miq mjw mk ml mn mni mnw mr ms mt my nan nb nds ne nhn niu nl nn nr nso oc om or os pa pap pl ps pt quz raj ro ru rw sa sah sat sc sd se sgs shn shs si sid sk sl sm so sq sr ss st sv sw szl ta tcy te tg th the ti tig tk tl tn to tpi tr ts tt ug uk unm ur uz ve vi wa wae wal wo xh yi yo yue yuw zh zu"
query="$*" local=$( echo $LANG|cut -d_ -f1 )
langcodes=$(shuf -e -n32 $all_langcodes ) for code in $langcodes; do transquery=$(./trans -b "$query" -s $local -t $code) if not test "$transquery" == "" ; then
oquery="\"$transquery\" OR $oquery"
echo $oquery
fi
sleep .1
done
` firefox "https://www.bing.com/search?q=$oquery"
My beloved:
Manual input of every language to translate, no all/none/select option, not even choose from file. Even worse, desplegable list doesn't update, so you are forced to pick one by one. Some things are if not all happens nothing happens. Al least for my use case that I need autotranslate for any page in any language, not just those I pick from a desplegable list that doesn't even update! Hpe that you programmed this picking each character from a desplegable list that doesn't update instead of just typing it. I mean those things that look like broken on purpose, everythings works well but you have to select each language to auto-translate., when I'm sure that you autogenerated that list from some locales.