You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm wondering if there's a particular reason why triples are preferred for the l10n extension in the inline strategy. Why not resort to maps for less duplication and simpler translation JSON - data structure translation (as I suspect the triples would get translated to maps anyway).
I'm wondering if there's a particular reason why triples are preferred for the
l10n
extension in theinline
strategy. Why not resort to maps for less duplication and simpler translation JSON - data structure translation (as I suspect the triples would get translated to maps anyway).So currently there's:
With maps:
Reading this as a human, it looks more convoluted for just one field being localized, but for more it ends up a bit more compact.
The text was updated successfully, but these errors were encountered: