Jump to: navigation, search

Difference between revisions of "Babel / Development Status Meetings / 2010-03-29"

(New page: === Attendees === {| border="1" |- | Kit |   |- | Denis |   |- | Gabe |   |- | Antoine |   |- | Nigel |   |- | Jeff |   |- | Margaret |   |} ==...)
 
(Topics)
Line 31: Line 31:
 
**Each project can specify its own plugin exclude patterns (used for both properties & doc files extraction)
 
**Each project can specify its own plugin exclude patterns (used for both properties & doc files extraction)
 
**May need a few twists to exclude some configuration XML files
 
**May need a few twists to exclude some configuration XML files
 +
*How should we save the doc files? Thoughts from Denis:
 +
**Since there is no turnkey solution for doing this, here are a couple of solutions I can think of for Babel.
 +
**1. We use an external VCS as Antoine suggested.  I think this is an entirely valid approach, although perhaps a bit more complex.
 +
**2. We do like MediaWiki -- save the entire file on each save.  If it works for them, it will work for us.  Except:
 +
***when a user wants to diff two versions, we could use one of the diff libraries Gabe pointed out.  No need to go to shell or write our own.
 +
***older revisions could pass through the gzip lib and be stored in compressed format.  If a user wants to diff to an older version, we unzip it first, then pass it through the diff engine.
 +
***one design consideration here would be to use many tables -- perhaps one translation table per language.  Or, one table to contain the 'latest' of everything and one table per language for the gzipped older versions.
 
[[Category:Babel]]
 
[[Category:Babel]]

Revision as of 06:52, 29 March 2010

Attendees

Kit  
Denis  
Gabe  
Antoine  
Nigel  
Jeff  
Margaret  

Topics

  • Doc translation proposal - progress
    • Was able to extact doc (HTM* & XML) files from Sequoyah & Eclipse projects
    • Each project can specify its own plugin exclude patterns (used for both properties & doc files extraction)
    • May need a few twists to exclude some configuration XML files
  • How should we save the doc files? Thoughts from Denis:
    • Since there is no turnkey solution for doing this, here are a couple of solutions I can think of for Babel.
    • 1. We use an external VCS as Antoine suggested. I think this is an entirely valid approach, although perhaps a bit more complex.
    • 2. We do like MediaWiki -- save the entire file on each save. If it works for them, it will work for us. Except:
      • when a user wants to diff two versions, we could use one of the diff libraries Gabe pointed out. No need to go to shell or write our own.
      • older revisions could pass through the gzip lib and be stored in compressed format. If a user wants to diff to an older version, we unzip it first, then pass it through the diff engine.
      • one design consideration here would be to use many tables -- perhaps one translation table per language. Or, one table to contain the 'latest' of everything and one table per language for the gzipped older versions.