You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@santuario.apache.org by ra...@apache.org on 2005/02/21 22:24:35 UTC
cvs commit: xml-security/src/org/apache/xml/security/resource xmlsecurity_en.properties
raul 2005/02/21 13:24:35
Modified: src/org/apache/xml/security/resource
xmlsecurity_en.properties
Log:
Added base64 message.
PR: 32996
Submitted by: Sean Mullan
Revision Changes Path
1.21 +1 -0 xml-security/src/org/apache/xml/security/resource/xmlsecurity_en.properties
Index: xmlsecurity_en.properties
===================================================================
RCS file: /home/cvs/xml-security/src/org/apache/xml/security/resource/xmlsecurity_en.properties,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- xmlsecurity_en.properties 13 Nov 2004 23:31:24 -0000 1.20
+++ xmlsecurity_en.properties 21 Feb 2005 21:24:34 -0000 1.21
@@ -111,6 +111,7 @@
transform.init.NotInitialized =
transform.init.wrongURI = Initialized with wrong URI. How could this happen? We implement {0} but {1} was used during initialization
utils.Base64.IllegalBitlength = Illegal byte length; Data to be decoded must be a multiple of 4
+Base64Decoding = Error while decoding
utils.resolver.noClass = Could not find a resolver for URI {0} and Base {1}
xml.WrongContent = Cannot find {0} in {1}
xml.WrongElement = Cannot create a {0} from a {1} element