mirror of
https://github.com/GrammaticalFramework/gf-core.git
synced 2026-04-09 13:09:33 -06:00
07ed00140a
The new logo is in the new directory doc/Logos. The old logo has been moved there too. The documentation has been updated to refer to the new logo. The new logo was provided in SVG format by Krasimir, but PNG files are included as well. There are some new rules in doc/Makefile to convert from SVG to PNG, which you can use if you edit the SVG files.
312 lines
9.9 KiB
HTML
312 lines
9.9 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
|
<HTML>
|
|
<HEAD>
|
|
<META NAME="generator" CONTENT="http://txt2tags.sf.net">
|
|
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
|
|
<TITLE>GF Project Ideas</TITLE>
|
|
</HEAD><BODY BGCOLOR="white" TEXT="black">
|
|
|
|
<P>
|
|
<center>
|
|
<IMG ALIGN="middle" SRC="Logos/gf0.png" BORDER="0" ALT="">
|
|
</center>
|
|
</P>
|
|
|
|
<P ALIGN="center"><CENTER>
|
|
<H1>GF Project Ideas</H1>
|
|
<FONT SIZE="4">
|
|
<I>Resource Grammars, Web Applications, etc</I><BR>
|
|
contact: Aarne Ranta (aarne at chalmers dot se)
|
|
</FONT></CENTER>
|
|
|
|
<P></P>
|
|
<HR NOSHADE SIZE=1>
|
|
<P></P>
|
|
<UL>
|
|
<LI><A HREF="#toc1">Resource Grammar Implementations</A>
|
|
<UL>
|
|
<LI><A HREF="#toc2">Tasks</A>
|
|
<LI><A HREF="#toc3">Who is qualified</A>
|
|
<LI><A HREF="#toc4">The Summer School</A>
|
|
</UL>
|
|
<LI><A HREF="#toc5">Other project ideas</A>
|
|
<UL>
|
|
<LI><A HREF="#toc6">GF interpreter in Java</A>
|
|
<LI><A HREF="#toc7">GF interpreter in C#</A>
|
|
<LI><A HREF="#toc8">GF localization library</A>
|
|
<LI><A HREF="#toc9">Multilingual grammar applications for mobile phones</A>
|
|
<LI><A HREF="#toc10">Multilingual grammar applications for the web</A>
|
|
<LI><A HREF="#toc11">GMail gadget for GF</A>
|
|
</UL>
|
|
<LI><A HREF="#toc12">Dissemination and intellectual property</A>
|
|
</UL>
|
|
|
|
<P></P>
|
|
<HR NOSHADE SIZE=1>
|
|
<P></P>
|
|
<A NAME="toc1"></A>
|
|
<H2>Resource Grammar Implementations</H2>
|
|
<P>
|
|
GF Resource Grammar Library is an open-source computational grammar resource
|
|
that currently covers 12 languages.
|
|
The Library is a collaborative effort to which programmers from many countries
|
|
have contributed. The next goal is to extend the library
|
|
to all of the 23 official EU languages. Also other languages
|
|
are welcome all the time. The following diagram show the current status of the
|
|
library. Each of the red and yellow ones are a potential project.
|
|
</P>
|
|
<P>
|
|
<center>
|
|
<IMG ALIGN="middle" SRC="school-langs.png" BORDER="0" ALT="">
|
|
</center>
|
|
</P>
|
|
<P>
|
|
<I>red=wanted, green=exists, orange=in-progress, solid=official-eu, dotted=non-eu</I>
|
|
</P>
|
|
<P>
|
|
The linguistic coverage of the library includes the inflectional morphology
|
|
and basic syntax of each language. It can be used in GF applications
|
|
and also ported to other formats. It can also be used for building other
|
|
linguistic resources, such as morphological lexica and parsers.
|
|
The library is licensed under LGPL.
|
|
</P>
|
|
<A NAME="toc2"></A>
|
|
<H3>Tasks</H3>
|
|
<P>
|
|
Writing a grammar for a language is usually easier if other languages
|
|
from the same family already have grammars. The colours have the same
|
|
meaning as in the diagram above; in addition, we use boldface for the
|
|
red, still unimplemented languages and italics for the
|
|
orange languages in progress. Thus, in particular, each of the languages
|
|
coloured red below are possible programming projects.
|
|
</P>
|
|
<P>
|
|
Baltic:
|
|
</P>
|
|
<UL>
|
|
<LI><font color="red"><b> Latvian </b></font>
|
|
<LI><font color="red"><b> Lithuanian </b></font>
|
|
</UL>
|
|
|
|
<P>
|
|
Celtic:
|
|
</P>
|
|
<UL>
|
|
<LI><font color="red"><b> Irish </b></font>
|
|
</UL>
|
|
|
|
<P>
|
|
Fenno-Ugric:
|
|
</P>
|
|
<UL>
|
|
<LI><font color="red"><b> Estonian </b></font>
|
|
<LI><font color="green" size="-1"> Finnish </font>
|
|
<LI><font color="red"><b> Hungarian </b></font>
|
|
</UL>
|
|
|
|
<P>
|
|
Germanic:
|
|
</P>
|
|
<UL>
|
|
<LI><font color="green" size="-1"> Danish </font>
|
|
<LI><font color="red"><b> Dutch </b></font>
|
|
<LI><font color="green" size="-1"> English </font>
|
|
<LI><font color="green" size="-1"> German </font>
|
|
<LI><font color="green" size="-1"> Norwegian </font>
|
|
<LI><font color="green" size="-1"> Swedish </font>
|
|
</UL>
|
|
|
|
<P>
|
|
Hellenic:
|
|
</P>
|
|
<UL>
|
|
<LI><font color="red"><b> Greek </b></font>
|
|
</UL>
|
|
|
|
<P>
|
|
Indo-Iranian:
|
|
</P>
|
|
<UL>
|
|
<LI><font color="orange"><i> Hindi </i></font>
|
|
<LI><font color="orange"><i> Urdu </i></font>
|
|
</UL>
|
|
|
|
<P>
|
|
Romance:
|
|
</P>
|
|
<UL>
|
|
<LI><font color="green" size="-1"> Catalan </font>
|
|
<LI><font color="green" size="-1"> French </font>
|
|
<LI><font color="green" size="-1"> Italian </font>
|
|
<LI><font color="red"><b> Portuguese </b></font>
|
|
<LI><font color="orange"><i> Romanian </i></font>
|
|
<LI><font color="green" size="-1"> Spanish </font>
|
|
</UL>
|
|
|
|
<P>
|
|
Semitic:
|
|
</P>
|
|
<UL>
|
|
<LI><font color="orange"><i> Arabic </i></font>
|
|
<LI><font color="red"><b> Maltese </b></font>
|
|
</UL>
|
|
|
|
<P>
|
|
Slavonic:
|
|
</P>
|
|
<UL>
|
|
<LI><font color="green" size="-1"> Bulgarian </font>
|
|
<LI><font color="red"><b> Czech </b></font>
|
|
<LI><font color="orange"><i> Polish </i></font>
|
|
<LI><font color="green" size="-1"> Russian </font>
|
|
<LI><font color="red"><b> Slovak </b></font>
|
|
<LI><font color="red"><b> Slovenian </b></font>
|
|
</UL>
|
|
|
|
<P>
|
|
Tai:
|
|
</P>
|
|
<UL>
|
|
<LI><font color="orange"><i> Thai </i></font>
|
|
</UL>
|
|
|
|
<P>
|
|
Turkic:
|
|
</P>
|
|
<UL>
|
|
<LI><font color="orange"><i> Turkish </i></font>
|
|
</UL>
|
|
|
|
<A NAME="toc3"></A>
|
|
<H3>Who is qualified</H3>
|
|
<P>
|
|
Writing a resource grammar implementation requires good general programming
|
|
skills, and a good explicit knowledge of the grammar of the target language.
|
|
A typical participant could be
|
|
</P>
|
|
<UL>
|
|
<LI>native or fluent speaker of the target language
|
|
<LI>interested in languages on the theoretical level, and preferably familiar
|
|
with many languages (to be able to think about them on an abstract level)
|
|
<LI>familiar with functional programming languages such as ML or Haskell
|
|
(GF itself is a language similar to these)
|
|
<LI>on Master's or PhD level in linguistics, computer science, or mathematics
|
|
</UL>
|
|
|
|
<P>
|
|
But it is the quality of the assignment that is assessed, not any formal
|
|
requirements. The "typical participant" was described to give an idea of
|
|
who is likely to succeed in this.
|
|
</P>
|
|
<A NAME="toc4"></A>
|
|
<H3>The Summer School</H3>
|
|
<P>
|
|
A Summer School on resource grammars and applications will
|
|
be organized at the campus of Chalmers University of Technology in Gothenburg,
|
|
Sweden, on 17-28 August 2009. It can be seen as a natural checkpoint in
|
|
a resource grammar project; the participants are assumed to learn GF before
|
|
the Summer School, but how far they have come in their projects may vary.
|
|
</P>
|
|
<P>
|
|
More information on the Summer School web page:
|
|
</P>
|
|
<P>
|
|
<A HREF="http://www.cs.chalmers.se/Cs/Research/Language-technology/GF/doc/gf-summerschool.html"><CODE>http://www.cs.chalmers.se/Cs/Research/Language-technology/GF/doc/gf-summerschool.html</CODE></A>
|
|
</P>
|
|
<A NAME="toc5"></A>
|
|
<H2>Other project ideas</H2>
|
|
<A NAME="toc6"></A>
|
|
<H3>GF interpreter in Java</H3>
|
|
<P>
|
|
The idea is to write a run-time system for GF grammars in Java. This enables
|
|
the use of <B>embedded grammars</B> in Java applications. This project is
|
|
a fresh-up of <A HREF="http://www.cs.chalmers.se/~bringert/gf/gf-java.html">earlier work</A>,
|
|
now using the new run-time format PGF and addressing a new parsing algorithm.
|
|
</P>
|
|
<P>
|
|
Requirements: Java, Haskell, basics of compilers and parsing algorithms.
|
|
</P>
|
|
<A NAME="toc7"></A>
|
|
<H3>GF interpreter in C#</H3>
|
|
<P>
|
|
The idea is to write a run-time system for GF grammars in C#. This enables
|
|
the use of <B>embedded grammars</B> in C# applications. This project is
|
|
similar to <A HREF="http://www.cs.chalmers.se/~bringert/gf/gf-java.html">earlier work</A>
|
|
on Java, now addressing C# and using the new run-time format PGF.
|
|
</P>
|
|
<P>
|
|
Requirements: C#, Haskell, basics of compilers and parsing algorithms.
|
|
</P>
|
|
<A NAME="toc8"></A>
|
|
<H3>GF localization library</H3>
|
|
<P>
|
|
This is an idea for a software localization library using GF grammars.
|
|
The library should replace strings by grammar rules, which can be conceived
|
|
as very smart templates always guaranteeing grammatically correct output.
|
|
The library should be based on the
|
|
<A HREF="http://www.cs.chalmers.se/Cs/Research/Language-technology/GF/lib/resource/doc/synopsis.html">GF Resource Grammar Library</A>, providing infrastructure
|
|
currently for 12 languages.
|
|
</P>
|
|
<P>
|
|
Requirements: GF, some natural languages, some localization platform
|
|
</P>
|
|
<A NAME="toc9"></A>
|
|
<H3>Multilingual grammar applications for mobile phones</H3>
|
|
<P>
|
|
GF grammars can be compiled into programs that can be run on different
|
|
platforms, such as web browsers and mobile phones. An example is a
|
|
<A HREF="http://www.cs.chalmers.se/Cs/Research/Language-technology/GF/demos/index-numbers.html">numeral translator</A> running on both these platforms.
|
|
</P>
|
|
<P>
|
|
The proposed project is rather open: find some cool applications of
|
|
the technology that are useful or entertaining for mobile phone users. A
|
|
part of the project is to investigate implementation issues such as making
|
|
the best use of the phone's resources. Possible applications have
|
|
something to do with translation; one suggestion is an sms editor/translator.
|
|
</P>
|
|
<P>
|
|
Requirements: GF, JavaScript, some phone application development tools
|
|
</P>
|
|
<A NAME="toc10"></A>
|
|
<H3>Multilingual grammar applications for the web</H3>
|
|
<P>
|
|
This project is rather open: find some cool applications of
|
|
the technology that are useful or entertaining on the web. Examples include
|
|
</P>
|
|
<UL>
|
|
<LI>translators: see <A HREF="http://tournesol.cs.chalmers.se:41296/translate">demo</A>
|
|
<LI>multilingual wikis: see <A HREF="http://csmisc14.cs.chalmers.se/~meza/restWiki/wiki.cgi">demo</A>
|
|
<LI>fridge magnets: see <A HREF="http://tournesol.cs.chalmers.se:41296/fridge">demo</A>
|
|
</UL>
|
|
|
|
<P>
|
|
Requirements: GF, JavaScript or Java and Google Web Toolkit, CGI
|
|
</P>
|
|
<A NAME="toc11"></A>
|
|
<H3>GMail gadget for GF</H3>
|
|
<P>
|
|
It is possible to add custom gadgets to GMail. If you are going to write
|
|
e-mail in a foreign language then you probably will need help from
|
|
dictonary or you may want to check something in the grammar. GF provides
|
|
all resources that you may need but you have to think about how to
|
|
design gadget that fits well in the GMail environment and what
|
|
functionality from GF you want to expose.
|
|
</P>
|
|
<P>
|
|
Requirements: GF, Google Web Toolkit
|
|
</P>
|
|
<A NAME="toc12"></A>
|
|
<H2>Dissemination and intellectual property</H2>
|
|
<P>
|
|
All code suggested here will be released under the LGPL just like
|
|
the current resource grammars and run-time GF libraries,
|
|
with the copyright held by respective authors.
|
|
</P>
|
|
<P>
|
|
As a rule, the code will be distributed via the GF web site.
|
|
</P>
|
|
|
|
<!-- html code generated by txt2tags 2.4 (http://txt2tags.sf.net) -->
|
|
<!-- cmdline: txt2tags -\-toc gf-ideas.txt -->
|
|
</BODY></HTML>
|