本地化静态网站的正确方法是什么
我需要将我们的网站本地化为多种语言。 该网站由多个静态页面组成，没有动态后端。 我们有一个良好的国际社会，人们愿意帮助我们。
问题是如何安排网站翻译，正确的工作流程是什么？
静态网站本地化的最佳实践是什么？ 如何组织语言字符串包？ 如何组织从字符串捆绑到生产网页的工作流程？
是否可以以 wiki 的方式安排翻译，让多个翻译者可以同时翻译一个字符串包？
I need to localize our site to a number of languages.
The site consists of several static pages, no dynamic backend.
We have a nice international community and the people are ready to help us.
The problem is how to arrange website translation, what is the right workflow?
What are the best practices for static website localization?
How to organize language strings bundles?
How to organize a workflow from string bundle to production web-page?
Is it possible to arrange translation in a wiki way, where several translators could translate a string bundle concurrently?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
更新：
截至 2012 年 3 月，99translations 已停止使用。我发现的另一个类似的服务是 www.getlocalization.com/
原始消息 ：
您可以使用类似 99translations.com 的内容。在那里打开一个项目并请求您的社区帮助翻译。例如， smartgwt 的人就是这样做的
UPDATE:
As of March 2012, 99translations has been discontinued. Another similar service I've found is www.getlocalization.com/
ORIGINAL MESSAGE:
You could use something like 99translations.com. Open a project there and ask your community to help with translation. For example this is how the guys at smartgwt did it
我认为这个问题有两个不同的部分。
技术：由于它是一个纯静态站点，没有动态内容，因此翻译也将在静态页面中提供。如果您正在运行 Apache，mod_mime 模块可让您向文件名添加语言后缀，这样您可能会拥有 mypage.html.en、mypage.html.fr 等 - cf: http://httpd.apache.org/docs/2.2/mod/mod_mime.html。其他网络服务器可能提供类似的选项。
组织：网站翻译的工作流程是完全不同的事情； Wiki 或 CMS 在这里可能会有所帮助，但它们至少很难用纯静态页面来实现。语言字符串包、资源文件等是否有任何帮助，取决于您的内容，并且在大多数情况下需要动态创建页面。您可以支持和维护哪种工作流程，很大程度上取决于您（您的组织）的处理能力。
我认为，这个问题值得更彻底的分析，才能得到满意的解决方案。
I think this question has two distinct parts.
Technical: as it is a pure static site with no dynamic content, the translations will be provided in static pages as well. If you're running Apache, the mod_mime module lets you add language suffixes to file names, so that you might have mypage.html.en, mypage.html.fr, etc. - cf: http://httpd.apache.org/docs/2.2/mod/mod_mime.html. Other web servers might offer similar options.
Organisational: the workflow for website translation is a totally different matter; a Wiki or CMS might be helpful here, but they are at least difficult to realise with pure static pages. If language string bundles, resource files and the like are of any help, depends on your content, and in most cases will require to create pages dynamically. Which workflow you can support and maintain, largely depends on your (your organisations) capacity to handle it.
In my opinion, this problem deserves a more thorough analysis to get a satisfactory solution.
我刚刚看到一个基于 JavaScript/CSS 的小项目，可以满足您静态国际化的需求： stati18n (https:// /github.com/k-yak/stati18n）尝试一下。
自述文件中解释了所有内容。
I just saw a little project based on JavaScript/CSS that can fit your needs of static internationalization : stati18n (https://github.com/k-yak/stati18n) give it a try.
Everything is explained in the readme file.
简而言之：
是否可以以 wiki 方式安排翻译？ 当然，有很多开源CMS（内容系统管理）可以为您完成这项工作！
静态网站本地化的最佳实践是什么？ 静态网站没有最佳实践！既然您有一个社区，您就必须使用动态内容，根据您的需要，静态网站本身就是不好的做法！
正确的工作流程是什么？ 将您的视图与逻辑分开，不要使用机器翻译，不要连接字符串......等等
希望这有帮助！
in short:
Is it possible to arrange translation in a wiki way? of course, there are a lot of open source CMS ( Content System Management ) that do this work for you!
What are the best practices for static website localization? there is no best practicse for static website! since you have a community you must work with dinamic content, for your needs static site is bad practicse itself!
what is the right workflow? Separate your views from your logic, Don’t use machine translation, Don’t concatenate strings...etc
Hope this help!