Annemarie Apple
Annemarie Apple
@sffc - Can you include the CLDR modify config file in the PR? We like including them so we have a history of the CLDR modify command that was run...
It looks like it's still failing since you didn't do the following two paths for all locales: //ldml/dates/calendars/calendar[@type="coptic"]/eras/eraAbbr/era[@type="0"] //ldml/dates/calendars/calendar[@type="coptic"]/eras/eraNarrow/era[@type="0"] You'll need to make sure all are removed.
So the CLDRModify change LGTM, but I don't know if there is any impact with re-ordering the calendars by calendar type name in English. I assume it's probably okay, but...
LGTM! So are we just going to file another ticket to clean up the initial batch of problematic links?
So does this just mean that there will be a list of errors after every time someone makes a spec change and it builds? Or is it every time there...
I didn't think we were changing the match to English, I think it should match what was done for Macedonian. I thought the goal was to remove the language match...
Will the same examples show in the Info Panel?
So will this just start failing when data is brought into vXML, or is there a way to get it to fail earlier in the cycle?
Agreed, it seems like it would be nice if the error started showing up in en instead, and then we have en show up in the priority issues tracking?
We should just update priority issue tracking to include errors in en for future releases.