To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=42148


User liz changed the following:

                  What    |Old value                 |New value
================================================================================
                    Status|STARTED                   |RESOLVED
--------------------------------------------------------------------------------
                Resolution|                          |WONTFIX
--------------------------------------------------------------------------------




------- Additional comments from [EMAIL PROTECTED] Fri Jul 22 07:59:55 -0700 
2005 -------
After researching this further, my decision is not to "fix". Going forward all
new or changed strings have to be written as  "%PRODUCTNAME Basic", and slowly
but surely the inconsistency will disappear. But, the priority and ROI for
making these changes now do not correspond.
Reasoning:
There are approx 70 UI strings which include "BASIC" or "Basic" or "%PRODUCTNAME
Basic". They are across several modules and would require at least 6 different
developers to implement the string changes in several CWS in both German and
English. 
Most of these strings will not be seen by users and when they are it will be 
seldom.
Putting the full name "%PRODUCTNAME Basic" in some cases would make the error
messages look more important than they are or even like "branded" instances:
thus the advice from YJ in tech pubs not to put the %PRODUCTNAME in to the
typical programmer error messages like "BASIC syntax error".
If we don't put "%PRODUCTNAME Basic" into every string, then we won't achieve
terminological consistency anyway. 
"BASIC" is _not_ the way the StarOffice/OOo Basic dialect is written in any
documentation. In effect any UI strings that use "BASIC" are the bugs, not the
other strings that use "Basic". The logical action would be to change all
strings with "BASIC" to "Basic" but that is the opposite of what Simon wanted
when he opened this issue.

Therefore, my decision to leave this as is. Translators will not benefit from
the fix I would have developers implement anyway. (i.e. it will not be clear
just from the capitalization that it is the normal word vs the programming
language).

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to