[
https://issues.apache.org/jira/browse/SHINDIG-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648974#action_12648974
]
Chris Chabot commented on SHINDIG-541:
--------------------------------------
Looking @ the patches I see that it's not using the multi_fetch feature that
we've added to the remove content fetchers, specifically for this case :)
Fetching bundles one by one / sequentially is very slow and will make the
initial render way to slow, that's why it's essential we fetch *all* message
bundles simultaneously (using the multi fetch function) and then process them
from there.
Could you possibly update the patch to reflect this? thanks!
> Tiered message bundles
> -----------------------
>
> Key: SHINDIG-541
> URL: https://issues.apache.org/jira/browse/SHINDIG-541
> Project: Shindig
> Issue Type: Bug
> Components: Gadget Rendering Server (PHP)
> Reporter: Chris Chabot
> Priority: Critical
> Attachments: GadgetServer.php.patch, MessageBundleParser.php.patch
>
>
> Currently shindig uses only one localization pack (whichever language pack
> matches the preffered language the closest), and uses only that for message
> tag substitution.
> However the correct behavior should be that if a translation tag (__MSG_foo)
> is not found in the active language set, it should try the the next best
> match (so first en-US, then en-ALL, then ALL-ALL if the previous 2 failed)
> and use that for translation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
