Issues

Select view

Select search mode

 

Something went wrong on our end

If this keeps happening, share this information with your admin, who should contact support.

Hash IB2EDC Trace dad9c05ecab345969166a22b3c271039

Description

None

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Details

Assignee

Jason Skomorowski

Reporter

Jason Skomorowski

Priority

P4

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Activity

Show:

Jason SkomorowskiOctober 3, 2016 at 9:17 PM

Jason SkomorowskiJune 27, 2016 at 5:18 PM
Edited

Some links from Filip on Slack:

@jason @nielserik A little gold mine of practical tips on multilingual web interfaces and RTL support. BBC’s web team explaining how they tried to solve massive multilingual layouts and fonts http://responsivenews.co.uk/post/123104512468/13-tips-for-making-responsive-web-design - maybe it’s more relevant for the HTML person we might hire, but it will definitely affect a bunch of more technical things relating to templating engines, etc. I guess react will be a good helper when we get to that part. (edited)

(This also seems to contain some good tips in point #3 and #4 http://webdesign.tutsplus.com/articles/tips-for-designing-and-building-a-multilingual-website--cms-24708)

Jason SkomorowskiApril 1, 2016 at 12:07 AM
Edited

From rangle:

  • format.js is definitely the right tool

  • the react-intl components it provides should be used extensively

  • 'ICU message syntax' it supports is known by translation firms eg. they can give translations in that format

  • read the guides first before getting into the react components; the i18n guides

TestRail: Cases
TestRail: Runs

Flag notifications