asp.net - Strategies for localizing large amounts of text in .NET applications -
i'm working on large asp application localized. i'm using standard named resx
approach in satellite assemblies, fallbacks (that is, es-mx
, es-cl
, fallback common es
, on).
not there hundreds (if not thousand or more!) of different strings; in places amount of text needs stored resource can long, tune of few paragraphs.
i'm guessing royal pain manage these strings in visual studio editor, not mention fact people of translations won't have access vs in first place.
how folks work on localized apps manage type of thing? advice , pointers appreciated.
if decide go db, check out article: creating data driven asp.net localization resource provider , editor rick strahl , download free
if decide still using resx, can use zeta resource editor mitigate pain.
Comments
Post a Comment