I think it's useful to globalize the error codes for the user's language.
One good way to implement this would be by creating .csv metadata files for each specific language. These files could be made available at https://errors.xboxresearch.com/ just like the default ones.
The language-specific files could follow a naming pattern like errormasks.[Language]-[Variant].csv, oserrors.[Language]-[Variant].csv, and postcodes.[Language]-[Variant].csv.
I'm just wondering whether it's necessary to localize all the text columns in those files (such as "Console", "Type", "Code", "Bitmask", "Name", and "Description") or just the "Description" column. For each localized file, we could include only the "Code" and "Description" columns, and retrieve the other columns from the default .csv metadata files.
I think it's useful to globalize the error codes for the user's language.
One good way to implement this would be by creating
.csvmetadata files for each specific language. These files could be made available at https://errors.xboxresearch.com/ just like the default ones.The language-specific files could follow a naming pattern like
errormasks.[Language]-[Variant].csv,oserrors.[Language]-[Variant].csv, andpostcodes.[Language]-[Variant].csv.I'm just wondering whether it's necessary to localize all the text columns in those files (such as "Console", "Type", "Code", "Bitmask", "Name", and "Description") or just the "Description" column. For each localized file, we could include only the "Code" and "Description" columns, and retrieve the other columns from the default
.csvmetadata files.