Multilanguage possible on textboxes or buttons?

multilingual

(Robert M. Münch) #21

Looking at this again, and I think it’s way to complicated. I still want a way to do alternatives (content, sizes, etc.) in Hype and switch between them with on click: EN verison, DE version and have elements shown / hidden.

Then I want to export EN version (using all EN flagged elements) or DE version etc.

It could be that simple…

(BTW: I can hack JS back and forth, etc. but it’s not the KISS way to do it)


(Mark Hunte) #22

I think thats called Scenes… :sunglasses:


(Robert M. Münch) #23

No, it’s not. To make it more clear:

Below you see the _EN and _DE element names. Depending on what I want, I turn them on or off. I have enabled one EN and one DE so you see the effect.

The thing is, I keep the animation which is in big parts the same between EN and DE only once. With scenes I would have a copy and need to duplicate changes… not very efficient.

What I want is a way that I can switch to all *_EN elements or all *_DE elements. It’s pretty simple…


(Hans-Gerd Claßen) #24

with applescriptsupport you would be able to for instance switch on/off elements with equal nameparts!!!

@hype so this would be a nice usecase … :slight_smile:


Hype Scriptability with (Script Editor) - Applescript/Javascript-for-automation
(Mark Hunte) #25

@robby,

I must admit I am not convinced with your argument and would much prefer an Applescript solution.
( Which if we had I am pretty sure Applescriptors like my self would offer up code)

But a suggestion (simplified ) of how the Hype team may do this is to offer a new type of Group.

These groups would be called Advanced Export Groups.

If you create a Advanced Export Group, a new Advanced Export Group icon appears at the top of the element tree.
Advanced Export Groups will always be at the Top of the element tree.

Elements added to a Advanced Export Group do not show as moved in the element tree. This is because we do not want to change the layer index. But opening an Advanced Export Group will reveal a reference to any elements added to it.

Advanced Export Groups could also have the hidden/display eye next to it.
If set to hide, all referenced elements would be hidden. Overriding the original elements hidden/display.
If set to display then the referenced elements original setting is honoured, which would be either hidden or display

When using Advanced Export, the Advanced Export Groups will be listed with a check box to include or not include.


(Robert M. Münch) #26

The trick with the name part was just done so I can distinguish the different things fast. Overall it’s not the way to go. It’s a messy hack because of missing alternatives. And I don’t like the AS approach… but this is purely emotional based as it smells like a messy hack on top of a messy approach :wink:

@MarkHunte While I can understand your idea, I’m not a fan of grouping or mapping of information to trees. It’s a categorization, and mostly needs to be MECE. Which is often not the case.

I would like to be able to hack in tags on wich I can then filter (inlcude / exclude) prior an action. That would be most flexible.


(Mark Hunte) #27

Not sure what these are ( ok, I know what a kiss is, think I had one once but pretty sure it’s not what you mean) can you elaborate ?

It may be that the tree is the wrong place to display them but in essence the type of group I mention are Tags.


Working with localizations in creatives
(Robert M. Münch) #28

MECE principle: mutually exclusive, collectively exhaustive (see wikipedia)
KISS = Keep it simple stupid :wink:


(Mark Hunte) #29

I think that may apply to the use of acronyms. Or not …:grinning:


(Adrian Millares) #30

What about iOS? How can we make language detection and then show one or another language?


(René) #31
window.gLanguage = (navigator.language).substr(0, 2);

give all the elements classname their corresponding language.
then use a script like this to show or hide these elements:

var i;
var vElements = document.getElementsByClassName(gLanguage);
for (i = 0; i < vElements.length; i++) {vElements[i].style.display = 'block';};

(Mark Hunte) #32

Good idea @rene

Although if you give the language elements two class names for example : lang and en

You could do it like this

window.gLanguage = (navigator.language).substr(0, 2);

var i;
//-- gather all elements with class name 'lang'
var vElements = document.getElementsByClassName('lang');

for (i = 0; i < vElements.length; i++) {
 
//-- filter using second class name which matches the language 
vElements[i].style.display  =  ( vElements[i].classList.contains(window.gLanguage) ? 'inline'  :  'none');;

}

#33

Maybe the “Multilingual” template is helpful…