Openbravo Issue Tracking System - Openbravo ERP |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0014831 | Openbravo ERP | 09. Financial management | public | 2010-10-08 10:43 | 2010-10-19 13:25 |
|
Reporter | networkb | |
Assigned To | vmromanos | |
Priority | high | Severity | minor | Reproducibility | always |
Status | closed | Resolution | unable to reproduce | |
Platform | | OS | 5 | OS Version | |
Product Version | 2.40MP12 | |
Target Version | 2.40MP13 | Fixed in Version | | |
Merge Request Status | |
Review Assigned To | |
OBNetwork customer | |
Web browser | |
Modules | Core |
Support ticket | |
Regression level | |
Regression date | |
Regression introduced in release | |
Regression introduced by commit | |
Triggers an Emergency Pack | No |
|
Summary | 0014831: Incorrect literal in general ledger report header |
Description | In the general ledger report [1] when using the application in spanish the literal in the header is always "cliente" (client) even if it is a provider.
[1]Financial Management || Accounting || Analysis Tools || General Ledger Journal || General Ledger Journal |
Steps To Reproduce | |
Proposed Solution | Change the transtaltion from "cliente" to "tercero" to avoid confusions |
Additional Information | |
Tags | No tags attached. |
Relationships | duplicate of | backport | 0010567 | 2.40MP11 | closed | vinothbabu | Label "Customer" in GeneralLedgerReport is showed where BP is customer but also with vendors/creditors |
|
Attached Files | generalledger.png (8,830) 2010-10-08 10:43 https://issues.openbravo.com/file_download.php?file_id=3196&type=bug
|
|
Issue History |
Date Modified | Username | Field | Change |
2010-10-08 10:43 | networkb | New Issue | |
2010-10-08 10:43 | networkb | Assigned To | => dalsasua |
2010-10-08 10:43 | networkb | File Added: generalledger.png | |
2010-10-19 07:54 | vmromanos | Assigned To | dalsasua => vmromanos |
2010-10-19 07:55 | vmromanos | Status | new => scheduled |
2010-10-19 07:55 | vmromanos | fix_in_branch | => pi |
2010-10-19 09:18 | vmromanos | Type | defect => backport |
2010-10-19 09:18 | vmromanos | fix_in_branch | pi => |
2010-10-19 10:09 | vmromanos | Relationship added | duplicate of 0010567 |
2010-10-19 10:09 | vmromanos | Status | scheduled => closed |
2010-10-19 10:09 | vmromanos | Resolution | open => duplicate |
2010-10-19 10:20 | gmauleon | Note Added: 0031954 | |
2010-10-19 10:20 | gmauleon | Status | closed => new |
2010-10-19 10:20 | gmauleon | Resolution | duplicate => open |
2010-10-19 11:08 | vmromanos | Note Added: 0031957 | |
2010-10-19 11:08 | vmromanos | Status | new => closed |
2010-10-19 11:08 | vmromanos | Resolution | open => no change required |
2010-10-19 11:39 | gmauleon | Note Added: 0031960 | |
2010-10-19 11:39 | gmauleon | Status | closed => new |
2010-10-19 11:39 | gmauleon | Resolution | no change required => open |
2010-10-19 13:25 | vmromanos | Note Added: 0031970 | |
2010-10-19 13:25 | vmromanos | Status | new => closed |
2010-10-19 13:25 | vmromanos | Resolution | open => unable to reproduce |
Notes |
|
|
Hi
Please note that the issue is exactly the same as you commented [1] but as written in the proposed solutions this is talking about the translation
"Change the transtaltion from "cliente" to "tercero" to avoid confusions"
[1] https://issues.openbravo.com/view.php?id=10567 [^]
Regards |
|
|
|
Hi Gorka,
In my system it currently shows "Tercero", so there is no need to change it. Do you have the last version of the Spanish translation?
Regards. |
|
|
|
Hi Victor
I've tried again in the 2.40 MP12 version of the client that its working in spanish and the translation in this field shows "Cliente" as you can see in the attached image. Can you please verify that you are checking the 2.40 MP12 version please
Regards |
|
|
|
Hi,
I'm checking it in the latest code available for 2.40 (next 2.40MP12.17) with the latest es_ES translation available for 2.40 and it shows "Tercero".
Please update both, your system and the translation to the latest available. In this circumstances, if the bug is still reproducible, then reopen the bug again. |
|