Localization importer does not accept {1:string} or {named:string} despite LocalizationTable
documentation.
LocalizationTable documentation on the wiki specifies that
Parameters can have format specifiers like {1:int}, {1:fixed}, {2:string}. They will be used for locale aware number, date, and time formatting and will also be used by the auto-translation system to re-format supported types where specified.
Unfortunately, if you try to specify {1:string} or {named:string} the localization system errors out upon import.
The string specifier was in the original spec but it wasn’t implemented apparently. Will remove it from the documentation until we can add it in. Sorry about that.
I’ll write up some more docs on the specifiers that aren’t currently documented as well.
While you’re here, what do you think the string specifier should do with a number? I’d lean towards throw (as int would for a string)
The Source column should have the value with the parameters too. Correct me if wrong but it appears that your second column here is Source, and I only see static strings here without parameters.
Example of what it should be like: (Source should be same as en-us)
It wasn’t; string specifier is just i.e. {1} (not {1:string})
I got it! Turns out what I was doing originally was working, but my strings were too ambiguous and every single possible pattern was being matched to the first, {1:int} {2} pattern. I fixed this by adding periods to all of the strings
