Derick Rethans a écrit : > On Mon, 14 Jul 2008, Andreas Schamberger wrote: > > >> I'm quite busy at the moment but I took the time today to write a quick >> requirements document for a ezlupdate.php script. >> >> Most of the required functionality is already in the script I posted some >> time >> ago. Therefore it shouldn't be too much work to add the rest. >> > > Looks good - I can't really think of something else, but I'm asking some > other folks as well. > One thing I think might be useful is help for the process of updating software versions, introducing new strings and removing some others. It would be handy to have a tool that is "diff" oriented:
- given a set of templates and a translation file, it adds the missing translations strings to the translation file and outputs the list of unused strings - given two translation files, it can add the missing strings from a to b [in "unfinished" mode] and output the list of strings in b which are not in a > >> Are there any design rules for a command line script in ezc? >> I guess a look at existing scripts should be enough (e.g. the >> PersistentObjectDatabaseSchemaTiein)? >> > > Yes, that would work. > > regards, > Derick > > (PS, could you please not top-post replies?) > -- Components mailing list [email protected] http://lists.ez.no/mailman/listinfo/components
