I18n: support more than just english by replacing hard-coded labels.

[jguddas]

Is your feature request related to a problem? Please describe.
If you want to create a website that is not English, you need to overwrite those values by hand.

Example: <CloseButton aria-label="Schließen" />

hope-ui/packages/core/src/close-button/close-button.tsx

Lines 28 to 35 in bdd5a99

	props = mergeThemeProps(
	"CloseButton",
	{
	"aria-label": "Close",
	children: () => <XMarkIcon />,
	},
	props
	);

Describe the solution you'd like
Example: <I18nProvider locale="DE-de" ><CloseButton/></I18nProvider>

 let strings = useLocalizedStringFormatter(intlMessages);
 props = mergeThemeProps( 
   "CloseButton", 
   { 
     "aria-label": strings.format('close'), 
     children: () => <XMarkIcon />, 
   }, 
   props 
 ); 

react-aria example

Describe alternatives you've considered
Ideally, we would add createCloseButton to solid-aria.

 let navProps = useCloseButton();
 props = mergeThemeProps( 
   "CloseButton", 
   { 
     ...navProps,
     children: () => <XMarkIcon />, 
   }, 
   props 
 ); 

Additional context

• solid-aria is currently not used in this project but there are plans to implement it.
• solid-aria has an I18nProvider but currently can't handle messages, something like useLocalizedStringFormatter would need to be added.

[fabien-ml]

Hi, thanks for reporting the issue. After consideration I will not use solid-aria in Hope UI but I can take inspiration from react-aria i18n to achieve the same feature.

[jguddas]

Ahh, okay, why is that I, would think this needlessly increases complexity?

[fabien-ml]

I've built solid-aria and I don't like the DX, also I don't have time to maintains both.