Translate Pushbuttons in AFP

[Former Member]

Hi guys,

When using the portal in spanish, the full screen & view options pushbuttons labels are not showing up in Spanish; the pushbuttons IDs are shown instead.

Click here to see a screenshot

¿How can I translate these objects to include the Spanish Label?

Thanks

Ivan

[Former Member · Accepted solution]

Hello Ivan,

this is strange as the Spanish translation should be there if you use standard portal components.

But if you want to find the translations for framework elements:

- open PAR file such as com.sap.portal.navigation.afp.pagetoolbar (With or without NWDS as ZIP file)

- go to PORTAL-INF > private > classes > here you can find the property files which contain the translations for all

- Find the appropriate file and add the translation, please keep in mind that if standard par then the change will be overridden in case of installing a patch

- For example: AFPPageToolbar_nls_es.properties contains

...

FULL_SCREEN_LABEL=Pantalla completa

...

OPTIONS_LABEL=Opciones

...

Hope this helps.

Best regards, Alex

[Former Member · Accepted solution]

Thanks Alexander. I was able to find the properties file AFPPageToolbar_nls_es.properties and the translations to spanish are in place, not sure why they are not loading. Might it be that the script that loads the translations has something wrong?

A consultant with whom I worked some time ago esolved this issue and told me to remove the special characters from AFPPageToolbar_nl file, however, I was not able to locate this file.

I'll do another search. In the meantime can you set your portal user to spanish to see if the translations are being loaded for you? May be it is something related to a SP level, we are on Portal 7.01 SP7

[Former Member · Accepted solution]

Hello,

do you use a custom portal component or a standard one. If standard then it should work. I can not access 7.01 right now but 7.02 works fine.

You could also track the translation values by debugging on the client and server side.

Client side: com.sap.portal.navigation.afp.pagetoolbar > toolbar.js > AFPPageToolbar.getConfigData check which value is passed from server. if wrong then go to server side debugging this check the controller and the data from the resource bundle.

Best regards,

Alex

[Former Member · Accepted solution]

Hi Alexander, not sure how to do client side debugging but I found this values passed from the server when checking the source page

,"AFPPageToolbar":{"FULL_SCREEN_DESCRIPTION":"Haga clic aquí para modo de pantalla completa","DETAILS_LABEL":"Detalles","NORMAL_MODE_LABEL":"Cerrar pantalla completa","HELP_LABEL":"Ayuda","REFRESH_LABEL":"Actualizar","PERSONALIZE_LABEL":"Personalizar","FULL_SCREEN_LABEL":"Pantalla completa","NEW_WINDOW_LABEL":"Abrir en una ventana nueva","NORMAL_MODE_DESCRIPTION":"Haga clic aquí para cerrar el modo de pantalla completa","OPTIONS_LABEL":"Opciones","FAVORITES_LABEL":"Añadir a Favoritos de browser","PORTAL_FAVORITES_LABEL":"Añadir a Favoritos de portal","PRINT_LABEL":"Imprimir","OPTIONS_DESCRIPTION":"Haga clic aquí para abrir el menú \u0022Opciones de página\u0022"}}','','/irj/servlet/prt/portal/prtroot/com.sap.portal.navigation.masthead.BackTargetComponent','');

I was told the problem are with the spanish special characters, thus i went into the server and updated the file AFPPageToolbar_nls_es.properties to remove those characters. After that the portal instance was restarted but i don't see that it is picking up the changes.

[Former Member · Accepted solution]

Hi Ivan,

I think SAP standard should work. Usually IDs are returned if no entry is available. Dont think special characters cause this behavior.

I would use a javascript debugger such as firebug/Ie8 debugger and track the way back from assigning the localized label to the button (JS file mentioned above) until the place where the properties files are read in the backend and send to the client. Then you canfind for sure the reason why the IDs are there.

Changes on the properties files do not need a restart to take effect. Please make sure you do not use some other portal component.

Hope this helps,

Alex