Are you trying to translate a BI report, or the string in the web interface?
I have to ask first:
- Have you enabled the German locale for Content Server?
- In your user profile, have you selected German?
Assuming both answers are yes...
I wouldn't worry about the XLF/XLIFF file if you are changing the caption in a report - provided the caption can even be translated in the report. URM does some black-magic translation for "certain" select strings in reports. Not sure "Warehouse" is one of them, though.
I'd avoid trying the <@lang_code.string@> route -- sometimes it works, sometimes not. In your custom component, create a folder structure like "resources/lang/de/ww_strings.htm", and put <@wwWarehouse=Archiv@> in that file.
Yes both answers are yes. I am in German context.
It is about the the web interface and not report. In the pages URM shows the out-of-box German translated text as 'Warehouse' based on the xlf file entry. But our customer does not like it and they want 'Archiv' to be shown in German. But in English and other languages they want to the URM default words. Thats the reason i want to override only the German word through the custom component.
In my custom component i have created the folder structure in all languages and only in /de/ww_strings.htm i am putting the entry <@de.wwWarehouse=Archiv@> and it does not work.
No it does not work. I put the entry without the 'de' prefix.
But one thing i observe that other XLF file entry keys which are without @002frm keyword they are very well overridden through the same custom component approach. But this one is not. So i strongly believe that the presence of @002frm keyword in the XLF file entry key is causing the problem. Any idea what is the significance of the word ?
If we are talking strictly about the string in the web UI, like in a "Browse Storage" menu, the XLF file has no significance. The web UI localization doesn't comes from those files. It comes from a htm based string file. (XLF/XLIFF files are just used for the BI report publishing, and not considered for the web UI.)
I'd grep the file system for "wwWarehouse". For a test (and only a test, in a development environment) I'd edit the system files containing that particular German translation string, and see if the problem clears up. If it does, that tells me that you have a load order issue with your component's resource file containing the string, (not the component load order itself.)