A place for Extension Authors to post and receive feedback on Extensions still in development. No Extensions within this forum should be used within a live environment!
SeewolfPK wrote: Fri Jul 07, 2023 12:10 pm
I am back to RC3.
With this I have the error and users have to choose their language
rc3.jpg
There is nothing I can do about that error in 3.3.0_RC3 which is why I have rebuilt it into 3.3.1_RC1 (but then that doesn't entirely work for you either)
SeewolfPK wrote: Fri Jul 07, 2023 12:10 pm
Only problem is working as admin. This only works if I change to english language in the transklation tool.
I suspect that is a conflict between the translated text and the text that phpBB is expecting and probably nothing that can be done about it
I will see, what users say, when I go online with a new forum.
I will give the users then the information
Nach einem Browser Neustart muss die Sprache neu gesetzt werden. --> undefined
After restarting the browser, the language must be reset. --> undefined
Na het herstarten van de browser moet de taal worden gereset. --> undefined
Après le redémarrage du navigateur, la langue doit être réinitialisée. --> undefined
Dopo aver riavviato il browser, la lingua deve essere reimpostata.--> undefined
După repornirea browserului, limba trebuie resetata. --> undefined
Después de reiniciar el navegador, se debe restablecer el idioma. --> undefined
După repornirea browserului, limba trebuie resetata. -> undefined -
HiFiKabin wrote: Fri Jul 07, 2023 10:30 am
Exactly so, but there is a way around it by using the code I have posted in the first post of this topic. The gTranslate code ignores anything wrapped in the ignore code. Not the easiest way to get the desired result, but trying to create an "ignore these words" list would be a never ending nightmare
That sounds interesting but I am unsure how to achieve this
In your code how do I add words like Deus and Allectus to be ignored ? could you please give a example ?
Is it something you simply add to the html or bbcode ?
Its not something I have ever used before.
Or does the code simply get me back to just the overall forum being translated ?
Thanks
If you set that BBCode on your board, then any text wrapped in that BBCo0de will not be translated. You can see the effect on my demo site with "This Post Is Written In ..." That would work for brand names etc, although your users would have to do that with each post. Inconvenient I know but I can not think of another way around it.
Also anything within the code tags is not translated either
The template files are a different matter, so (for example) every time username appears in the template it would need to be wrapped in the "notranslate" HTML code. I do not know it that would be possible using an extension but I am investigating further.
Did both JS Codes updated by the developers or just the current one? Maybe you can also show how to color and adjust the dropdown boxes for the personal needs from the latest version.
On the other hand, I would like to report a bug when the extension Digital Clock is activated: depending on the date and time format chosen, there is a flickering which occurs and it is very unpleasant...
encreuse.net
Forum version : 3.3.11
php version : 8.2.10
Thanks for the colors first, as I only had the ones from the old post from old translators and not the ones from the new one. I tried this right away, unfortunately the translator seems to translate everything immediately despite the correctly recognized language and there seems to be only one style but no more settings as in 3.30 RC3 or ?
There is only one style folder, and it translates immediately, even if I don't want it to. So I can no longer set that nothing is translated in the following language at first. This, of course, destroys the complete function and internationality of my forum. If someone wants a translation, they should be able to decide for themselves. So, I will probably have to stay with 3.30 RC3, as this destroys my multilingual posts and international buttons.
It should not necessarily always translate everything immediately and at least not translate the set base language. But unfortunately, there are likely no more settings where this is possible, and I don't know if I can just change the style folder and continue to use the other language setting data in the ACP. In the old version, this version was also available all the time and worked fine there, so why is this now suddenly gone?
If the first option inside this dropdown box would something like NO TRANSLATION by default and only translate if a language would be selected, I think it would work nice.
Miri4ever wrote: Sun Jul 09, 2023 10:03 am
If the first option inside this dropdown box would something like NO TRANSLATION by default and only translate if a language would be selected, I think it would work nice.
HiFiKabin wrote: Sun Jul 09, 2023 11:05 am
this version is the best compromise I can come up with (and it is very much a compromise) although I am still trying to improve it.
Regardless if this EXT cannot be improved further your efforts are very much appreciated, certainly from my end as without you we have nothing