Edit - Software Engineering Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Thanks. For option 1, if I were to store the English title in resource file as well, what would I use as the "key" to pull specific books? Will the resource store the primary key of the book entities as well then? Thanks

overloading
– overloading

2020-06-17 15:50:51 +00:00
Commented Jun 17, 2020 at 15:50
If the ISBN is the key then that would not apply for me. I was using Books as a sample of what I need to do localization on. The data I will be working with is unique and does not have any unique key like ISBN. In that scenario, would you still say to store English in the resource file? Thanks again

overloading
– overloading

2020-06-17 20:05:56 +00:00
Commented Jun 17, 2020 at 20:05
@overloading Because I don't know your domain, that's why I can't suggest you good lookup key. If your lookup key is a surrogate key then yes the English localization should be stored in the resource files as well. If your lookup key is a composite key ({title}_{publication_year}_{main_author}) then you should still store the title as a resource because the lookup key can have constraints, like do not allow the following characters: #, !, - , `, etc.. Do you get my point?

Peter Csala
– Peter Csala

2020-06-18 06:24:41 +00:00
Commented Jun 18, 2020 at 6:24

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »