-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 27.03.2012 21:02, schrieb Fabian Acevedo: > > Hi everyone I was wondering how it might be possible to change the > category titles in the Asset Info (Display Category,Notification > Category, Description etc ) thanks¡¡¡ > > > > ------------------------------------------------------------------------------ > > > This SF email is sponsosred by: > Try Windows Azure free for 90 days Click Here > http://p.sf.net/sfu/sfd2d-msazure > > > > _______________________________________________ Please read the > OpenNMS Mailing List FAQ: > http://www.opennms.org/index.php/Mailing_List_FAQ > > opennms-devel mailing list > > To *unsubscribe* or change your subscription options, see the > bottom of this page: > https://lists.sourceforge.net/lists/listinfo/opennms-devel
Hi Fabian, if you want to change any text on the asset info page you have at least two options: _change the default text entries_ in this file "YOUR_OPENNMS_SRC/opennms/opennms-webapp/src/main/java/org/opennms/gwt/web/ui/asset/client/AssetPageConstants.java". That could cause problems during updates, so be careful. _define a separate set of "translations"_ This file is a sample for German "AssetPageConstants_de.properties" it's in the same folder as "AssetPageConstants.java". If you go this way you have to add your own "AssetPageConstants_YourCode.properties" file for the language code your users are running on. The fallback is still the "AssetPageConstants.java". New languages have to be added in this file "YOUR_OPENNMS_SRC/opennms/opennms-webapp/src/main/java/org/opennms/gwt/web/ui/asset/Asset.gwt.xml" with an entry like this "<extend-property name="locale" values="YourCode"/>", a sample entry is already provided for German. In both cases you have to build you OpenNMS from source like described in the wiki at: http://www.opennms.org/wiki/Installation:Source Keep in mind that you are going to change names for entities that may be uses in reports or any other place in OpenNMS. Nothing will be broken by this step, but you may run into inconsistent names. Maybe a reference to the original names in the help text would be helpful. Regards Markus -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPc6tmAAoJEJFt8t3uH6b9bE8IALwYiwWbMz1qUefMeNbYLnei E8uucjLbU3+tPXsrP7F+OVAVYW5N0nHGe9L/i8hbn0G2dCwkEehSkgk0DAN/EB3z w/2fXoWIKgWPWzTTkR6dvJ9NBM1mkra/Zz/+KupaZ5IZIrWol6iM0gsD0ujMV2+u PzzuLp/rduzJsc1PqgRUPebWh/kx2IavbjdorT6WGyzFnrOOb5/xLxCMJD+qGMzD oJbQl53ZGQ9SIMBkU2OLBE+boTPvJV6R1YJ/fJ0esdAw67IrANYKmPL2+q++ZyNN ZA5uKLeuB2fe5D/oU9LjprDehNZhfUtJhSlHbpryfxjivITJKn3QT70lTIeqhJc= =DPco -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ Please read the OpenNMS Mailing List FAQ: http://www.opennms.org/index.php/Mailing_List_FAQ opennms-devel mailing list To *unsubscribe* or change your subscription options, see the bottom of this page: https://lists.sourceforge.net/lists/listinfo/opennms-devel
