Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
3

Universal expressions

Explorer ,
Mar 21, 2024 Mar 21, 2024

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.

Idea No status
TOPICS
Expressions , Scripting , UI and UX , Workflow
712
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 3 Correct answers

Explorer , Jan 26, 2024 Jan 26, 2024

you need use "match name", this is absolute name, wont change everythime , more info here : https://ae-scripting.docsforadobe.dev/matchnames/effects/firstparty.html

Translate
Community Beginner , Jan 25, 2024 Jan 25, 2024

I can make it simpler from

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

to

effect("Slider Control")(1)

But others don't do that. 


The name of the effect is not important, it is saved as it is set, but the parameters change the name depending on the language of the program, which causes difficulties. If they didn't change it while saving, the problem wouldn't arise. This can be taken out as the fourth idea to the three I suggested.

Translate
Community Expert , Jan 25, 2024 Jan 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")

 

Translate
7 Comments
Community Beginner ,
Jan 25, 2024 Jan 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.
Translate
Report
Community Expert ,
Jan 25, 2024 Jan 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")

 

Translate
Report
Community Beginner ,
Jan 25, 2024 Jan 25, 2024

I can make it simpler from

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

to

effect("Slider Control")(1)

But others don't do that. 


The name of the effect is not important, it is saved as it is set, but the parameters change the name depending on the language of the program, which causes difficulties. If they didn't change it while saving, the problem wouldn't arise. This can be taken out as the fourth idea to the three I suggested.

Translate
Report
Explorer ,
Jan 26, 2024 Jan 26, 2024

you need use "match name", this is absolute name, wont change everythime , more info here : https://ae-scripting.docsforadobe.dev/matchnames/effects/firstparty.html

Translate
Report
Community Expert ,
Jan 26, 2024 Jan 26, 2024

I'm not sure if I made it clear (apologies if you already understand this), but the match names don't change from language to language, which is the whole point. So "ADBE Slider Control" will always work, even if your script is run in a different language version of AE.

Translate
Report
LEGEND ,
Mar 22, 2024 Mar 22, 2024

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

 

Mylenium

Translate
Report
Explorer ,
Mar 22, 2024 Mar 22, 2024
LATEST

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.

Translate
Report