Opened 15 years ago

Closed 15 years ago

Last modified 15 years ago

#1820 closed defect (wontfix)

Widgets fail to show up when localized messages do not exist

Reported by: [email protected] Owned by: Adam Peller
Priority: high Milestone:
Component: Internationalization Version: 0.4
Keywords: Cc: [email protected]
Blocked By: Blocking:


Here's an example: <div dojoType="datepicker" lang="en"></div>

Even if messages for the 'en' locale may not exist, I would expect dojo to use default messages (or even those of a 'near' locale) and still display the widget.

Instead, I get FATAL exception raised: Bundle not found: gregorian in dojo.i18n.calendar , locale=en DEBUG: dojo.widget.Parse: error:Error: Bundle not found: gregorian in dojo.i18n.calendar , locale=en

Change History (7)

comment:1 Changed 15 years ago by Adam Peller

Component: WidgetsInternationalization
Owner: changed from bill to Adam Peller

I need to do a better job documenting this, but it's a requirement that you use locales that either match your browser (installed setting, not preferences) or are explicitly declared using djConfig.locale or djConfig.extraLocale prior to loading dojo.js. I'm assuming that your browser is Greek, is that right? If so, you'll need a djConfig setting to see lang="en". Please let me know if that's not the case.

I'm going to hold on to this bug until I've fixed the documentation. I'm also not sure if this needs to be fatal.

comment:2 Changed 15 years ago by [email protected]

Thanks! added djConfig.locale="en" and it seems to work...

I didn't quite get what you mean by '(installed setting, not preferences)' but as i said, declaring the locale explicitly resolves this.

comment:3 Changed 15 years ago by Adam Peller

severity: majornormal

we go by whatever the browser provides for navigator.language (IE uses navigator.userLanguage, or something like that) This comes with the browser installation and is not settable in the preferences dialog. The languages you see in the preferences dialog are sent to the server in HTTP headers and are unfortunately not available to Dojo/JS.

comment:4 Changed 15 years ago by alex

Cc: [email protected] added

so what's the fix? is there one? should we be marking "wontfix"?

comment:5 Changed 15 years ago by [email protected]

well, if you ask me, i'd go for 'invalid'. Further investigation of the problem i originally reported showed this to be a server-side issue.

comment:6 Changed 15 years ago by Adam Peller

Resolution: wontfix
Status: newclosed

comment:7 Changed 15 years ago by (none)

Milestone: 0.4.1

Milestone 0.4.1 deleted

Note: See TracTickets for help on using tickets.