Issue 89738 - Errors in the original strings (crashrep)
Summary: Errors in the original strings (crashrep)
Status: CONFIRMED
Alias: None
Product: porting
Classification: Code
Component: code (show other issues)
Version: OOo 3.0 Beta
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-21 15:30 UTC by clytie
Modified: 2019-05-06 17:36 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: 4.1.6
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description clytie 2008-05-21 15:30:28 UTC
While translating the interface, I found these errors. I thought you would want to fix them, as they 
detract from the overall quality of the program.

I am not sure against which module to report each string: I notice clicking on "officecfg" brings me to 
"utilities", so I may be reporting in separate places strings belonging together. However, I have tried 
reporting them altogether, and that isn't OK either. So this is my effort. I hope it is useful.


1. Please don't use angle brackets with placeholders, because they trip the XML error checks: 

crashrep	source\all\crashrep.ulf	0	LngText	%MSG_PARAM_PROCESSID%				0	
en-US	-p <process ID>				2002-02-02 02:02:02

Every time the strings are updated, every translator has to check through this false positive while 
checking the translation. Please find another way to do this.


2. Spaced question mark

crashrep	source\all\crashrep.ulf	0	LngText	%ENTER_DESCRIPTION%				0	en-US	
~How were you using %PRODUCTNAME% when the error occurred ?				2002-02-02 
02:02:02

- occurred ?	
+ occurred?

Question marks are not spaced in English.


Clytie
Vietnamese Free-Software Translation Team
Comment 1 Marcus 2017-05-20 11:33:17 UTC
Reset assigne to the default "issues@openoffice.apache.org".