TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Îñţérñåţîöñåļîžåţîöñ

141 点作者 pwim超过 13 年前

11 条评论

tjoff超过 13 年前
An extremely important point that most native english speakers just doesn't seem to get: Don't force a localized version to your users.<p>In many countries your users are probably going to prefer english than a translated version for many reasons, and that's even before taking into account that you probably can't translate it well anyway (even with a lot of resources and effort) which makes it even worse.<p>Always make it ridiculously easy to switch to english, always. In many cases you probably should make english the default even though you have a localized version (this is especially true for web sites, few things are as annoying as having to change language again and again and again and on every device, browser etc. (example: youtube has this annoying message telling me that a localized version is available that forces a page reload to dismiss (and thus you have to reload and restart the video, true story))).<p>This of course depends heavily on your target audience and their culture but just don't assume a translated page/app is a favor, you just might end up with some confusion and a group of really outraged users (boy do I loathe applications that assume I want a translated version - always give me the option to change it to english during the installation).<p>Direct machine translations might be better than nothing for some cultures but for some it's a slap to the face and will just make your company look pathetic. Example: Adobe.
评论 #2982164 未加载
评论 #2982406 未加载
评论 #2982689 未加载
hopeless超过 13 年前
We're currently going through our internationalisation test phase for a major release and it's been a <i>huge</i> headache.<p>My one piece of generalised advice: DO NOT leave internationalisation testing to the end of the release. Make sure you're pumping Unicode strings through your app in unit tests. Make sure you're regularly viewing your app in other languages using mock strings if you haven't got the translations. The earlier you can find these defects, the easier it is to fix. There's a perception that internationalisation defects are easy fixes, just updating a messages file. The truth is that major parts of your app may not work unless you regularly test it. And don't rely on the Unicode abilities of your chosen framework, language or operating system. If you haven't tested it, it doesn't work
评论 #2983916 未加载
_delirium超过 13 年前
&#62; We can’t recommend this enough: reuse the same template for all language versions<p>This can get quite tricky, because languages don't easily map onto 1-to-1 items that can be just translated independently and stuck into a template. See the classic "localization horror story": <a href="http://interglacial.com/tpj/13/" rel="nofollow">http://interglacial.com/tpj/13/</a> (and HN discussion: <a href="http://news.ycombinator.com/item?id=2095334" rel="nofollow">http://news.ycombinator.com/item?id=2095334</a>)
评论 #2981973 未加载
jontsai超过 13 年前
Oh yes, this is tremendously fun! I worked on i18n/g11n/l10n for Y! World Cup and other games<p>Compare: <a href="http://us.wc.fantasysports.yahoo.com/" rel="nofollow">http://us.wc.fantasysports.yahoo.com/</a> <a href="http://hk.wc.fantasysports.yahoo.com/" rel="nofollow">http://hk.wc.fantasysports.yahoo.com/</a> <a href="http://tw.wc.fantasysports.yahoo.com/" rel="nofollow">http://tw.wc.fantasysports.yahoo.com/</a><p>It's a tremendous amount of work, and you have to identify translatable phrases AND contexts, not just strings and words. Websites that plan on catering to multiple languages and regions should incorporate i18n from the beginning, not an afterthought, which would require going through lots of code with a fine-toothed comb =)
peng超过 13 年前
If i18n is a priority on your project, make sure you show your designer(s) this article. With the current trending emphasis on grids and horizontal rhythm, left-aligned labels are quite fashionable.<p>An effective bandaid solution is to set left-align labels to text-align: right; thereby visually linking the variable width label to the field.
st3fan超过 13 年前
Good to see that Hacker News deals correctly with those beautiful glyphs :-)
评论 #2982516 未加载
评论 #2982130 未加载
pud超过 13 年前
Good article. Now can anyone recommend a service for replacing the copy in a site with copy in different languages, so I can use my same templates?<p>Like Google Website Optimizer, but replaces strings with the appropriate language.. ?
itsadok超过 13 年前
I'd be interested in knowing what made them write that IntelliJ IDEA provides "decent solutions for bidirectional editing", considering that JetBrains' Dmitry Jemerov has specifically said that they don't see the business case in supporting RTL editing:<p><a href="http://youtrack.jetbrains.net/issue/IDEABKL-5572" rel="nofollow">http://youtrack.jetbrains.net/issue/IDEABKL-5572</a>
onetime123超过 13 年前
I just want to point out that the title uses a letter which doesn't exist in any language: t with a cedilla. It's a Unicode fuck up which plagues the romanian language to this day. Not just on computer systems, in real life too!
DiabloD3超过 13 年前
Nothing like early morning Unicode abuse. ;)
Mafana0超过 13 年前
I'm a web developer with experience of technical editing, a native speaker of Arabic, have translated many popular Firefox extensions to Arabic, and worked in "Google in your language" project, since I speak English and German fluently. I'm willing to help any HN member who wants to localize his startup/website to a RTL language, for free. If you contact me, I will gladly review the Arabic localization and RTL design and help you with the globalization in general in my spare time. As a thank you for the community I'm a big fan of.