Skip to main content
Inspiring
January 25, 2024
Open for Voting

Universal expressions

  • January 25, 2024
  • 3 replies
  • 1016 views

Increated mogrt templates that turned out to be unusable because the UI elements seem to have different names in different languages. So we can't simply share that with countries.

 

This design decision doesn't make a lot of sense. Terms like "slider" are understood in any country and anyone who is able to script shouldn't have the ability to understand those UI terms.

 

It would be great if you could simply universalize these terms so that there are no language barriers.

3 replies

Mikay²Author
Inspiring
March 22, 2024

Thankso much for your advice! This is great news!

Then they should make it the default method of referencing and make the other method obsolete. I don't think anybody knows that this is possible and most ae and mogrt files shared online will not make use of this feature.

Mylenium
Legend
March 22, 2024

You already can by referencing the internal Adobe matchnames and enumerated indices.

 

Mylenium

Participant
January 25, 2024

Make it so that when the program language is changed, expressions containing effects continue to work.

  • This can be done by translating all effects in all languages to English.
  • The second way is to use indexes, now when inserting an effect into an expression it is inserted with the name by default, but it can be done with an index. But then it should change numbers in the expression itself when the index is changed.
  • The third way is to create a special identifier for effects, by which it will change its name as it changes it during renaming, but taking into account the change of the program language.
Dan Ebberts
Community Expert
Community Expert
January 25, 2024

One way to help "language-proof" your expressions is to use the match names for effect parameters. So, for example, instead of:

effect("Slider Control")("Slider")

you would use:

effect("ADBE Slider Control")("ADBE Slider Control-0001")