Error messages for DOMException are expected to be defined in the same order...
Error messages for DOMException are expected to be defined in the same order of the corresponding enum, but we were missing several of them git-svn-id: https://svn.apache.org/repos/asf/xerces/c/trunk@655539 13f79535-47bb-0310-9956-ffa450edef68
Showing
- src/xercesc/NLS/EN_US/XMLErrList_EN_US.Xml 9 additions, 3 deletionssrc/xercesc/NLS/EN_US/XMLErrList_EN_US.Xml
- src/xercesc/util/MsgLoaders/ICU/resources/root.txt 8 additions, 2 deletionssrc/xercesc/util/MsgLoaders/ICU/resources/root.txt
- src/xercesc/util/MsgLoaders/InMemory/XercesMessages_en_US.hpp 19 additions, 5 deletions...xercesc/util/MsgLoaders/InMemory/XercesMessages_en_US.hpp
- src/xercesc/util/MsgLoaders/MsgCatalog/XercesMessages_en_US.Msg 28 additions, 22 deletions...rcesc/util/MsgLoaders/MsgCatalog/XercesMessages_en_US.Msg
- src/xercesc/util/MsgLoaders/Win32/Version.rc 28 additions, 22 deletionssrc/xercesc/util/MsgLoaders/Win32/Version.rc
- src/xercesc/util/XMLDOMMsg.hpp 35 additions, 29 deletionssrc/xercesc/util/XMLDOMMsg.hpp
Loading
Please register or sign in to comment