Timeline for DDD Model to handle Localizations
Current License: CC BY-SA 4.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 3, 2024 at 12:59 | vote | accept | Hélder | ||
| Jun 27, 2024 at 6:45 | answer | added | Christophe | timeline score: 2 | |
| Jun 26, 2024 at 17:56 | comment | added | Erik Eidt | I don't know why the Localization needs an Id at all. Are you allowing the same (CultureId, ResourceKey) pair with multiple/different Values? | |
| Jun 26, 2024 at 17:52 | comment | added | gnasher729 | So your “users” are not the usual users who are using an application they are given, but a combination of managers / translators / developers responsible for me (French end user) to see an application in French language, showing the temperature in Celsius and distances in kilometres / metres / centimetres etc. | |
| Jun 26, 2024 at 17:34 | answer | added | Ewan | timeline score: 1 | |
| Jun 26, 2024 at 17:20 | comment | added | Rik D | Translation and localization is probably a context that is completely separated from your main context. I would treat it as such. It’s probably also not a core domain for your business, but a generic subdomain, meaning you should really question if this is worth putting a lot of development effort into, or if you should look into off-the-shelf solutions. | |
| Jun 26, 2024 at 16:03 | comment | added | Hélder | The stakeholders indeed see this as more than just translating forms. The goal is to provide a robust system that allows users to manage translations effectively, ensuring that the application is usable and accessible in multiple languages and cultures. The users in this context are the people responsible for managing the content of the application. In this context they will have the following abilities: - Manage Translations: They can add, update, and delete localizations for different cultures. | |
| Jun 26, 2024 at 15:53 | comment | added | gnasher729 | Who are “the users” and what abilities do they have? | |
| Jun 26, 2024 at 15:52 | comment | added | Hélder | @BartvanIngenSchenau, The users will have the hability to manage the translations. | |
| Jun 26, 2024 at 15:01 | comment | added | Erik Eidt | Also consider the way these are used, referred to, externally. With the former, the path to a localization will have to have the culture id and the localization id, but the localization id doesn't have to be unique across cultures, whereas with the latter, the localization id's must be unique regardless of culture, while the path to a localization won't need a culture id. | |
| Jun 26, 2024 at 14:57 | comment | added | Bart van Ingen Schenau | How do your domain stakeholders view the concept of internationalization, especially if you don't make it a given that the implementation will be done in software (i.e., it might be old-fashioned paper and pen)? Do they consider it as "just translate the forms and you are done" or does it have actual impact on the business? | |
| S Jun 26, 2024 at 13:54 | review | First questions | |||
| Jun 26, 2024 at 14:58 | |||||
| S Jun 26, 2024 at 13:54 | history | asked | Hélder | CC BY-SA 4.0 |