W3C home > Mailing lists > Public > public-i18n-its@w3.org > April to June 2005

RE: [ESW Wiki] Update of "its0503ReqSpan"

From: Richard Ishida <ishida@w3.org>
Date: Sat, 2 Apr 2005 10:23:37 +0100
To: <public-i18n-its@w3.org>
Message-Id: <20050402092337.E00504F01F@homer.w3.org>


You will have been seeing messages like this that are an indication that I think I've finally solved our wiki set up problems. I have set up two wiki pages so far (see the links in the email).  

At the moment only I can edit these pages.  Each of you needs to set up a user login at esw.w3.org. To do this go to http://esw.w3.org/, follow the link to "ESW wiki", and click on "User Preferences" on the page you get to. Important: In the name field use your real name, **with no spaces**, eg. RichardIshida.  Make up a password and enter it in both boxes, and add your email address. Then send me your user name so I can give you write access.

You won't need to subscribe to each page, since when I create each wiki page I have subscribed a user called ItsList who's email address is the public-i18n-its list.  This ensures that we all receive notification and provides a very secure record of all edits.

See the top of each wiki for instructions about how to edit.

At the top of the wiki there is currently a link to the GEO article development process indicating the status of the content. In due course we should create an ITS specific version of this process and link to that.

Have fun.


Richard Ishida

contact info:

W3C Internationalization:

Publication blog:

> -----Original Message-----
> From: public-i18n-its-request@w3.org 
> [mailto:public-i18n-its-request@w3.org] On Behalf Of 
> w3t-archive+esw-wiki@w3.org
> Sent: 02 April 2005 09:37
> To: public-i18n-its@w3.org
> Subject: [ESW Wiki] Update of "its0503ReqSpan"
> Dear Wiki user,
> You have subscribed to a wiki page or wiki category on "ESW 
> Wiki" for change notification.
> The following page has been changed by RichardIshida:
> http://esw.w3.org/topic/its0503ReqSpan
> --------------------------------------------------------------
> ----------------
> + '''[MD] I think this is clear enough for the moment. We can 
> refine this later if needed.'''
> + 
> + 
>   == Background: ==
>   This allows localisation tools to determine their behaviour 
> on certain sections of text. This could be for sections of 
> text that need to be translated by a domain-expert (as with 
> source code fragments) or need special terminology in order 
> to be properly translated. In particular, a span-like element 
> can be useful to help translation tools determine where to 
> apply sentence-breaks and also to assist word-counting 
> algorithms. Other uses are foreseen, within the scope of the ITS.
> + 
> + '''[MD] This omits a very important use of the <span> 
> element, and the main reason it was added to HTML originally: 
> language information.
> + Language information is important both for 
> internationalization (e.g. different styling according to 
> language) as well as localization (text needs to go to 
> different translator, or not translated, or otherwise treated 
> differently).'''
> + 
>   One example would be the following sentence, which contains 
> some source code that we would like to treat specially during 
> translation :
> @@ -49, +56 @@
>   Are there any more that people can think of that don't 
> directly fall into other sections, that is, I expect we would 
> have particular requirements for dealing with terms, phrases, 
> etc. elsewhere in the requirements document.
>   ]''
> + 
> + '''[MD] I think two more aspects should be mentioned shortly:
> + 
> +  - Any element that in and by itself doesn't carry specific 
> semantics
> +    is fine. If the target schema already has such an element, fine.
> +  - Say where the element should be allowed in the target schema:
> +    Everywhere where natural language/translatable text can appear.
> + 
> + I'm using the term 'target schema' here to talk about the 
> schema that we are trying to internationalize/localize.'''
Received on Saturday, 2 April 2005 09:23:58 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:43:04 UTC