Timeline for Naming Conventions for Localized Items?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 19, 2014 at 18:34 | comment | added | Miguel | Example: Step 1) 020 News is created in the parent Step 2) As is new, we automatic localize and just put the name between brackets 020 News [News] is created in the child Step 3) Item is send for translation and comes back as 020 Noticias [Noticias] Step 4) We ignore everything from the translation except [Noticias], access the parent and get the name 020 News [Noticias] Step 5) Parent is updated, 020 Breaking News we can rebuild the child and transtale again 020 Breaking News [Ultimas Noticias] | |
| May 19, 2014 at 18:21 | comment | added | Miguel | Even case 2 would work in automatic translation. We should consider just the translation of the words between brackets [] and rename the SG or Folder when comes back from translation getting the English (or main language) name from the parent and adding the translated name (The one that is between []) | |
| May 19, 2014 at 18:18 | history | edited | Miguel | CC BY-SA 3.0 |
edited body
|
| May 19, 2014 at 18:13 | vote | accept | Alvin Reyes | ||
| May 19, 2014 at 18:13 | comment | added | Alvin Reyes | Nice and thank you, Miguel. Case 2 is a great way to keep a familiar structure (and ordering) while keeping both the original and translated languages in context. I see how case 3 would work with managed translation scenarios but does hide the expected, translated value from local editors. I'll remember to keep naming conventions handy as another tool to handle direct/indirect relationships. :-) | |
| May 19, 2014 at 18:03 | history | answered | Miguel | CC BY-SA 3.0 |