[tei-council] ITS at W3C (was:Re: roma, documentation, i18n)

[Natasha Smith]

I fully support this move and hope we will be successful in forming a good
working relationship with W3C. And thank you to Sebastian for agreeing to
put effort - and time! - into it.



on the related topic and following-up the conversation of 5/23-5/24 about
the priority of languages. I agree with Christian that we might be more
interested in investing in regions/languages that are not yet covered to the
extent they should be - as they have real potential (ex., Japan, China,
Korea.) But I understand that the practicality and reality (I can start with
as simple as finding not just *a* translator, but a reliable one) might
change the priority list and its order.



Finally, I wanted to check what we already have on the site and remembering
that tei has been translated at some point to Russian, I did search and
discovered the following broken links on http://www.tei-c.org.uk/Lite/



http://www.tei-c.org.uk/Lite/teiu5_fr.tei

http://www.tei-c.org.uk/Lite/teiu5_zh.xsw

http://www.tei-c.org.uk/Lite/teiu5_kr.tei

http://www.tei-c.org.uk/Lite/teiu5_ru.rtf



also, in http://www.tei-c.org.uk/Software/ there is a link to TEI Tools by
Boris Tobotras that is password-protected:

http://xtalk.price.ru/SGML/TEItools/index-en.html



best, n



----- Original Message ----- 
From: "Christian Wittern" <wittern at kanji.zinbun.kyoto-u.ac.jp>
To: <tei-council at lists.village.Virginia.EDU>
Sent: Monday, June 27, 2005 11:36 PM
Subject: [tei-council] ITS at W3C (was:Re: roma, documentation, i18n)


>
> Council members,
>
> As it happens, I had a long conversation with Felix Sasaki yesterday,
> who joined the W3C host in Japan this April and works there on i18n
> issues.  He mentioned work going on at the W3C at the ITS
> (Internationalization Tag Set,
> cf. http://www.w3.org/International/its/) group, which seems to have
> some overlap with our problem here. The mission statement for the
> group is as follows:
> <quote>
> Mission: Develop a set of elements and attributes that can be used
> with new DTDs/Schemas to support the internationalization and
> localization of documents; and provide best practice techniques for
> developers of DTDs/Schemas that show how to enable
> internationalization of their documents.
> </quote>
>
> They are not ready and it might be overkill, but it seems to me that
> we should monitor this.
>
> He asked also if somebody from the TEI would be interested to join
> this group; we also discussed if the TEI could/should consider to
> enter into some formal relation with the W3C.  I would be interested
> in opinions from the Council members on the desirability of such a
> development.
>
> Sebastian Rahtz <sebastian.rahtz at computing-services.oxford.ac.uk> writes:
>
> > Christian Wittern wrote:
> >
> >>What would be the advantage of pulling this into the main P5 source?
> >>I see only added maintainance cost with no real benefit.  You could as
> >>easily pull them out and merge them into the tree on runtime.
> >>
> >>
> > perhaps its matter of semantics; if the main ODD processing
> > software expects to find the various language-specific <desc>s
> > in site in the main document, then it does not much matter whether
> > the merge is at runtime or at source. I just want to avoid a "normal"
> > ODD processor from having to know about the language modules.
> >
> >>>dont forget attributes, and vallists, by the way
>
> >>But attributes should be covered within the elementSpec, shouldnt
> >>they.
> >>
> > and the classSpecs.
>
> -- 
>  Christian Wittern
>  Institute for Research in Humanities, Kyoto University
>  47 Higashiogura-cho, Kitashirakawa, Sakyo-ku, Kyoto 606-8265, JAPAN
> _______________________________________________
> tei-council mailing list
> tei-council at lists.village.Virginia.EDU
> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
>