You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I am the author of taranis a weather application for Pocketbook e-readers.
The English in the GetLangTime() docstring isn't very precise... It would be nice to have an example of this function usage. Having dates printed in current language is a must have for serious applications...
/** * localized value by key should be in part of "strftime" format * return localized time in variable "buf" or empty string if "key" not found * return value "0" - ok * return value "-1" - no key found (key may be a format) * return value "-2" - not found any replacement of time format * return value "-3" - result not fit in buffer * return value "-100" - not supported format * Notice: function try to add "_12" to key if AM/PM time format turned on in settings * Requirments for keys: * "@TimeFormat" + <key_words1> + <options> + <key_words2> + <am.pm> * <options>: * "Date"/"SDate" - month name and month day number / short month name and month day number (ex. January/Jan) * "Time" - hours and minutes * "WDay"/"SWDay" - Week day name / short week day name (ex. Monday/Mon) * "Year" - year number * others - other options like "Seconds", "Month", "SMonth", "SMDay", etc * <key_words1>, <key_words2> - optional if need for detalize key * <am.pm> - if AM/PM time format turned on in settings, auto add "_12" in function.*/intGetLangTime(char *buf, int size, constchar *key, structtm *t);
The text was updated successfully, but these errors were encountered:
Hello, I am the author of taranis a weather application for Pocketbook e-readers.
The English in the
GetLangTime()
docstring isn't very precise... It would be nice to have an example of this function usage. Having dates printed in current language is a must have for serious applications...An example of what I've tried: orontee/taranis#46 (comment)
Thanks!
The text was updated successfully, but these errors were encountered: