Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0003667Openbravo ERPZ. Otherspublic2008-03-31 14:212008-06-12 09:44
cromero 
cromero 
normalminoralways
closedfixed 
5
 
 
No
Core
No
0003667: Spelling errors in document statii
Releted to bug:

While playing around with completed function I noticed some spelling errors
which might mislead users.

TABLE ad_ref_list changed lines below

"168";"0";"0";"Y";"0099-07-01 00:00:00";"0";"2008-03-28
11:52:55.629343";"100";"NA";"Not Accepted";"";"131";"";"";"D"
"171";"0";"0";"N";"0099-07-01 00:00:00";"0";"2008-03-28
11:54:14.891649";"100";"TR";"Transferred";"";"131";"";"";"D"
"172";"0";"0";"Y";"0099-07-01 00:00:00";"0";"2008-03-28
11:54:26.429237";"100";"VO";"Voided";"";"131";"";"";"D"
"190";"0";"0";"Y";"0099-07-01 00:00:00";"0";"2008-03-28
11:52:07.518594";"100";"??";"Unknown";"";"131";"";"";"D"


The dates are the original dates in the table. As far as I am aware their
value does not matter.

The update is to change the values stored, viz.
"Not Accepted" instead of " Not Acecpted"
"Transferred" instead of "Transfered"
"Voided" instead of " Avoided"
"Unknown" instead of "Unknow"

How you change those values does not really matter. I supplied the 3 rows
of the table so that you could import them replacing the existing rows. If
you want me to supply this kind of information in a different way then
please say so.

However, getting 4 spelling mistakes corrected in the main trunk is
proving to be a marathon. This is the 3rd message I have sent on this
subject.

Kind regards,

Andrew.
No tags attached.
blocks defect 0002771 closed cromero Spelling errors in document statii 
Issue History

Notes
(0007256)
user71   
2005-06-01 00:00   
(edited on: 2008-06-12 09:44)
This bug was originally reported in SourceForge bug tracker and then migrated to Mantis.

You can see the original bug report in:
https://sourceforge.net/support/tracker.php?aid=1930124 [^]
(0004118)
cromero   
2008-03-31 14:23   
(edited on: 2008-06-12 09:27)
Logged In: YES
user_id=1500614
Originator: YES

Fixed in the branch in revision 3145