9
Today is possible to corrupt Extension when included translation file (Xliff1.2) is not valid. This causes the language to disappear completely.
Please, can you Validate *.xlf files (XML) against schema (XSD) "urn:oasis:names:tc:xliff:document:1.2 http://docs.oasis-open.org/xliff/v1.2/cs02/xliff-core-1.2-transitional.xsd" when compile time?
Also does not exists any switch for "alc.exe" to force Xliff validation. This switch may be sufficient...
Please, can you Validate *.xlf files (XML) against schema (XSD) "urn:oasis:names:tc:xliff:document:1.2 http://docs.oasis-open.org/xliff/v1.2/cs02/xliff-core-1.2-transitional.xsd" when compile time?
Also does not exists any switch for "alc.exe" to force Xliff validation. This switch may be sufficient...
STATUS DETAILS
Needs Votes
Comments
Oh, I see that it can solve it with Rule "AL1026" - Generic XML validation.
Redefine action action from warning to error.
Only issue is when I have in solution some broken XML.
{
"id": "AL1026",
"action": "Error",
"justification": "An error occurred during XML validation."
}
So, this idea seems not necessary...
Category: Development
Business Central Team (administrator)
Thank you for this suggestion! Currently this is not on our roadmap. We are tracking this idea and if it gathers more votes and comments we will consider it in the future. Best regards, Business Central Team