Hi Chris,
Thanks much. Right-to-left support can be added as a i18n
requirement. (part of rtl layout functionality, ie. converting the
Arabic/Hebrew UTF-8 text to RTL form is supported by the browser, but
the wiki s/w is responsible for RTL placements of interface components
like menus etc)
We separated out the ease of doing localization into a separate category
because thats a high priority requirement determining our success on
making it easier for the end users to localize the pages without the
site admin's interference, also the content organization to enable
organic growth of languages should also be considered.
There can be fully i18ned wikis which makes it difficult for users to
add pages. dropdown language menu's etc are convenience mechanisms that
we put in place to make it easy for end users. A set of requirements in
this area is essential for reducing the learning curve on contributing
and poising the site for intuitive and organic growth.
globalization = i18n + l10n
this is the common terminology, i18n is not used in place of l10n commonly.
Regards,
Suresh
Chris Phelan wrote:
> Suresh,
>
> Yes, it does make sense to make your proposed edits, but as all the i18n
> requirements are formative at the moment I'd like to wait to see if we
> get any more requirements - right-to-left support for example.
>
> I am aware of the distinction between localization and
> internationalization, but removed a similar explanation from an earlier
> draft I had as 'internationalization' is often used as a blanket term,
> rightly or wrongly. Separating them as you propose also allows for, say,
> Unicode to be essential but for drop down menus (or similar) for
> selecting the language to be a different priority. I'm not suggesting
> that should happen, by the way, I'm just trying to cater for what is a
> complicated area.
>
> Chris
>
>
> Jim Grisanzio wrote:
>
>> Cross-posting to website-discuss. -- Jim
>>
>> Suresh Chandrasekharan wrote:
>>
>>
>>> Hi Jim/Chris,
>>>
>>> In
>>>
>>> http://www.opensolaris.org/os/project/website/wiki_requirements/
>>>
>>> Does it makes sense if we are modifying C5 as E5 withe the following
>>> proposed changes ?
>>>
>>> Regards,
>>> Suresh
>>>
>>> -----------------------------------------------------------------------------------------------------------------------------------
>>>
>>> *E5 The software should support internationalization and localization
>>>
>>> *
>>>
>>> Internationalization is the process of designing software so that it can
>>> be adapted to various languages and regions *without engineering
>>> changes*. Localization is the process of adapting software for a
>>> specific region or language by *adding locale specific components and
>>> translating text*.
>>>
>>> Wiki internationalization could be broadly segmented as:
>>>
>>> 1. Base i18n support in software: Mainly Unicode support.
>>>
>>> Wiki localization could be broadly segmented as:
>>>
>>> 1. Infrastructure support for ease of localization: Software should
>>> have interfaces so that it's easy for users to extend support to
>>> other languages. Drop down menus to select languages when creating
>>> content , language based web content organization etc. will come
>>> under this.
>>> 2. Translation of the 'structural' components of the site: menus,
>>> button text, icons etc. For example, with J2EE applications, such
>>> localization is achieved by using locale-specific resource bundles.
>>> 3. Page translations - for example FAQs, developer guides, governance
>>> pages. Also pages owned by a particular community, e.g. a MDB or
>>> ZFS 'HowTo' guide.
>>>
>>> All three points require the software to be able to render different
>>> languages. Community contributed requirements which address
>>> internationalization issues (and, in part, wikis) are available here
>>> <http://opensolaris.org/os/project/portals/portals-v2/> and the current
>>> Country Portals are detailed here
>>> <http://opensolaris.org/os/project/portals/>.
>>>
>>> -----------------------------------------------------------------------------------------------------------------------------------
>>> Jim Grisanzio wrote:
>>>
>>>
>>>
>>>> hey ...
>>>>
>>>> Chris Phelan from the OpenSolaris engineering team has starting a
>>>> conversation on website-discuss about wiki requirements and tools for
>>>> opensolaris.org. If you have an interest in this, please feel free to
>>>> follow and contribute. If you are leading a country/language portal,
>>>> please follow very closely and participate directly because this is
>>>> the conversation that will lead to the upgrade of the site and the
>>>> replacement of the current portals with something very much better. :)
>>>> Sign up to website-discuss here:
>>>> http://mail.opensolaris.org/mailman/listinfo/website-discuss
>>>>
>>>> Jim
>>>>
>>>>
>>>>
>>>>
>>>>
>
> _______________________________________________
> website-discuss mailing list
> [email protected]
>
_______________________________________________
website-discuss mailing list
[email protected]
