[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [higgins-dev] NLS changes and new MessageProperties files for M4
|
Hi Jim,
I synced the latest code from SVN repository, but I
didn't see any NLS changes in any of the IdAS packages except jndi-cp .
I am wondering if there is any plan to add all NLS changes I uploaded
to defect in bugzilla (https://bugs.eclipse.org/bugs/show_bug.cgi?id=242052
).
As I could see only jndi-cp package
thats having all the NLS changes that are added so far, please see the
attached patch file which I created after updating the content of the messages.
Until and unless I see the NLS changes
for the remaining comonents in SVN , I can not create the patch file for
their message updates.
Thanks and Regards,
Prakash
---------------------------------------------------------------------------------------------------
Advisory Software Engineer,
Tivoli Security Products
ETZ, Plot No. 3 , Rajiv Gandhi Infotech Park
Phase II, Hinjewadi, Pune - 411057
Ph: +91-20-42025544
e-mail: prakash.mallick@xxxxxxxxxx
---------------------------------------------------------------------------------------------------
"Jim Sermersheim"
<jimse@xxxxxxxxxx>
Sent by: higgins-dev-bounces@xxxxxxxxxxx
09/12/2008 03:21 AM
Please respond to
"Higgins \(Trust Framework\) Project developer discussions"
<higgins-dev@xxxxxxxxxxx> |
|
To
| <higgins-dev@xxxxxxxxxxx>
|
cc
| Mukul P Markande/India/IBM@IBMIN
|
Subject
| Re: [higgins-dev] NLS changes and new
MessageProperties files for M4 |
|
so, there are only .properties file in the attachment.
Are you saying that you want the component owners to build appropriate
XYZMessages classes and then go thru their code and track down the strings
found in the .properties files, and convert them to use XYZMessages.SOME_CONSTANT?
Also note that it would be best if these came as a diff.
We don't know what changes might have occurred between the time you
updated, and the time we merge your changes.
To answer your question: all the changes you sent
earlier have been committed to svn. I noted that in this thread:
http://dev.eclipse.org/mhonarc/lists/higgins-dev/msg04990.html
Jim
>>> Prakash C Mallick <prakash.mallick@xxxxxxxxxx> 09/11/08
7:44 AM >>>
Hi Brian and All,
Please see the
new set of message properties files for following components ( based
on M4 base line), that are updated with some review comments from
UA groups here. I have only upgraded the quality of few messages as per
the review feed back , without affecting the structure and meaning of those
messages .
org.eclipse.higgins.idas.common
org.eclipse.higgins.idas.cp.jndi
org.eclipse.higgins.idas.spi
org.eclipse.higgins.util.idas.cp
org.eclipse.higgins.util.jscript
I would expect the component owners to use these properties files and merge
it their respective components. Please let me know if there is any issue
on this.
NOTE : I am not sure whether all the components I globalized are
available in SVN repository or no. Can anybody please tell when those changes
will be available in SVN M4 base line ?
Thanks and Regards,
Prakash
---------------------------------------------------------------------------------------------------
Advisory Software Engineer,
Tivoli Security Products
ETZ, Plot No. 3 , Rajiv Gandhi Infotech Park
Phase II, Hinjewadi, Pune - 411057
Ph: +91-20-42025544
e-mail: prakash.mallick@xxxxxxxxxx
---------------------------------------------------------------------------------------------------
_______________________________________________
higgins-dev mailing list
higgins-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/higgins-dev
Index: C:/supertemp/M4_Latest/org.eclipse.higgins.idas.cp.jndi/.project
===================================================================
--- C:/supertemp/M4_Latest/org.eclipse.higgins.idas.cp.jndi/.project (revision 20653)
+++ C:/supertemp/M4_Latest/org.eclipse.higgins.idas.cp.jndi/.project (working copy)
@@ -6,6 +6,11 @@
</projects>
<buildSpec>
<buildCommand>
+ <name>com.ibm.etools.common.migration.MigrationBuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ <buildCommand>
<name>org.eclipse.wst.common.project.facet.core.builder</name>
<arguments>
</arguments>
Index: C:/supertemp/M4_Latest/org.eclipse.higgins.idas.cp.jndi/src/org/eclipse/higgins/idas/cp/jndi/l10n/JNDICPMessages.properties
===================================================================
--- C:/supertemp/M4_Latest/org.eclipse.higgins.idas.cp.jndi/src/org/eclipse/higgins/idas/cp/jndi/l10n/JNDICPMessages.properties (revision 20653)
+++ C:/supertemp/M4_Latest/org.eclipse.higgins.idas.cp.jndi/src/org/eclipse/higgins/idas/cp/jndi/l10n/JNDICPMessages.properties (working copy)
@@ -6,14 +6,14 @@
NO_JNDI_CONN=No JNDI connection settings specified
NO_UNIQUE_IDENTITY=Non-unique identity from AuthN materials.
-OPEN_WITH_USER=attempt open using simple auth with user: {0} mapped to: {1}
-OPEN_WITH_DIGITALMATERIALS=attempt open using digestmaterials: {0}
-OPEN_WITH_PRIV_USER=attempt open using least privileged user: {0}
-OPEN_WITH_ANONYMOUSMATERIALS=attempt open using anonymous materials
+OPEN_WITH_USER=Attempt to open using simple authorization with user: {0} mapped to: {1}
+OPEN_WITH_DIGITALMATERIALS=Attempt to open using digestmaterials: {0} .
+OPEN_WITH_PRIV_USER=Attempt to open using least privileged user: {0}
+OPEN_WITH_ANONYMOUSMATERIALS=Attempt to open using anonymous materials
NO_SASLSAML_CLIENT=SASL SAML Client Provider not specified
UNSUPPORTED_FORMAT_SAML_ASSERT=Unsupported name format specified in SAML assertion
UNSUPPORTED_AUTHN_MATERIALS=Unsupported AuthN materials: {0}
-START_TLS_MSG=Start TLS request successful: Host ({0}), Protocol ({1})
+START_TLS_MSG=The request to start TLS is successful: Host ({0}), Protocol ({1}).
OPENED_CNTXT_INFO=Context opened: {0} as: {1}
NO_ENTITY_ID=AuthN materials produced no Entity ID: {0}
NO_JNDI_SERVICE_CONFIGURED=No JNDI service addresses configured.
@@ -24,12 +24,12 @@
SEARCH_ENTITY_EID="Searching for Entity: {0} as: {1} in context: {2}
NO_UNIQUE_EID=Non-unique Entity ID
CMPRTR_NOT_SUPPORTED=omparator ( {0} ) not supported.
-NOT_SUPPORTED_COMPLEX_VALUES=Complex assertion values in filters not supported.
-NOT_SUPPORTED_OPERATOR=Operator ({0}) not supported.
+NOT_SUPPORTED_COMPLEX_VALUES=Complex assertion values in filters are not supported.
+NOT_SUPPORTED_OPERATOR=Operator ({0}) is not supported.
FILTER_SEARCH_INFO=Searching for Entities matching filter: {0} as: {1} in context: {2}
STRING_FILTER_INFO=LDAP String Filter: {0}
NO_STRUCURAL_CLASS_FOUND=No structural class found.
-EXPECTED_VALUE_INFO=Only 1 value expected, found: {0}
+EXPECTED_VALUE_INFO=Only one value expected, found: {0}
NO_STRUCURALOBJECT_CLASS_FOUND=No structural class or object class found.
APPLY_UPDATE=Applying updates
CHANGE=change