[CDB] gTranslate

[stone23]

download and unzip the attached, uploading it to:-

ext/chris1278/jsclock/styles/prosilver/template/event/

replacing the original file and purge the boards cache

(I have wrapped the notranslate span around the code that needs to be ignored by the translate script)

Thanks, it works.

[HiFiKabin]

download and unzip the attached, uploading it to:-

ext/chris1278/jsclock/styles/prosilver/template/event/

replacing the original file and purge the boards cache

(I have wrapped the notranslate span around the code that needs to be ignored by the translate script)

Thanks, it works.

No Problem

[Miri4ever]

I found this solution for the problem now, I am satisfied with:

Use 3.30 RC3 Version and use the style files from 3.31 RC1

And then add this code from the old 3.30 RC to the new style:

Code: Select all

      "default_language":"{{ TRANSLATE_DEFAULT_LANG |escape('js') }}",

Now anybody can select his home language for the translator and this home language is not anymore translated. So your page's default language cannot be translated, and you can use several languages. But you need to old setup acp things back.

And if those BBCodes should be created we definitely need also an installer inside the extension.

[Chico Gois]

Or what languages do you want to appear

Code: Select all

"languages":["en","fr","de","ja","nl","it"],

[Miri4ever]

Possible but it's not the users' work to modify files on its own just to switch settings. So, this solution from a mix of old and new code is for now the best situation until we find our own way to add a no translate field with JS code. And nobody needs to translate its page with the origin language.

[Mick]

Use 3.30 RC3 Version and use the style files from 3.31 RC1

Presumably you mean versions 3.3.0_RC3 and 3.3.1_RC1 etc?

[SeewolfPK]

A request:
If changes are announced here, please indicate in which file exactly the changes should be made.

[HiFiKabin]

Now anybody can select his home language for the translator and this home language is not anymore translated. So your page's default language cannot be translated, and you can use several languages. But you need to old setup acp things back.

Correct, but then not all posts will be translated. I built the current version to solve that more important issue.

And if those BBCodes should be created we definitely need also an installer inside the extension.

What BBCodes? If you the notranslate BBCode then that is not needed for the extensions correct operation but can be added is the board owner wishes (just like any other BBCode)

find our own way to add a no translate field with JS code

As I have said before, I totally agree but unless gTranslate are willing to alter their code (and remember the code is not just for this extension) then it will not happen.

Or what languages do you want to appear

Code: Select all

"languages":["en","fr","de","ja","nl","it"],

That is the only way thus far that you can limit the number of languages available for translation, however as it requires the extension file to be edited it would not pass validation

[warmweer]

Code: Select all

"languages":["en","fr","de","ja","nl","it"],

That is the only way thus far that you can limit the number of languages available for translation, however as it requires the extension file to be edited it would not pass validation

Perhaps a configuration setting in which languages can be ticked or just entered (limiting the translation to those languages)?
However, the point of the extension is to provide translated pages. Some actions shouldn't really be available in translated mode: e.g. editing, deleting, posting/quoting?).

Personally I wouldn't try to fix the visual glitches too much as the widget may change in the future, and I know of another widget (different company) being developed, which (if it is better that the one used at this time) may render the current widget outdated.

[Chico Gois]

Personally I wouldn't try to fix the visual glitches too much as the widget may change in the future, and I know of another widget (different company) being developed, which (if it is better that the one used at this time) may render the current widget outdated.

In general, this extension is a good example not only of exercising the imagination but also of learning.

[warmweer]

...
In general, this extension is a good example not only of exercising the imagination but also of learning.

Agreed but there has to be a cut-off point somewhere.

[Miri4ever]

No I was talking about 3.3.0 RC3 and 3.3.1 RC1 as I wrote.

I just did a quick test with mine to translate the page and topic to whatever language. As far I can tell, anything is translated as those not translated you concern about were inside the JS Code from 3.3.0 RC3, and they made some updates with the browser detected and further refinements since 3.3.1 RC1.

So doing this mix I created with set up the translator to board language by default seems to do an impressive job and not break any moderating features, any design, any extensions and usernames so far. Sure, translated pages look horrible with many extensions and texts outside buttons, but most will only use for a special text to get translated. And for the good translations we can still use the SIMPLE TRANSLATE Plugin with even better doing as Google ever can do.

I just did a brief look at the base JS Code and as we can adjust colors, and browser detect. I think it's also possible to create a variable for inserting a no translate flag, into this country list, via HTML / JS inside the extension itself. The same way we change colors.

And it even should not do auto-translate by its own if there is no request. This seems to work for now with the old code, the new style code from the latest release, plus this one code line I added from the old styles. It would be the same fun thing a car would start driving on its own without a driver, just because it's a car.

Yeah, sure I know about those BB Codes must be added on the own. But then we're coming back to question why people need to modify things inside and for to run extensions on their own. I think this was my intention behind these questions.

I am excited to see if there are better solutions in the future as the old google if there much better translations plugins exist inside browsers, that possible could be adapted in future time. I may play a bit with the code to see if a custom flag could be added, but how to change this text from the base language setup inside ACP menu.

[Mick]

No I was talking about 3.3.0 RC3 and 3.3.1 RC1 as I wrote.

Sorry,I wasn’t clear, you said:

Use 3.30 RC3 Version and use the style files from 3.31 RC1

What I meant was versions 3.30 and 3.31 don’t exist, they are 3.3.0 and 3.3.1.

[HiFiKabin]

And for the good translations we can still use the SIMPLE TRANSLATE Plugin with even better doing as Google ever can do.

What simple translate plug in? I can not find anything of this name in the CDB

But then we're coming back to question why people need to modify things

There is no NEED for the BBCode to be added, no more than the need for a spoiler or strike through code. It is an option should the boards admin require it

I am glad that you are happy with the solution you have come up with that suits your purpose. That is the beauty of Open Source. Anyone can make any changes they wish, and release it for others if they so wish.

[SeewolfPK]

How can I prevent the username from being translated?