Typecraft v2.5
Jump to: navigation, search

Difference between revisions of "Bulletin Board 2010 - 2012"

Line 1: Line 1:
 +
==TypeCraft Presentation at [http://ilk.uvt.nl/LaTeCH2011/prgr.html ACL 2011 workshop] on: Language Technology for Cultural Heritage, Social Sciences, and Humanities==
 +
 +
Friday June 24, 2011 - Portland Marriott Downtown Waterfront, Portland, Oregon, USA.
 +
 
==Have you seen this?==
 
==Have you seen this?==
  

Revision as of 21:24, 26 May 2011

TypeCraft Presentation at ACL 2011 workshop on: Language Technology for Cultural Heritage, Social Sciences, and Humanities

Friday June 24, 2011 - Portland Marriott Downtown Waterfront, Portland, Oregon, USA.

Have you seen this?

The picture Gallery from the Trondheim LDD-workshop is available here Trondheim_Workshop_in_Language_Description_and_Documentation_Gallery.

--Dorothee Beermann 19:36, 6 April 2011 (UTC)

Do you need help with structuring your TCwiki page?

Nathan Colton has joined TypeCraft to assist you with the structuring of your TCwiki pages.

You might already have noticed that we have started a 'Spring Cleaning' initiative for all TCwiki pages Smiley.jpg.png.

Our main goal is to motivate all of you to start reporting about your annotation projects and linguistic work related to your project. So far we did not look too hard at editorial issues. Also concerning references we have been rather relaxed.

The most important thing is still to get on the wiki and to write about the linguistic challenges that one faces when taking Interlinear Glossing seriously. Yet, with more and more TCwiki pages coming online it becomes important to provide adequate references. Not only the linguistic data, but all information that you give on a TCwiki page needs to be verifiable. For each claim you make you want to use material from the TC database to substantiate your claims. References to published sources are needed. Sometimes secondary sources are named, but not sufficiently references. This has to be changed. Remember also that also picture material integrated into your TCwiki page must be sourced properly.

All questions concerning editing your pages and referencing correctly can now directly be addressed to Nathan. Please use Nathan's TC e-mail to contact him. You find his mail address as a link (E-mail this user) on the navigation bar of Nathan's user page.

Infobox Language available

Search a language family by clicking on a colour box
Afro-Asiatic Niger-Congo Nilo-Saharan - no representative yet Khoisan - no representative yet
Indo-European Caucasian - no representative yet Altaic - no representative yet Dravidian Paleosiberian - no representative yet
Austronesian - - no representative yet Austro-Asiatic - no representative yet Sino-Tibetan Papuan - no representative yet
American Dené-Yeniseian - no representative yet Hmong-Mien - no representative yet
Creole/Pidgin/Mixed Eskimo-Aleut - no representative yet Uralic - no representative yet Australian - no representative yet

You now can add a Infobox about your language to your TC-wiki page.

A basic infobox looks as shown below:

{{Infobox language ← this calls the template
|name=name of language ← the name of the language needs to be given
|familycolor=appropriate language family ← refer to the coloured chart to the right (or above, depending on your browser), and type the name shown there (so for example you type: Indo-European); this will add the appropriate family color to the template top
}} ← this ends the template call

You probably would want to add some more parameters to your infobox. You find an overview over possible parameters on the Skeleton Infobox Language page.

Mapping between TypeCraft Glosses and the Gold Ontology

Ontology.jpeg TypeCraft has been updated to GOLD 2010! --Dorothee Beermann 21:03, 22 August 2010 (UTC)

New Workshop at CIIL, Mysore India coming up

Due to time conflicts the workshop has been rescheduled for the spring 2011

TypeCraft Workshop at the Central Institute of Indian Languages

End of October/Beginning of November 2010. More information as it becomes available.