This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
in new ruby help jar is nbruby.jhp - it says not to edit it; but does it need change of encoding tag for localized help ? the .jhm or map.xml files in other javahelp are not changed except to have encoding tag be that that wil be applicable to the other locales being localized - and for ja and zh that have some unix sub locales with different encoding in each - there is one encoding that has been found for each that will work for all of these sub locales - should that encoding be used in this jhp file ? if so, please make sure to add this to ruby special l10n.list - new for nb6 is global l10n.list managed by BE with common localizable file types and locations, but developers need to add other files/locations or exclude certain files themselves - BE has docs about that.
This bug has been resolved through email. Here's the thread: Paul Fussell wrote: 1. nbruby.jhp is a file used only by the Helen help authoring tool. It doesn't get used at all the JavaHelp helpset and should not be output to the help jar file in the builds. It also should not get translated, and character encoding isn't necessary. Ken Frank answered: ok, its good to know; since ruby is new I didn't want to assume that there might not be something different needed thats why asked about it. Paul Fussell wrote: 2. The topic files (.html) are encoded as follows: <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> Is this encoding okay? Ken Frank answered: I think it can be same as in past but probably not matter - for ja and zh, since there are several sub locales of each - they use a differnt enc tag that works for all 3 of those locales - its not utf-8. and commu l10n should know that they might need to change it. Paul Fussell wrote: 3. The toc, index, and map files are xml files that have the following encoding (same as our NetBeans visual web help files, BTW): encoding='ISO-8859-1' Are you requesting that the encoding of these files be changed? If so, to what? Ken Frank answered: no, these can stay the same - l10n will change it also as needed; the issue was just about that jhp file. Paul Fussell wrote: 4. I have no idea what you're talking about here: "...if so, please make sure to add this to ruby special l10n.list - new for nb6 is global l10n.list managed by BE with common localizable file types and locations, but developers need to add other files/locations or exclude certain files themselves - BE has docs about that." Ken Frank answered: RE has changed l10n.list process so that dev might not need to do l10n.list at all except for special cases - I think RE needs to distribute some docs about this to dev teams.