Ticket #1671 (accepted defect) — at Version 3
i18n_checktimelength may vary depending on the season
Reported by: | sfionov | Owned by: | zaytsev |
---|---|---|---|
Priority: | major | Milestone: | 4.7.2 |
Component: | mc-core | Version: | master |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Branch state: | Votes for changeset: | andrew_b |
Description (last modified by andrew_b) (diff)
On some systems i18n_checktimelength may vary not only depending on locale but also on the current month.
For example, with Russian locale on Solaris, 9th month %b is "сент.", 10th month is "окт.".
So, this function returns 14 in September, and 13 in October. September dates are cut in October, and "ент." is displayed.
Change History
Changed 15 years ago by sfionov
- Attachment i18n-checktimelength.patch added
comment:1 Changed 15 years ago by sfionov
Just to clarify, width of "MTime" column is i18n_checktimelength result.
comment:2 Changed 15 years ago by zaytsev
- Status changed from new to accepted
- Owner set to zaytsev
- Version changed from 4.7.0-pre3 to master
- severity changed from no branch to on review
Branch: 1671_i18n_checktimelength (parent: master)
Changeset: 28eda668032a73e2a433d84b23b8e2a92d04663f
Please review and vote! With the regards to cache, I am not sure about the obscure corner cases e.g. whether the value of str_term_width1 is still valid when the terminal encoding has been modified on fly (I think it still is).
Thanks!
Cycle around all months to determine maximum time string length.