CARVIEW |
Select Language
HTTP/2 200
date: Wed, 08 Oct 2025 22:09:23 GMT
content-type: text/html
content-encoding: gzip
last-modified: Thu, 13 Jul 2023 18:23:49 GMT
cache-control: max-age=2592000, public
expires: Fri, 07 Nov 2025 22:09:23 GMT
vary: Accept-Encoding
access-control-allow-origin: *
x-request-id: 98b8f6580fc86f7a
strict-transport-security: max-age=15552015; preload
x-frame-options: deny
x-xss-protection: 1; mode=block
cf-cache-status: EXPIRED
set-cookie: __cf_bm=xYQKzzGp.Y.hgXxSg3qHVfv.DfjL._REnEbcu0NrcOY-1759961363-1.0.1.1-m2LuoQ4WiNVrQGkKtAq7XVy4AwZZc55LCDj5ezkfgWuRUlVIfl7.tJKjgjTfSQl6DSPYnbwVrtvsnSzvvmBzmTa0YbRat.uMW.tlY1SFr9U; path=/; expires=Wed, 08-Oct-25 22:39:23 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98b8f6580fc86f7a-BLR
alt-svc: h3=":443"; ma=86400
RE: I18N-ISSUE-240: Bad example: Hard-coded coordinates [ITS-20] from Yves Savourel on 2013-01-19 (public-multilingualweb-lt-comments@w3.org from January 2013)
RE: I18N-ISSUE-240: Bad example: Hard-coded coordinates [ITS-20]
- From: Yves Savourel <ysavourel@enlaso.com>
- Date: Sat, 19 Jan 2013 06:12:20 -0700
- To: "'Internationalization Working Group'" <public-multilingualweb-lt-comments@w3.org>
- CC: <www-international@w3.org>
- Message-ID: <assp.0731fd845b.assp.0731ead92b.001201cdf646$9d3f5710$d7be0530$@com>
> https://www.w3.org/TR/2012/WD-its20-20121206/#motivation-its-issues > Example 2 contains data that is highly inappropriate for an internationalized > application: Hard-coded coordinates for user interface elements. > Such coordinates would have to be changed during localization to accommodate > strings that expand or shrink during translation, larger or smaller fonts > used for a localized user interface, expansion or shrinkage in surrounding > content, or a change in the overall directionality of the user interface. > These items should be removed from the example. The example is meant to show real-life problematic files, not to demonstrate best practices. This said, today's UI do a better job of auto-resizing, so we could update the example to reflect that. For instance, replacing elements like: <data type="coordinates">12,20,50,14</data> by something like: <data type="position">12,20</data> Thanks for pointing this out. -yves
Received on Saturday, 19 January 2013 13:12:55 UTC