Another one of the "questions that came to me while translating":
- many strings (e.g. "branch '%s' is empty") talk about branches and tags 'directly' - many others (e.g. "put a symbolic tag cert on a revision") talk about 'cert branch' and 'cert tag', implying the user to know that every one of those "logical attributes" of a revision is really a digitally signed certificate - some others talk about command line arguments and not their meaning (e.g. "need --branch argument for approval") The UI-wide question is: should the user actually need to know that all trhose data is implemented using certificates? Or should the user better think about them as directly as branches and tags without the need to know their implementation? In both choices, some of the strings better be changed a bit and once this is discussed/decided (*and* I have more free time, i.e. after friday) I volunteer to track the strings down and uniform them. Lapo _______________________________________________ Monotone-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/monotone-devel
