I've ran into a bug where every strings from the CEP seems to be encoded in macroman.
You can easily reproduce it by initializing a skeleton project with a single hello world function that print a string with a special character.
Ex :
In src/jsx/ppro/ppro.ts
This is not a display bug, as if I retrieve the name of let's say a projectItem that contains a special character and print it, it will be displayed correctly. It really is the content of the string (this is troublesome because I can't match it against other strings from ppro).
This bug was not present in bolt-cep in July 2023
I'm am on MacOs with an M3 chip.
Bug noted on premiere pro 24.6.3
EDIT :
Here what i meant by "matching against other strings from ppro" :
On the first line I'm logging the same string as before, written by me.
On the second line I'm directly logging the name of the projectItem.
EDIT2:
Seems like I can fix the problem by explicitly specifying the unicode that I want, like so :
Hello,
I've ran into a bug where every strings from the CEP seems to be encoded in macroman. You can easily reproduce it by initializing a skeleton project with a single hello world function that print a string with a special character. Ex : In src/jsx/ppro/ppro.ts
In src/js/main/main.tsx
A call to the function result in
This is not a display bug, as if I retrieve the name of let's say a projectItem that contains a special character and print it, it will be displayed correctly. It really is the content of the string (this is troublesome because I can't match it against other strings from ppro). This bug was not present in bolt-cep in July 2023
I'm am on MacOs with an M3 chip. Bug noted on premiere pro 24.6.3
EDIT :
Here what i meant by "matching against other strings from ppro" :
On the first line I'm logging the same string as before, written by me. On the second line I'm directly logging the name of the projectItem.
EDIT2:
Seems like I can fix the problem by explicitly specifying the unicode that I want, like so :