1,068
edits
L10n:Localizability/Web: Difference between revisions
Jump to navigation
Jump to search
m
→Example 1: HTML
| Line 58: | Line 58: | ||
The localizer then submits the translated HTML or PHP back to us by either checking in changes to SVN or sending us a patch that Pascal checks in. | The localizer then submits the translated HTML or PHP back to us by either checking in changes to SVN or sending us a patch that Pascal checks in. | ||
'''Advantage to HTML''' | |||
*# Good for small projects | *# Good for small projects | ||
*# Very simple for web developers | *# Very simple for web developers | ||
| Line 64: | Line 64: | ||
*# A localizer who knows basic HTML can style translations to make sure translations display correctly...we can allow slight modifications (e.g. RTL or wider display) | *# A localizer who knows basic HTML can style translations to make sure translations display correctly...we can allow slight modifications (e.g. RTL or wider display) | ||
*# Simple workflow, just put the file on svn and it can appear on the staging server | *# Simple workflow, just put the file on svn and it can appear on the staging server | ||
'''Disadvantages to HTML''' | |||
*# Very hard for QA | *# Very hard for QA | ||
** If localizer changes something incorrectly (i.e. accidentally removes some html like "</h1>", that localizer can break everything.) | ** If localizer changes something incorrectly (i.e. accidentally removes some html like "</h1>", that localizer can break everything.) | ||