Expand currency symbol options in PAW shapes and text objects (currently limited to $ only; add €, £, ¥, and others)

Dear team,

Current Limitation: When adding shapes or text objects via "Add shapes and text" in a PAW book (e.g., rectangles, callouts, labels for KPIs/tiles), users can apply formatting to the text content, including currency/number styles under the Appearance or Format tab.

However, the built-in currency symbol selector (or preset) is severely limited: only the US Dollar sign ($) is available as a native/preset option. Common international currency symbols such as:

• € (Euro)

• £ (British Pound)

• ¥ (Japanese Yen)

• CHF (Swiss Franc)

• and others

are not offered in any dropdown, picker, or quick-select list. Users are forced to:

• Manually type the Unicode character (e.g., Alt+0128 for €)

• Or use custom format strings (e.g., "€#,##0") if supported in that context This is tedious, error-prone (especially for non-technical business users), inconsistent across locales, and breaks uniform branding in multi-currency dashboards.

Business Value / Use Cases:

• Global finance/planning teams: Need quick insertion of €, £, ¥ etc. in shape-based KPI tiles, scorecards, or dashboard labels (e.g., "Revenue €1.2M", "Costs £850k").

• Corporate dashboards: Consistent currency display without manual hacks improves professionalism and reduces formatting time.

• International reporting: Supports regional requirements (e.g., Eurozone, UK, Japan) without relying on custom workarounds that may not render consistently in exports (PDF/Excel).

Proposed Enhancement:

• Extend the currency symbol picker/dropdown in shape/text object formatting (Appearance > Text > Format or similar) to include a comprehensive list of standard ISO 4217 currency symbols: €, £, ¥, CHF, AUD, CAD, SEK, etc. (at least the most common ones).

• Make it locale-aware where feasible (e.g., default based on browser/system locale).

• Integrate with presets like "Currency", "Accounting" for shapes/text (similar to views/visualizations).

• Ensure symbols render correctly in consumption mode, exports, and across devices.

• Optionally: Allow admins to define/add custom symbols globally.

Workaround (current): Manual entry of Unicode symbols or custom strings – unreliable for end-users and time-consuming in books with many shapes/labels.

With best regards,
Vitalij