Ukendio
(Marcus)
April 18, 2024, 9:43pm
16
Cool but the localizations table and are still fundamentally broken with substring patterns. I was told that people were assigned to this a month ago but are there any updates and ETAs? We are going to be blocked until that is fixed and no matter how nice this feature this is, we won’t be able to use it
AFAIK substrings ({%pattern} string) has never worked since release (including testimonies from other developers). This is incredibly frustrating to work with and borderline makes the translator portal useless because it scrapes hundreds of duplicate strings where otherwise the substring feature should have deduplicated it.
Setting autolocalize to false on the problematic textlabels doesn’t inhibit the strings from being auto-captured (separate bug: Auto-Capture doesn't respect AutoLocalize ). I…
Are the strings you are seeing in your table the "<playername> sent you a trade request!" ones?
Yes
If so, can you show how Description is being created?
It is in the second snippet of my previous message. We clone an instance that we have made imperatively in the PlayerGui.
(note that client-side translator instances can contribute to ATC as well).
I am not sure what ATC is but we have a lot of strings that are getting duplicated, ones that do not use Translator instances at all!
2 Likes