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.
Summary: | wptg_tbt:t13y:please provide comments for these DNT strings | ||
---|---|---|---|
Product: | xml | Reporter: | Marian Mirilovic <mmirilovic> |
Component: | XSL | Assignee: | Svata Dedic <sdedic> |
Status: | RESOLVED INCOMPLETE | ||
Severity: | normal | CC: | jessicali, masaki |
Priority: | P2 | Keywords: | I18N |
Version: | 7.2 | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Bug Depends on: | |||
Bug Blocks: | 212666 |
Description
Marian Mirilovic
2012-05-18 07:51:54 UTC
belongs to xsl question: I'd like to have the thing translatable, but the string is a suffix of the filename. Using _ in the translated string is widely used - we should probably avoid special chars or spaces in filenames, if possible. I can easily change the key (is there a spec on how the bundle key should be formatted), but I would be rather strict with the translated string. If the string will be used in a part of file name, let's use just ascii characters and mark it as #NOI18N string. Because using localized/multibyte characters in file name would cause unexpected error and it's not good for compatibility. So how about adding just #NOI18N comment? Suppose we make the string NOI18N. Then if a French user uses the XSL tool on 'exemple.xml', she will receive an output file "exemple_output.xml" instead of "exemple_resultat.xml". Surely workable, but IMHO not ideal from translation completness point of view. Re. multibyte characters in filenames - I agree, and it should be noted in the bundle file. No further response, closing as INCOMPLETE, as it is not obvious what should be fixed. The string is translatable and the translated value should start with underscore as one of the few non-alphanumeric chars widely accepted as part of filename. I would strongly discourage hardcoding the separator in the code. |