RickStrahl / Westwind.Globalization

Database driven resource localization for .NET applications
543 stars 135 forks source link

Namespace Support #160

Closed bliles closed 5 years ago

bliles commented 5 years ago

The project appears to assume that all ResourceSets are in the same namespace. What do you think would be involved in supporting namespaces for ResourceSets?

RickStrahl commented 5 years ago

Not sure exactly what you're referring to here.

Output generation and imports are for a single namespace yes. Not sure how we could fix that without making things a lot more complicated by requiring namespaces inside of the resource file itself.

Personally what I do if I have multiple namespaces I have separate projects and separate sets of resources for each.

bliles commented 5 years ago

Yes, I agree with what you're saying. Originally we had separated out a variety of resources into different namespaces, but for the sake of making a UI to make it easy for our translators to translate our app, we moved everything that needs translation into the same namespace and it's fine.