[Wicket-user] localized resource property file - fallback to default?
Right now, if I have a localized property file (e.g. Welcome_de.properties), it seems I must have all resource keys defined in it. I would prefer to have the localizer be smart enough to fallback to the default properties file (e.g. Welcome.properties) if a property is not present in the localized property file. This would make it possible to add properties to the system and not have to translate them all immediately - let it fall back to the default language until someone gets around to translating it. Does Wicket have this easily configurable, or do I need to roll my own resource resolvers or other classes for this purpose? -- View this message in context: http://www.nabble.com/localized-resource-property-file---fallback-to-default--tf3493032.html#a9755878 Sent from the Wicket - User mailing list archive at Nabble.com. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] localized resource property file - fallback to default?
It already does work like that. http://cwiki.apache.org/WICKET/i18n-and-resource-bundles.html Regards, Erik. dukejansen wrote: > Right now, if I have a localized property file (e.g. Welcome_de.properties), > it seems I must have all resource keys defined in it. > > I would prefer to have the localizer be smart enough to fallback to the > default properties file (e.g. Welcome.properties) if a property is not > present in the localized property file. > > This would make it possible to add properties to the system and not have to > translate them all immediately - let it fall back to the default language > until someone gets around to translating it. > > Does Wicket have this easily configurable, or do I need to roll my own > resource resolvers or other classes for this purpose? > -- Erik van Oosten http://day-to-day-stuff.blogspot.com/ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] localized resource property file - fallback to default?
Hi Erik, Wicket does fall back to the default *file* but what about the case where you have one (or more) large properties file(s) for your default language and you want to create a variation in which you want to change just a few words for instance to make them more domain specific? In that case I would like a way to override just those few domain specific terms, ie an additional .properties file for that variation containing only the deviating terms instead of a copy of the original with just a few changes. Is there a wicket way to implement that? Regards, Wilko Erik van Oosten wrote: > > It already does work like that. > http://cwiki.apache.org/WICKET/i18n-and-resource-bundles.html > > Regards, > Erik. > > > dukejansen wrote: >> Right now, if I have a localized property file (e.g. >> Welcome_de.properties), >> it seems I must have all resource keys defined in it. >> >> I would prefer to have the localizer be smart enough to fallback to the >> default properties file (e.g. Welcome.properties) if a property is not >> present in the localized property file. >> >> This would make it possible to add properties to the system and not have >> to >> translate them all immediately - let it fall back to the default language >> until someone gets around to translating it. >> >> Does Wicket have this easily configurable, or do I need to roll my own >> resource resolvers or other classes for this purpose? >> > > -- > Erik van Oosten > http://day-to-day-stuff.blogspot.com/ > > > - > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > ___ > Wicket-user mailing list > Wicket-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wicket-user > > -- View this message in context: http://www.nabble.com/localized-resource-property-file---fallback-to-default--tf3493032.html#a9891947 Sent from the Wicket - User mailing list archive at Nabble.com. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] localized resource property file - fallback to default?
Wicket does not only fall back to the default. It iterates over a long list of property filenames which are created from the component tree, locale, style and variation. Juergen On 4/8/07, Wilko Hische <[EMAIL PROTECTED]> wrote: > > Hi Erik, > > Wicket does fall back to the default *file* but what about the case where > you have one (or more) large properties file(s) for your default language > and you want to create a variation in which you want to change just a few > words for instance to make them more domain specific? > In that case I would like a way to override just those few domain specific > terms, ie an additional .properties file for that variation containing only > the deviating terms instead of a copy of the original with just a few > changes. Is there a wicket way to implement that? > > Regards, > > Wilko > > > > Erik van Oosten wrote: > > > > It already does work like that. > > http://cwiki.apache.org/WICKET/i18n-and-resource-bundles.html > > > > Regards, > > Erik. > > > > > > dukejansen wrote: > >> Right now, if I have a localized property file (e.g. > >> Welcome_de.properties), > >> it seems I must have all resource keys defined in it. > >> > >> I would prefer to have the localizer be smart enough to fallback to the > >> default properties file (e.g. Welcome.properties) if a property is not > >> present in the localized property file. > >> > >> This would make it possible to add properties to the system and not have > >> to > >> translate them all immediately - let it fall back to the default language > >> until someone gets around to translating it. > >> > >> Does Wicket have this easily configurable, or do I need to roll my own > >> resource resolvers or other classes for this purpose? > >> > > > > -- > > Erik van Oosten > > http://day-to-day-stuff.blogspot.com/ > > > > > > - > > Take Surveys. Earn Cash. Influence the Future of IT > > Join SourceForge.net's Techsay panel and you'll get the chance to share > > your > > opinions on IT & business topics through brief surveys-and earn cash > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > ___ > > Wicket-user mailing list > > Wicket-user@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wicket-user > > > > > > -- > View this message in context: > http://www.nabble.com/localized-resource-property-file---fallback-to-default--tf3493032.html#a9891947 > Sent from the Wicket - User mailing list archive at Nabble.com. > > > - > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > ___ > Wicket-user mailing list > Wicket-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wicket-user > - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] localized resource property file - fallback to default?
I do understand this, but that is not really my question. Let's assume all my keys are in an application scoped property file MyApplication.properties, where MyApplication.java extends the WebApplication. Let this file contain a large amount of keys. Now some customer of ours comes along and insists on the use of specific terminology for a few of the keys. I think the Wicket approach would be to create a variant of MyApplication.properties, MyApplication_customer.properties? But then I have to copy *all* keys, not only the few that will have another translation. Because if I don't provide the other keys as well Wicket will follow the tree upwards to WebApplication.properties, and of course will not find them. In other words, defaults are looked for on a higher level, not sideways as well. But maybe there is another way to tackle this case? Because now I would be stuck with maintaining files that are almost identical. Wilko Juergen Donnerstag wrote: > > Wicket does not only fall back to the default. It iterates over a long > list of property filenames which are created from the component tree, > locale, style and variation. > > Juergen > > On 4/8/07, Wilko Hische <[EMAIL PROTECTED]> wrote: >> >> Hi Erik, >> >> Wicket does fall back to the default *file* but what about the case where >> you have one (or more) large properties file(s) for your default language >> and you want to create a variation in which you want to change just a few >> words for instance to make them more domain specific? >> In that case I would like a way to override just those few domain >> specific >> terms, ie an additional .properties file for that variation containing >> only >> the deviating terms instead of a copy of the original with just a few >> changes. Is there a wicket way to implement that? >> >> Regards, >> >> Wilko >> >> >> >> Erik van Oosten wrote: >> > >> > It already does work like that. >> > http://cwiki.apache.org/WICKET/i18n-and-resource-bundles.html >> > >> > Regards, >> > Erik. >> > >> > >> > dukejansen wrote: >> >> Right now, if I have a localized property file (e.g. >> >> Welcome_de.properties), >> >> it seems I must have all resource keys defined in it. >> >> >> >> I would prefer to have the localizer be smart enough to fallback to >> the >> >> default properties file (e.g. Welcome.properties) if a property is not >> >> present in the localized property file. >> >> >> >> This would make it possible to add properties to the system and not >> have >> >> to >> >> translate them all immediately - let it fall back to the default >> language >> >> until someone gets around to translating it. >> >> >> >> Does Wicket have this easily configurable, or do I need to roll my own >> >> resource resolvers or other classes for this purpose? >> >> >> > >> > -- >> > Erik van Oosten >> > http://day-to-day-stuff.blogspot.com/ >> > >> > >> > >> - >> > Take Surveys. Earn Cash. Influence the Future of IT >> > Join SourceForge.net's Techsay panel and you'll get the chance to share >> > your >> > opinions on IT & business topics through brief surveys-and earn cash >> > >> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV >> > ___ >> > Wicket-user mailing list >> > Wicket-user@lists.sourceforge.net >> > https://lists.sourceforge.net/lists/listinfo/wicket-user >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/localized-resource-property-file---fallback-to-default--tf3493032.html#a9891947 >> Sent from the Wicket - User mailing list archive at Nabble.com. >> >> >> - >> Take Surveys. Earn Cash. Influence the Future of IT >> Join SourceForge.net's Techsay panel and you'll get the chance to share >> your >> opinions on IT & business topics through brief surveys-and earn cash >> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV >> ___ >> Wicket-user mailing list >> Wicket-user@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wicket-user >> > > - > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > ___ > Wicket-user mailing list > Wicket-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wicket-user > > -- View this message in context: http://www.nabble.com/localized-resource-property-file---fallback-to-default--tf3493032.html#a9893882 Sent from the Wicket - User mailing list archive at Nabble.com. -
Re: [Wicket-user] localized resource property file - fallback to default?
Please take alook at Localizer and IStringResourceStreamLocator (? hopefully I got it right). Localizer basically iterates of all locators registers with Settings. Hence, you write and add as many new locators as you like. Juergen On 4/8/07, Wilko Hische <[EMAIL PROTECTED]> wrote: > > > I do understand this, but that is not really my question. Let's assume all > my keys are in an application scoped property file MyApplication.properties, > where MyApplication.java extends the WebApplication. Let this file contain a > large amount of keys. Now some customer of ours comes along and insists on > the use of specific terminology for a few of the keys. I think the Wicket > approach would be to create a variant of MyApplication.properties, > MyApplication_customer.properties? But then I have to copy *all* keys, not > only the few that will have another translation. Because if I don't provide > the other keys as well Wicket will follow the tree upwards to > WebApplication.properties, and of course will not find them. In other words, > defaults are looked for on a higher level, not sideways as well. But maybe > there is another way to tackle this case? Because now I would be stuck with > maintaining files that are almost identical. > > Wilko > > > Juergen Donnerstag wrote: > > > > Wicket does not only fall back to the default. It iterates over a long > > list of property filenames which are created from the component tree, > > locale, style and variation. > > > > Juergen > > > > On 4/8/07, Wilko Hische <[EMAIL PROTECTED]> wrote: > >> > >> Hi Erik, > >> > >> Wicket does fall back to the default *file* but what about the case where > >> you have one (or more) large properties file(s) for your default language > >> and you want to create a variation in which you want to change just a few > >> words for instance to make them more domain specific? > >> In that case I would like a way to override just those few domain > >> specific > >> terms, ie an additional .properties file for that variation containing > >> only > >> the deviating terms instead of a copy of the original with just a few > >> changes. Is there a wicket way to implement that? > >> > >> Regards, > >> > >> Wilko > >> > >> > >> > >> Erik van Oosten wrote: > >> > > >> > It already does work like that. > >> > http://cwiki.apache.org/WICKET/i18n-and-resource-bundles.html > >> > > >> > Regards, > >> > Erik. > >> > > >> > > >> > dukejansen wrote: > >> >> Right now, if I have a localized property file (e.g. > >> >> Welcome_de.properties), > >> >> it seems I must have all resource keys defined in it. > >> >> > >> >> I would prefer to have the localizer be smart enough to fallback to > >> the > >> >> default properties file (e.g. Welcome.properties) if a property is not > >> >> present in the localized property file. > >> >> > >> >> This would make it possible to add properties to the system and not > >> have > >> >> to > >> >> translate them all immediately - let it fall back to the default > >> language > >> >> until someone gets around to translating it. > >> >> > >> >> Does Wicket have this easily configurable, or do I need to roll my own > >> >> resource resolvers or other classes for this purpose? > >> >> > >> > > >> > -- > >> > Erik van Oosten > >> > http://day-to-day-stuff.blogspot.com/ > >> > > >> > > >> > > >> - > >> > Take Surveys. Earn Cash. Influence the Future of IT > >> > Join SourceForge.net's Techsay panel and you'll get the chance to share > >> > your > >> > opinions on IT & business topics through brief surveys-and earn cash > >> > > >> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > >> > ___ > >> > Wicket-user mailing list > >> > Wicket-user@lists.sourceforge.net > >> > https://lists.sourceforge.net/lists/listinfo/wicket-user > >> > > >> > > >> > >> -- > >> View this message in context: > >> http://www.nabble.com/localized-resource-property-file---fallback-to-default--tf3493032.html#a9891947 > >> Sent from the Wicket - User mailing list archive at Nabble.com. > >> > >> > >> - > >> Take Surveys. Earn Cash. Influence the Future of IT > >> Join SourceForge.net's Techsay panel and you'll get the chance to share > >> your > >> opinions on IT & business topics through brief surveys-and earn cash > >> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > >> ___ > >> Wicket-user mailing list > >> Wicket-user@lists.sourceforge.net > >> https://lists.sourceforge.net/lists/listinfo/wicket-user > >> > > > > - > > Take Surveys. Earn Cash. Influence the Future of IT > > Join SourceForge.net's Techsay panel and you'll get the chance to share > > your > > opinions on IT & business topics through brief surv
Re: [Wicket-user] localized resource property file - fallback to default?
I see what you mean, and understand this use case may be good for some occasions. There is a big danger however, of Wicket 'silently' failing (depending on your settings not throwing an exception or displaying a place holder with a warning) when it cannot locate messages. It would be too easy to overlook messages that aren't localized. I think Wicket's defaults are good. And like Juergen said, if you feel you need another algorithm, you can implement this yourself by doing an extra bit of work. Shouldn't be too difficult. Eelco On 4/8/07, Wilko Hische <[EMAIL PROTECTED]> wrote: > > > I do understand this, but that is not really my question. Let's assume all > my keys are in an application scoped property file MyApplication.properties, > where MyApplication.java extends the WebApplication. Let this file contain a > large amount of keys. Now some customer of ours comes along and insists on > the use of specific terminology for a few of the keys. I think the Wicket > approach would be to create a variant of MyApplication.properties, > MyApplication_customer.properties? But then I have to copy *all* keys, not > only the few that will have another translation. Because if I don't provide > the other keys as well Wicket will follow the tree upwards to > WebApplication.properties, and of course will not find them. In other words, > defaults are looked for on a higher level, not sideways as well. But maybe > there is another way to tackle this case? Because now I would be stuck with > maintaining files that are almost identical. > > Wilko > > > Juergen Donnerstag wrote: > > > > Wicket does not only fall back to the default. It iterates over a long > > list of property filenames which are created from the component tree, > > locale, style and variation. > > > > Juergen > > > > On 4/8/07, Wilko Hische <[EMAIL PROTECTED]> wrote: > >> > >> Hi Erik, > >> > >> Wicket does fall back to the default *file* but what about the case where > >> you have one (or more) large properties file(s) for your default language > >> and you want to create a variation in which you want to change just a few > >> words for instance to make them more domain specific? > >> In that case I would like a way to override just those few domain > >> specific > >> terms, ie an additional .properties file for that variation containing > >> only > >> the deviating terms instead of a copy of the original with just a few > >> changes. Is there a wicket way to implement that? > >> > >> Regards, > >> > >> Wilko > >> > >> > >> > >> Erik van Oosten wrote: > >> > > >> > It already does work like that. > >> > http://cwiki.apache.org/WICKET/i18n-and-resource-bundles.html > >> > > >> > Regards, > >> > Erik. > >> > > >> > > >> > dukejansen wrote: > >> >> Right now, if I have a localized property file (e.g. > >> >> Welcome_de.properties), > >> >> it seems I must have all resource keys defined in it. > >> >> > >> >> I would prefer to have the localizer be smart enough to fallback to > >> the > >> >> default properties file (e.g. Welcome.properties) if a property is not > >> >> present in the localized property file. > >> >> > >> >> This would make it possible to add properties to the system and not > >> have > >> >> to > >> >> translate them all immediately - let it fall back to the default > >> language > >> >> until someone gets around to translating it. > >> >> > >> >> Does Wicket have this easily configurable, or do I need to roll my own > >> >> resource resolvers or other classes for this purpose? > >> >> > >> > > >> > -- > >> > Erik van Oosten > >> > http://day-to-day-stuff.blogspot.com/ > >> > > >> > > >> > > >> - > >> > Take Surveys. Earn Cash. Influence the Future of IT > >> > Join SourceForge.net's Techsay panel and you'll get the chance to share > >> > your > >> > opinions on IT & business topics through brief surveys-and earn cash > >> > > >> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > >> > ___ > >> > Wicket-user mailing list > >> > Wicket-user@lists.sourceforge.net > >> > https://lists.sourceforge.net/lists/listinfo/wicket-user > >> > > >> > > >> > >> -- > >> View this message in context: > >> http://www.nabble.com/localized-resource-property-file---fallback-to-default--tf3493032.html#a9891947 > >> Sent from the Wicket - User mailing list archive at Nabble.com. > >> > >> > >> - > >> Take Surveys. Earn Cash. Influence the Future of IT > >> Join SourceForge.net's Techsay panel and you'll get the chance to share > >> your > >> opinions on IT & business topics through brief surveys-and earn cash > >> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > >> ___ > >> Wicket-user mailing list > >> Wicket-user@lists.sourceforge.net > >> https://lists.sourceforge.net/lists
Re: [Wicket-user] localized resource property file - fallback to default?
Thanks Jurgen & Eelco, I understand you would not want this as default behaviour & I suppose I can figure it out. Cheers, Wilko Eelco Hillenius wrote: > > I see what you mean, and understand this use case may be good for some > occasions. There is a big danger however, of Wicket 'silently' failing > (depending on your settings not throwing an exception or displaying a > place holder with a warning) when it cannot locate messages. It would > be too easy to overlook messages that aren't localized. > > I think Wicket's defaults are good. And like Juergen said, if you feel > you need another algorithm, you can implement this yourself by doing > an extra bit of work. Shouldn't be too difficult. > > Eelco > > > On 4/8/07, Wilko Hische <[EMAIL PROTECTED]> wrote: >> >> >> I do understand this, but that is not really my question. Let's assume >> all >> my keys are in an application scoped property file >> MyApplication.properties, >> where MyApplication.java extends the WebApplication. Let this file >> contain a >> large amount of keys. Now some customer of ours comes along and insists >> on >> the use of specific terminology for a few of the keys. I think the Wicket >> approach would be to create a variant of MyApplication.properties, >> MyApplication_customer.properties? But then I have to copy *all* keys, >> not >> only the few that will have another translation. Because if I don't >> provide >> the other keys as well Wicket will follow the tree upwards to >> WebApplication.properties, and of course will not find them. In other >> words, >> defaults are looked for on a higher level, not sideways as well. But >> maybe >> there is another way to tackle this case? Because now I would be stuck >> with >> maintaining files that are almost identical. >> >> Wilko >> >> >> Juergen Donnerstag wrote: >> > >> > Wicket does not only fall back to the default. It iterates over a long >> > list of property filenames which are created from the component tree, >> > locale, style and variation. >> > >> > Juergen >> > >> > On 4/8/07, Wilko Hische <[EMAIL PROTECTED]> wrote: >> >> >> >> Hi Erik, >> >> >> >> Wicket does fall back to the default *file* but what about the case >> where >> >> you have one (or more) large properties file(s) for your default >> language >> >> and you want to create a variation in which you want to change just a >> few >> >> words for instance to make them more domain specific? >> >> In that case I would like a way to override just those few domain >> >> specific >> >> terms, ie an additional .properties file for that variation containing >> >> only >> >> the deviating terms instead of a copy of the original with just a few >> >> changes. Is there a wicket way to implement that? >> >> >> >> Regards, >> >> >> >> Wilko >> >> >> >> >> >> >> >> Erik van Oosten wrote: >> >> > >> >> > It already does work like that. >> >> > http://cwiki.apache.org/WICKET/i18n-and-resource-bundles.html >> >> > >> >> > Regards, >> >> > Erik. >> >> > >> >> > >> >> > dukejansen wrote: >> >> >> Right now, if I have a localized property file (e.g. >> >> >> Welcome_de.properties), >> >> >> it seems I must have all resource keys defined in it. >> >> >> >> >> >> I would prefer to have the localizer be smart enough to fallback to >> >> the >> >> >> default properties file (e.g. Welcome.properties) if a property is >> not >> >> >> present in the localized property file. >> >> >> >> >> >> This would make it possible to add properties to the system and not >> >> have >> >> >> to >> >> >> translate them all immediately - let it fall back to the default >> >> language >> >> >> until someone gets around to translating it. >> >> >> >> >> >> Does Wicket have this easily configurable, or do I need to roll my >> own >> >> >> resource resolvers or other classes for this purpose? >> >> >> >> >> > >> >> > -- >> >> > Erik van Oosten >> >> > http://day-to-day-stuff.blogspot.com/ >> >> > >> >> > >> >> > >> >> >> - >> >> > Take Surveys. Earn Cash. Influence the Future of IT >> >> > Join SourceForge.net's Techsay panel and you'll get the chance to >> share >> >> > your >> >> > opinions on IT & business topics through brief surveys-and earn cash >> >> > >> >> >> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV >> >> > ___ >> >> > Wicket-user mailing list >> >> > Wicket-user@lists.sourceforge.net >> >> > https://lists.sourceforge.net/lists/listinfo/wicket-user >> >> > >> >> > >> >> >> >> -- >> >> View this message in context: >> >> >> http://www.nabble.com/localized-resource-property-file---fallback-to-default--tf3493032.html#a9891947 >> >> Sent from the Wicket - User mailing list archive at Nabble.com. >> >> >> >> >> >> >> - >> >> Take Surveys. Earn Cash. Influence the Future of IT >> >> Join SourceForge.net's Techsay panel and you'
