diff options
| author | Rob Landley <rob@landley.net> | 2005-10-31 23:52:02 +0000 |
|---|---|---|
| committer | Rob Landley <rob@landley.net> | 2005-10-31 23:52:02 +0000 |
| commit | dbc608b5687ebe1b828f921c70573280d6c3e313 (patch) | |
| tree | 0df0bcda4b5c6014f8b20d775b766cd6cde0c1b7 /TODO | |
| parent | c63fe9137fbdf83794d1ea5a3e000238816cba94 (diff) | |
| download | busybox-w32-dbc608b5687ebe1b828f921c70573280d6c3e313.tar.gz busybox-w32-dbc608b5687ebe1b828f921c70573280d6c3e313.tar.bz2 busybox-w32-dbc608b5687ebe1b828f921c70573280d6c3e313.zip | |
We've got fuser, fix some typos, and move Vodz's comment about UTF8 into
a new "internationalization" section, with some related concerns.
Diffstat (limited to 'TODO')
| -rw-r--r-- | TODO | 32 |
1 files changed, 25 insertions, 7 deletions
| @@ -11,19 +11,14 @@ sh | |||
| 11 | work all that well (especially not in a chroot environment), due to apps not | 11 | work all that well (especially not in a chroot environment), due to apps not |
| 12 | being reentrant. Unifying the various shells and figuring out a configurable | 12 | being reentrant. Unifying the various shells and figuring out a configurable |
| 13 | way of adding the minimal set of bash features a given script uses is a big | 13 | way of adding the minimal set of bash features a given script uses is a big |
| 14 | job, but it be a big improvement. | 14 | job, but it would be a big improvement. |
| 15 | 15 | ||
| 16 | Note: Rob Landley (rob@landley.net) is working on this one, but very slowly... | 16 | Note: Rob Landley (rob@landley.net) is working on this one, but very slowly... |
| 17 | |||
| 18 | Support unicode for cmdedit. | ||
| 19 | --- | 17 | --- |
| 20 | diff | 18 | diff |
| 21 | We should have a diff -u command. We have patch, we should have diff | 19 | We should have a diff -u command. We have patch, we should have diff |
| 22 | (we only need to support unified diffs though). | 20 | (we only need to support unified diffs though). |
| 23 | --- | 21 | --- |
| 24 | fuser | ||
| 25 | Would be nice. The basic susv3 options, plus fuser -k. | ||
| 26 | --- | ||
| 27 | patch | 22 | patch |
| 28 | Should have simple fuzz factor support to apply patches at an offset which | 23 | Should have simple fuzz factor support to apply patches at an offset which |
| 29 | shouldn't take up too much space. | 24 | shouldn't take up too much space. |
| @@ -51,7 +46,30 @@ Do a SUSv3 audit | |||
| 51 | 46 | ||
| 52 | Even better would be some kind of automated compliance test harness that | 47 | Even better would be some kind of automated compliance test harness that |
| 53 | exercises each command line option and the various corner cases. | 48 | exercises each command line option and the various corner cases. |
| 54 | -- | 49 | --- |
| 50 | Internationalization | ||
| 51 | How much internationalization should we do? | ||
| 52 | |||
| 53 | The low hanging fruit is UTF-8 character set support. We should do this. | ||
| 54 | (Vodz pointed out the shell's cmdedit as needing work here. What else?) | ||
| 55 | |||
| 56 | We also have lots of hardwired english text messages. Consolidating this | ||
| 57 | into some kind of message table not only makes translation easier, but | ||
| 58 | also allows us to consolidate redundant (or close) strings. | ||
| 59 | |||
| 60 | We probably don't want to be bloated with locale support. (Not unless we can | ||
| 61 | cleanly export it from our underlying C library without having to concern | ||
| 62 | ourselves with it directly. Perhaps a few specific things like a config | ||
| 63 | option for "date" are low hanging fruit here?) | ||
| 64 | |||
| 65 | What level should things happen at? How much do we care about | ||
| 66 | internationalizing the text console when X11 and xterms are so much better | ||
| 67 | at it? (There's some infrastructure here we don't implement: The | ||
| 68 | "unicode_start" and "unicode_stop" shell scripts need "vt-is-UTF8" and a | ||
| 69 | --unicode option to loadkeys. That implies a real loadkeys/dumpkeys | ||
| 70 | implementation to replace loadkmap/dumpkmap. Plus messing with console font | ||
| 71 | loading. Is it worth it, or do we just say "use X"?) | ||
| 72 | --- | ||
| 55 | Unify archivers | 73 | Unify archivers |
| 56 | Lots of archivers have the same general infrastructure. The directory | 74 | Lots of archivers have the same general infrastructure. The directory |
| 57 | traversal code should be factored out, and the guts of each archiver could | 75 | traversal code should be factored out, and the guts of each archiver could |