Difference between revisions of "Internationalization/code parser"

m
Line 1: Line 1:
 
[[Category:Internationalization]]
 
[[Category:Internationalization]]
  
page moved to [[Internationalization/mo parser|mo parser]] because content didn't match title. --[[User:Carlo|Carlo]] 18:23, 7 May 2006 (CEST)
+
==Code Parser==
 +
 
 +
This part of the project should produce a clickable thing in EiffelStudio.
 +
 
 +
When actually clicked, it should examine the current project. If the current project includes our wonderful framework, this clicky thing should look at the calls to the i18n and i18n_plural functions and produce a .po file based on the strings provided to those functions as arguments.
 +
 
 +
===Composition===
 +
 
 +
There are several things needed:
 +
 
 +
* The clicky thing itself.
 +
* An ast visitor that finds calls to i18n and i18n_parser and then extracts arguments.
 +
* A set of classes that provides a nice representation of a .po file.
 +
* A GUI to ask where to place the .po file and if the project should first be recompiled.
 +
 
 +
===Progress===
 +
 
 +
First commit Real Soon Now™

Revision as of 04:36, 14 June 2006


Code Parser

This part of the project should produce a clickable thing in EiffelStudio.

When actually clicked, it should examine the current project. If the current project includes our wonderful framework, this clicky thing should look at the calls to the i18n and i18n_plural functions and produce a .po file based on the strings provided to those functions as arguments.

Composition

There are several things needed:

  • The clicky thing itself.
  • An ast visitor that finds calls to i18n and i18n_parser and then extracts arguments.
  • A set of classes that provides a nice representation of a .po file.
  • A GUI to ask where to place the .po file and if the project should first be recompiled.

Progress

First commit Real Soon Now™