Solving Localization Challenges with Design Pattern Automation
•
0 likes•716 views
Localization is crucial for reaching out to a global audience, however, it’s often an afterthought for most developers and non-trivial to implement. Traditionally, game developers have outsourced this task due to its time consuming nature. But it doesn’t have to be this way. Yan Cui will show you a simple technique his team used at GameSys which allowed them to localize an entire story-driven, episodic MMORPG (with over 5000 items and 1500 quests) in under an hour of work and 50 lines of code, with the help of PostSharp.
Report
Share
More Related Content
What's hot
Viewers also liked
Similar to Solving Localization Challenges with Design Pattern Automation
Similar to Solving Localization Challenges with Design Pattern Automation (20)
More from PostSharp Technologies
More from PostSharp Technologies (6)
Recently uploaded
Recently uploaded (20)
Solving Localization Challenges with Design Pattern Automation
- 1. Simplify Localization with Design Pattern Automation an AOP success story by Yan Cui @theburningmonk
- 2. Hi, my name is Yan Cui @theburningmonk
- 3. plz ask question in the questions window
- 4. Watch the webinar recording here: http://www.postsharp.net/blog/post/ webinar-recording-localization
- 9. more text than first 3 Harry Porter books COMBINED!
- 13. localization needs to be applied in many, many places!
- 16. traditionally…
- 17. ingest gettext (.po) file
- 19. msgid = original text msgstr = localized text
- 20. ingest gettext (.po) file substitute display text
- 21. Watch the webinar recording here: http://www.postsharp.net/blog/post/ webinar-recording-localization
- 22. button.text = getLocalizedText("back"); label.text = getLocalizedText("baits"); monster.name = getLocalizedText(monster.name); ...
- 23. ingest gettext (.po) file substitute display text render translated text instead
- 26. but wait…
- 27. but wait… what if we add another type of domain object or add/change an screen?
- 28. ingest gettext (.po) file substitute display text render translated text instead
- 29. ingest gettext (.po) file substitute display text render translated text instead
- 31. hard to get good test coverage scope is too big
- 32. easy for regressions to creep in during frequent release cycles
- 33. 6 sins of traditional approach to localization large up-front development effort not future proof duplicated effort for each client platform hard to get good test coverage prone to regressions pressure on QA resources
- 35. THINK OUTSIDE
- 42. yup, we iterate A LOT!
- 43. Watch the webinar recording here: http://www.postsharp.net/blog/post/ webinar-recording-localization
- 48. publisher service our pipeline what if we localize here?
- 49. publisher service our pipeline so what goes here is already localized (where necessary)
- 52. 6 sins of traditional approach to localization large up-front development effort not future proof duplicated effort for each client platform hard to get good test coverage prone to regressions pressure on QA resources
- 53. 6 sins of traditional approach to localization large up-front development effort not future proof duplicated effort for each client platform hard to get good test coverage prone to regressions pressure on QA resources
- 54. ingest gettext (.po) file substitute display text render translated text instead
- 55. server team
- 56. 1. ingest gettext (.po) file 2. check domain objects for string fields/properties 3. use localized text when transforming to DTO 4. repeat for next language
- 57. 1. ingest gettext (.po) file 2. check domain objects for string fields/properties 3. use localized text when transforming to DTO 4. repeat for next language hey Watson! I found a Pattern!
- 58. “thou shall not burn me” - a server dev
- 59. to ingest .po files in .Net
- 60. to automate implementation patterns in .Net
- 66. ps. we had a convention of suffix DTO types with VO
- 67. 6 sins of traditional approach to localization large up-front development effort not future proof duplicated effort for each client platform hard to get good test coverage prone to regressions pressure on QA resources
- 68. Watch the webinar recording here: http://www.postsharp.net/blog/post/ webinar-recording-localization
- 69. 6 sins of traditional approach to localization large up-front development effort not future proof duplicated effort for each client platform hard to get good test coverage prone to regressions pressure on QA resources
- 70. 6 sins of traditional approach to localization large up-front development effort not future proof duplicated effort for each client platform hard to get good test coverage prone to regressions pressure on QA resources
- 71. Q. how do I exclude a DTO from localization?
- 72. Q. how do I exclude a DTO from localization? A. use [Localize(AttributeExclude = true)]
- 73. Q. where did the .po files come from?
- 74. Q. where did the .po files come from? A. TNT publisher service +.PO .PO
- 75. Q. where did the .po files come from? A. TNT publisher service +.PO .PO
- 76. Q. where did TNT get the .po files from?
- 77. A. you publisher service Q. where did TNT get the .po files from? game designer tool for generating new .po file
- 80. A. you publisher service Q. where did TNT get the .po files from? game designer tool for generating new .po file unchanged strings keep msgstr changed strings has empty msgstr
- 81. A. you publisher service Q. where did TNT get the .po files from? game designer tool for uploading .po file
- 82. Watch the webinar recording here: http://www.postsharp.net/blog/post/ webinar-recording-localization