September 14, 2009 at 18:34I want 3 !!! My work on errors on the idea of unifying interfaces
Judging by the minuses, I came to the conclusion that I did not quite understand the idea of unifying the interfaces of web projects. I apologize to everyone and correct myself ...
The idea of unifying interfaces was initially proposed only for socially significant (socially oriented) Internet projects. Those that go beyond the idea of one state. Like Facebook, Twitter.
Translate common interface, narrative, contacts. Those. that information that does not change often. And the user only selects either his own language from the drop-down list, or the browser automatically (Accept-Language) picks up the user's local settings. Moreover, the language menu is installed in a standard place. Following the example of copyright. It is placed at the bottom of the page of the site and has a unified view.
Naturally, it is necessary to approach this topic at the interstate level. For each individual developer simply will not pull the localization under "all" languages. But if everyone agrees, such as "www" for sites and "ftp" well ... you yourself know why :) then there will be no problems with unifying interfaces ...
Exit with Google translate does not work, at least for now ... it translates still oh how not a buzz from the point of view of understanding.
The idea may seem utopian. However, it is full of examples when some standards were introduced “from scratch” ... and everything became very convenient. The same OpenID. If he was officially supported, if I may say so, then it would be much more convenient to work on social networks, online stores, forums ...
I want 1 , I want 2 .
The idea of unifying interfaces was initially proposed only for socially significant (socially oriented) Internet projects. Those that go beyond the idea of one state. Like Facebook, Twitter.
Translate common interface, narrative, contacts. Those. that information that does not change often. And the user only selects either his own language from the drop-down list, or the browser automatically (Accept-Language) picks up the user's local settings. Moreover, the language menu is installed in a standard place. Following the example of copyright. It is placed at the bottom of the page of the site and has a unified view.
Naturally, it is necessary to approach this topic at the interstate level. For each individual developer simply will not pull the localization under "all" languages. But if everyone agrees, such as "www" for sites and "ftp" well ... you yourself know why :) then there will be no problems with unifying interfaces ...
Exit with Google translate does not work, at least for now ... it translates still oh how not a buzz from the point of view of understanding.
The idea may seem utopian. However, it is full of examples when some standards were introduced “from scratch” ... and everything became very convenient. The same OpenID. If he was officially supported, if I may say so, then it would be much more convenient to work on social networks, online stores, forums ...
I want 1 , I want 2 .