- Home
- Forum
- React - EJ 2
- Ambiguous localization of "Column" term in PivotView component
Ambiguous localization of "Column" term in PivotView component
Chinese translation of the of the Syncfusion PivotView component, the term "Column" has ambiguous meanings:
In Pivot Table context: "Column" refers to data columns
In Chart context: "Column" refers to Column Chart type
This creates localization conflicts when using L10n.load(). The same resource key "Column" needs different translations based on context.
L10n.load({ 'zh-CN': { 'pivotview': { 'Column': '???', // Should be "列" for table, "柱状图" for chart // Other conflicting terms: // 'Bar': '???', // Table vs Chart // 'Line': '???', // Table vs Chart } } });
Hi DSC,
Thank you for contacting Syncfusion support. We have validated your query and understand the conflict you are encountering when applying localization for “Column”. We have identified this as a bug: “Localization Conflict Between Column Chart Type and Column Axis in Pivot Table.” A fix for this issue is planned for the upcoming Service Pack release scheduled for the first week of February. You can track the status of this issue using the feedback link below:
Disclaimer: “Inclusion of this solution in the weekly release may change due to other factors including but not limited to QA checks and works re prioritization”.
We hope this issue does not significantly impact the component’s core functionality. If you need any further assistance, please don’t hesitate to reach out—we’re happy to help!
Regards,
Karthickraja
Hi DSC,
Thank you for your patience. We are glad to announce that our Essential Studio® 2026 Volume 4 Service Pack Release v32.2.3 is rolled out and the fix for the reported issue: “Localization Conflict Between Column Chart Type and Column Axis in Pivot Table”, has been included in this release. Additionally, we have prepared a sample with the latest version for your reference.
Sample: https://stackblitz.com/edit/udspxwfb-nfemvhm8?file=index.html,index.js
Output:
Root cause:
The issue occurred because the same locale name was used for both the column axis and the column chart type, which caused a conflict when attempting to update the column chart type. This has been resolved by handling the locale for the column chart type separately.
We thank you for your support and appreciate your patience in waiting for this release. Please get in touch with us if you require any further assistance.
Regards,
Karthickraja
- 3 Replies
- 2 Participants
-
DS DSC
- Jan 22, 2026 03:17 AM UTC
- Feb 11, 2026 06:05 AM UTC