libhdate, hcal and hdate Activity
C library for Hebrew dates / times of day / solar times
Brought to you by:
boruch-baum,
kzamir
Activity for libhdate, hcal and hdate
-
Boruch Baum posted a comment on a wiki page
Done. Thank you. Fixed. The 'master' branch had been renamed to 'main'. Also, FYI, the repository is also available on github (and just this second I'm not certain whether the github version is ahead a few commits of this sourceforge version, and I have to rush on something else)
-
Home
-
Cherniavsky Beni posted a comment on a wiki page
Need to update to git clone --branch=master
-
hcal: refactor parsing of config file
-
hcal: bugfix identification of holidays (bad pointer)
-
hcal: refactor parsing of user menus
-
hcal: move in-line documentation to front of file
-
hcal.c; refactor initialization of option_list struct
-
hcal: refactor sections in main
-
hcal: refactor final sections in main
-
support.h: remove unused definition BEST_TIMEZONE
-
hdate.c: refactor main: initialize_option_list_struct
-
hdate.c: refactor main: parse_config_file
-
hdate.c: refactor main: parse_command_line
-
hdate.c: refactor main: parse_user_menu_selection
-
custom_days.c: resolve compiler warning (unused variable)
-
timezone_functions.c: resolve compiler warnings (needs testing)
-
Restore a blank README (kludge to get make to work)
-
Makefile.am: rename README to README.md
-
hdate.c: refactor remainder of parsing
-
hcal, hdate: refactor (mainly remove needless parentheses)
-
hcal: bugfix three-month bidi first line padding
-
README: change to github-style markdown format README.md
-
hcal: disallow (broken) combination --html --three-month
-
custom_days: remove DEBUG compiler variable
-
hcal: bugfix three-month bidi display in correct month sequence
-
custom_days.c: use compile directive DEBUG for day tests
-
hcal, hdate: parse config file case-insensitively
-
refactor: footnotes, option 'separator', 'print_' function names
-
option: --tmux-bidi for display kludges
-
Changelog: catch-up neglected commits
-
hcal: improve some bidi corner cases, minor refactor
-
hcal: refactor selected integers to boolean
-
hcal: mlterm support: add to config file options
-
new option: --mlterm for strict proper bidi with no kludges
-
remove option: --spacing
-
hcal: option --border: documentation update
-
bugfix: alignment of border for Adar II in three-month display
-
sanity refactor: spacing v separator v border v ...
-
hcal: autodetect mlterm terminal emulator
-
hcal: mlterm fixes for three-month option
-
hcal: more alignment kludges for non-mlterms
-
hcal: man page: mlterm support; alignment bugs in 3-month view
-
custom_days: uniform symbol for Israeli national days
-
Update copyright
-
hcal: padding for Hebrew trailing days of month (last calendar line)
-
padding for three-month Hebrew trailing days of month
-
man pages: align options, improve holiday/custom day description
-
zdump3.c: use glibc extensions to tm struct; remove placeholder data
-
configure/make: corrections and fixes
-
fixes timezone handling code
-
Merge branch 'master' of ssh://git.code.sf.net/p/libhdate/git
-
fix timezone-handling logic
-
hdate: fix options --quiet-{alerts,gregorian,descriptions}
-
hdate: remove unused parameters from internal functions
-
hdate: fix options --quiet-{alerts,gregorian,descriptions}
-
Set short format of Shabbat to ז instead of ש
-
hdate: fixes to option -oo omer-counting
-
configure/make: corrections and fixes
-
fixes timezone handling code
-
Minor updates to colophons and urls
-
fix timezone-handling logic
-
Shmu26 posted a comment on discussion Help
Thanks for the heads up about the sunset time changing accordingly. I did notice that inexorable side-effect.
-
On 2021-02-21 18:12, Shmu26 wrote: Yeah, it's all about altitude and taking the mountains on the horizon into account. The times they use in the minyan are based on actual sightings of the sunrise, which of course depends a lot on where the sighter was standing. So your last idea, to choose a longitude that gives me the result I want, sounds right. Uh, not so fast... In the situation you describe, if you adjust the computer program's longitude configuration to account for the sunrise obstruction,...
-
Yeah, it's all about altitude and taking the mountains on the horizon into account. The times they use in the minyan are based on actual sightings of the sunrise, which of course depends a lot on where the sighter was standing. So your last idea, to choose a longitude that gives me the result I want, sounds right. It will be interesting to see if it stays accurate as the seasons change. Thanks!
-
On 2021-02-21 14:43, Shmu26 wrote: My minyan thinks that the sun rises 8 minutes earlier than the time posted by hdate for my locale (Jerusalem, Israel). You minyan could be correct for its exact point on Earth and the decision of your local posek should always be respected. The computer program doesn't guess exactly where within J-m you are, or whether your location has its horizon sunrise/sunset obstructed by some hill/mountain; there will be variation accordingly. Also be aware that your posek...
-
So here comes a perhaps unreasonable question: Can I configure the sunrise time to display as eight minutes earlier than the standard output? My minyan thinks that the sun rises 8 minutes earlier than the time posted by hdate for my locale (Jerusalem, Israel). For reference, my hdaterc file says as follows. I think this is right for Jerusalem. LATITUDE=31 LONGITUDE=34 # TIMEZONE may may be in decimal format or in the form degrees[:minutes] # with the characters :'" as possible delimiters. TIMEZO...
-
Yup, did that. It is explained very nicely in the config file, and I think the warning also displays in the terminal until it is configured. Thanks for the great app!
-
On 2021-02-17 09:48, Shmu26 wrote: You are right. It's there. To get sunrise and sunset times for tomorrow, the 18th of February 2021, I did hdate 18 2 2021 -s --sun and it worked perfectly. Great. Now just be certain that you're getting data for the correct location on Earth. If the program hasn't correctly guessed your location, you need to explicitly define it. Again, see the documentation for details. -- hkp://keys.gnupg.net CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0
-
You are right. It's there. To get sunrise and sunset times for tomorrow, the 18th of February 2021, I did hdate 18 2 2021 -s --sun and it worked perfectly.
-
On 2021-02-17 08:46, Shmuel Globus wrote: Let's say I want to get sunrise time or other output for tomorrow, or for a certain date. how to do that in linux terminal? Take a look at the program's documentation for all of its features. If you feel that the feature you're asking for isn't clearly described, then let me know. You had me worried for a bit, but I double-checked and your question is very clearly answered both by 'man hdate' and 'hdate --help'. Kol tuv, -- hkp://keys.gnupg.net CA45 09B5...
-
Let's say I want to get sunrise time or other output for tomorrow, or for a certain date. how to do that in linux terminal?
-
The example in "USE" file is totally broken.
-
Thank you, Alex. An update to the USE file has been pushed to the git master branch
-
Update very old (and now broken example)
-
Alex Hitech created ticket #2
The example in "USE" file is totally broken.
-
Remove file INSTALL from package
-
autoconf fix-up attempt ; drop ruby binding
-
hcal, local_functions: initialize variables correctly
-
hcal/hdate makefile corrections and tweaks
-
create .gitignore
-
bugfix: hcal print bidi footnote elements in correct sequence
-
Home
-
Home
-
Home
-
Home
-
Home
-
Home
-
Home
-
Home
-
Home
-
bugfix: bidi print correct sequence
-
hdate.c: coding style changes
-
hcal.c: coding style changes
-
bugfix: segfault for option '-s'
-
bugfix: print shabbat name when using bidi (option '-sb')
-
Yaacov zamir committed [d5d55b]
change hdate struct
-
*** empty log message ***
-
Root committed [9283e4]
initial checkin
-
more code cleanups
1 >