Thanks Jaap. The command successfully printed out a date and time. However, is the calendar.py and datetimetz.py modules included in the Zim package different from the defaults in the python package? Should I be directing python to the Zim modules as opposed to the python defaults? If so, how? I am not sure my "export PYTHONPATH ..." is doing that correctly.
Two potentially relevant insights from debug mode: 1. After opening Zim with "python2.6 ./zim.py -D": "DEBUG: Set XDG_DATA_HOME to /Users/ambrya/.local/share" There is no "XDG" in the above directory. The only files in this directory are: zim/templates/Default.txt zim/templates/Journal.txt 2. After creating a new page: "ERROR: Error in strftime "%A %d %B %Y Traceback (most recent call last): File "/Users/ambrya/source/zim-0.59/zim/templates.py", line 742, in __call__ return string.decode(locale.getpreferredencoding()) LookupError: unknown encoding:" After line 742, there is comment that I don't understand and am not sure is relevant: # strftime returns locale as understood by the C api # unfortunately there is no guarantee we can actually # decode it ... Thoughts? Thanks so much for your help, Jaap. Best, Alex On Thu, Apr 25, 2013 at 2:47 PM, Jaap Karssenberg < jaap.karssenb...@gmail.com> wrote: > On Thu, Apr 25, 2013 at 8:37 PM, Alexander Bryan <amb...@umich.edu> wrote: > > Thanks for your response, Jaap. Yes, but the same issue occurs with daily > > pages only without the "to." I don't think it's a bug with Zim, unless > it's > > a compatibility issue with Macs. My suspicion is the problem lies in how > I > > have installed python and/or Zim such that the strftime command in the > > Default.txt and Journal.txt templates are failing. Not sure how to test > that > > though—I've never used python until 2 days ago! > > You can do a quick check by running the following command in a terminal: > > $ python -c "import datetime; print > datetime.datetime.now().strftime('%c')" > > If it prints a date to the terminal, the python module is working fine. > > You can also try running "zim -D" to check for error logging in the > debug output. > > Regards, > > Jaap >
_______________________________________________ Mailing list: https://launchpad.net/~zim-wiki Post to : zim-wiki@lists.launchpad.net Unsubscribe : https://launchpad.net/~zim-wiki More help : https://help.launchpad.net/ListHelp