Michael Meskes dixit: >> >Could you please elaborate what (n)cal miss? "ncal -w" does give you >> >week numbers >> >> But which ones? American? German? ISO? (Turns out the latter two are > >Depends on the locale you use.
The locale doesn’t contain enough information to calculate calendar weeks: https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap07.html There’s neither a data field for the first day of the week, nor one for the various ways to calculate a calendar week. >No idea what you are saying, sorry, please elaborate. There are multiple ways to calculate calendar weeks, see above. >> I understand if you find this too bothersome to do in Debian for >> such a (corner?) case, but that is why this is of wishlist severity >> ;) > >Na, the problem is understanding what's missing, or wrong. :) I think that while ncal may be a usable provider for cal, it’s not suitable in all situations whereas the other implementation has its benefit in some of these (but on the other hand lacking in cases ncal supports) so we maybe should just have both? Currently I just install kwal and call it as kwal, but with ncal now being its separate package I just don’t need to install it any more. This leaves cal(1) unprovided though so I came to consider alternatives for it. Of course I could locally symlink it, but that doesn’t scale, and Conflicts isn’t useful either so I can’t add the symlinks to the kwal package. In the end I just need a reliable way to get at German (= ISO) calendar weeks, for use in business environments, and found that, rather than having to write code myself, I could use OpenBSD’s cal, which has an option for specifically this (although only for years 1753‥9999, same as ncal). bye, //mirabilos -- (gnutls can also be used, but if you are compiling lynx for your own use, there is no reason to consider using that package) -- Thomas E. Dickey on the Lynx mailing list, about OpenSSL
