Difference between revisions of "Internationalization/code parser"

 
 
(10 intermediate revisions by 4 users not shown)
Line 1: Line 1:
== Summary ==
+
[[Category:Internationalization]]
That's what this part of the project should achieve:
+
[[Category:Internationalization SA project]]
* reading and parsing of MO files containing the strings and their translations
+
 
* organize the object collection in an incremental way: don't load the whole file if it's not needed
+
==Code Parser==
* give a simple interface to the localization class, so that the strings can be printed out without too much efforts
+
 
 +
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===
 +
 
 +
<strike>First commit Real Soon Now&trade;</strike> Initial commit made.
 +
 
 +
Status is currently (16:24, 1 July 2006 (CEST)):
 +
 
 +
* Clicky thing:  <font color="orange">Mostly works. Some bugs related to escaping that need fixing.</font>
 +
* AST visitor:  <font color="green">No apparent bugs</font>
 +
* .po representation: <font color="orange">Works. Needs word wrapping for long entries.</font>
 +
* GUI: <font color="green">Works</font>

Latest revision as of 08:31, 15 August 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™ Initial commit made.

Status is currently (16:24, 1 July 2006 (CEST)):

  • Clicky thing: Mostly works. Some bugs related to escaping that need fixing.
  • AST visitor: No apparent bugs
  • .po representation: Works. Needs word wrapping for long entries.
  • GUI: Works