<p>If one wants to write software intended to be translated and run literally everywhere in whatever languages the user wants what are the current best practices?</p>
<hr/>**评论:**<br/><br/>drvd: <pre><p>The stuff in golang.org/x/text and especially golang.org/x/text/message</p>
<p>Be prepare for <strong>real</strong> <strong>hard</strong> work if you want to achieve your goal of "run literally everywhere in whatever languages". I'm sure you know there are languages with a very reduced concept of time or cardinality.</p></pre>shaleh: <pre><p>Agreed. I am just trying to wrap my head around what is available. Go is surprising less "Batteries Included" than expected given its popularity. I find plenty of 2 and 3 year old blog posts and semi abandoned code on GitHub. So it is never clear where the consensus lies.</p></pre>Jelterminator: <pre><p>The things in the golang.org/x/name are usually where some consensus is.</p></pre>lobocv: <pre><p>Not specifically written for Go but I have a work flow tool for internationalizing python applications. Im not very experienced with Go but in the odd chance it can be helpful to you please have a look. Hopefully it can be easily adapted to extract tags from Go source code. I wouldn't mind helping you adapt it if you can point out the areas that need work.</p>
<p><a href="http://www.github.com/lobocv/translation_factory" rel="nofollow">www.github.com/lobocv/translation_factory</a></p></pre>
Which package(s) currently provide best practices for i18n (and l10n) of Go software?
blov · · 446 次点击这是一个分享于 的资源,其中的信息可能已经有所发展或是发生改变。
入群交流(和以上内容无关):加入Go大咖交流群,或添加微信:liuxiaoyan-s 备注:入群;或加QQ群:692541889
- 请尽量让自己的回复能够对别人有帮助
- 支持 Markdown 格式, **粗体**、~~删除线~~、
`单行代码`
- 支持 @ 本站用户;支持表情(输入 : 提示),见 Emoji cheat sheet
- 图片支持拖拽、截图粘贴等方式上传