Internationalizing 99designs
99designs.com
Internationalizing 99designs
1–10 of 10 posts
Re: Internationalizing 99designs
#2Great article, I had to do something similar few years back. Good to see some of the ideas we had were the same. Just wait till you have to mirror the site for Arabic etc. That's when it gets fun.
Re: Internationalizing 99designs
#3Great article, I had to do something similar few years back. Good to see some of the ideas we had were the same. Just wait till you have to mirror the site for Arabic etc. That's when it gets fun.
Thanks! Even moving to CJK will be fun, though a right-to-left script sounds like it could break all kinds of layout assumptions.
Re: Internationalizing 99designs
#4Very useful thanks for the break down! Internationalization is more and more relevant.
Re: Internationalizing 99designs
#5youre probably doing it wrong, i can do that in a week with sublime edit. (no offense)
if i had to do this now id go to unheap.com and get that jquery plugin that squishes long text into a div without resizing it, squish-it (? or something), i think itd make it so much easier.
for my next project im planning to use squish it and am ignoring translation sizing in my designs from now on
Re: Internationalizing 99designs
#6Great article, I had to do something similar few years back. Good to see some of the ideas we had were the same. Just wait till you have to mirror the site for Arabic etc. That's when it gets fun.
Thanks! Even moving to CJK will be fun, though a right-to-left script sounds like it could break all kinds of layout assumptions.
It seems you're already over the hurdle of not assuming other languages have the same grammar as English. From my experience (internationalizing a site for English and Japanese with both heavy back and front end rendering) with that groundwork laid, at least Japanese is relatively simple.
A favorite solution for varying lengths of content is html's flex box. Luckily I only had to support WebKit.
Re: Internationalizing 99designs
#7How can a website nowadays need 9 months to add a new language? I mean good article, but seriously. If you have to refactor your whole codebase to add i18n, you did it very wrong in the first place.
Re: Internationalizing 99designs
#8We did something similar due to very old/messy code, but not with a 3rd party service. We just built an Apache OutputFilter that recognizes text (also in alt, title, button value attributes) and replaces it based on a set of more than 200k regexps. Sounds slow, but works fine due to (tmpfs + mmap based) caching after some warmup. The first working prototype took about 4h.
We'll never do it like this again though!
Re: Internationalizing 99designs
#9How can a website nowadays need 9 months to add a new language? I mean good article, but seriously. If you have to refactor your whole codebase to add i18n, you did it very wrong in the first place.
A small product built in one of today's modern frameworks? Sure, that'll be much faster. 5+ years ago when 99designs was kicked off, the landscape looked much different.
Importantly, the founders choices allowed them to iterate quickly and essentially capture global Anglophone market for our product. If that made i18n a little harder, it was no doubt still a good trade-off to make.
Re: Internationalizing 99designs
#10How can a website nowadays need 9 months to add a new language? I mean good article, but seriously. If you have to refactor your whole codebase to add i18n, you did it very wrong in the first place.
What would doing it right be? Interested what techniques you'd suggest for keeping new PHP/Ruby projects i18n-friendly.