Community
Participate
Working Groups
chkpii yields: ECLIPSE\PLUGINS\ORG.ECLIPSE.PDE\CHEATSHEETS\ UPDATES.XML XML-WELCOM 969 (W) XML tag attribute (param3) may contain translatable text which cannot be translated. Line: 53 The line is: param3="XYZ Feature" (it looks like line 57 in my editor) I changed the 'param3' tag to 'title', and that (title="XYZ Feature) passes chkpii. It appears that param3 needs to be changed to something approved by chkpii. Is this a change that can be made?
Any status on this? 3.1 is coming up and we have to work around this until a fix is made...
trying another component to get a response This is still causing problems...
Please have this problem fixed as we are unable to send this file for translation for 3.1. We keep on having to delete it out of the PII package.
The chkpii warning is bogus. Cheatsheet files are translated as a whole, instead of providing a matching properties file (similar to HTML or JSP files).
I think there is a misunderstanding here. The cheatsheet.xml can be kept as is. The only variable which needs to be fixed in this xml is param3="XYZ Feature". Please update variable param3 to something different,such as title3="XYZ Feature" for example. This way, translation can be performed for this variable. Else by default this field will be blocked because variable param is used, which indicates the constant is not translatable. We had been handling this translation through the back door for previous release. I would like to see the problem fixed once for all for this release and for future releases.
We cannot make this change. Name of the arguments is API i.e. cannot be changed without breaking our clients.
If I recall correctly, the param3="XYZ Feature" is just an initial value for a field on the cheatsheet that the user will probably change. I don't think it is critical to translate it but we do need the file to be completely CHKPII clean (errors and warnings) in order to get any of the file translated and there is other content in the file that we want translated. I know this is a bit strange, but what if we changed "XYZ Feature" to something CHKPII will not detect as being translatable text in a non-translatable field? I believe the hueristic the CHKPII is using trips up on this one due to the embedded blank. Cam, could you run a quick test to see if changing it to "XYZ-Feature" or "XYZ_Feature" or "FeatureName" would get rid of the warning? Dejan, would one of these values or some other you suggest be an acceptable fix to this issue?
I am curious that CHKPII flags a blank in an attribute as a problem, but has no problem with blanks in element bodies. We can apply various hacks here but at the end of the day we want to use a sentence in the attribute and 'param3' is API for that particular element. I assume CHKPII has a list of attributes for which it expects blanks in attributes (e.g. title, name etc.), so param3 trips it. You are free to change the title to whatever you want just to get CHKPII to pass, but when you translate, try to mentally 'remove' the tweak.
Moving to affected component.
This is the same bug as Bug 102366 which is now FIXED on the cheat sheet side. The cheat sheet content file spec now contains a translation hint and I have been assured that CHKPII will be modified to look for the translation hint. *** This bug has been marked as a duplicate of bug 102366 ***
