Damian Krzeminski wrote: > Alberto wrote: >> Hi, >> I'm actually seeing this issue again in: sipXconfig (3.11.4-012821 >> 2008-06-05T05:55:50 ecs-centos5) >> >> I'm not using any installable language pack just using the Italian >> translation already committed in the mainline. >> >> Parts that are not translated are for example: >> sipXconfig [PRODUCT.DETAILS] in the default english version: sipXconfig >> (3.11.4-012821 2008-06-05T05:55:50 ecs-centos5) >> [BANNER.TITLE] that is null in the default english translation >> >> It's easy to reproduce. Just set you're browser default pages language >> to Italian. >> >> I will fix them in the Italian translation, but the issue is definitely >> still open. >> >> Alberto >> >> >> > > > It might be a different issue. XCF-2297 was about the lack of fallback from > installed packages to default resolution. Since > you do not have any language pack installed this one is probably about the > fact the we do not fall back to default version > during standard locale resolution. > It might be related, but then again might be totally different issues. > Kevin - what do you think. Should we re-opne XCF-2297 or open a new one. > D. >
I was just typing the same response :) The issue described in XCF-2297, and the associated fix, only applied to loadable localization packs. I did not make any changes related to the way that tapestry loads localization files that are part of the source (as is the case here). However, I also can't guarantee that the loadable localization code doesn't somehow break the regular tapestry message resolution (I doubt it, but its possible). We should open a new issue for this. If it is found to be related to XCF-2297, we can always link it in Jira Kevin _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
