fail if org file contains UTF-8 characters
If the org file contains ascii characters only, orgstat works fine. If the file is encoded as utf-8 because I use Chinese characters, it fails.
The log looks like: (journal.org contains Chinese characters and the file is saved as utf-8).
[Debug] [2019-04-02 02:20:38.95 UTC] Config:
OrgStatConfig {confScopes = [ConfScope {csName = "default", csPaths = "/Users/han/Dropbox/Org-mode/ideas.org" :| ["/Users/han/Dropbox/Org-mode/journals.org"]}], confReports = [ConfReport {crName = "prevMonth", crScope = "default", crRange = ConfBlockMonth 1, crModifiers = []}], confOutputs = [ConfOutput {coType = TimelineOutput {toParams = TimelineParams {_tpColorSalt = 0, _tpLegend = True, _tpTopDay = 5, _tpColumnWidth = 1.0, _tpColumnHeight = 1.0, _tpBackground = Data.Colour.SRGB.Linear.rgb 1.0 1.0 1.0}, toReport = "prevMonth"}, coName = "curWeekFullTimeline"}], confTimelineParams = TimelineParams {_tpColorSalt = 3, _tpLegend = True, _tpTopDay = 8, _tpColumnWidth = 1.2, _tpColumnHeight = 1.1, _tpBackground = Data.Colour.SRGB.Linear.rgb 1.0 0.0 0.4019777798321958}, confTodoKeywords = ["TODO","STARTED","WAITING","DONE","CANCELED"], confOutputDir = "/Users/han/Dropbox/Org-mode/orgstat/reports/"}
[Info] [2019-04-02 02:20:38.95 UTC] Processing output curWeekFullTimeline
[Debug] [2019-04-02 02:20:38.95 UTC] Reading org file /Users/han/Dropbox/Org-mode/ideas.org
[Debug] [2019-04-02 02:20:38.98 UTC] Reading org file /Users/han/Dropbox/Org-mode/journals.org
[Error] [2019-04-02 02:20:38.98 UTC] Top level error occured: /Users/han/Dropbox/Org-mode/journals.org: hGetContents: invalid argument (invalid byte sequence)
Is there any solution to this problem? Thanks!!
Hi @philohistoria. This is most likely caused by the locale misconfiguration and doesn't have anything to do with the orgstat in particular. Orgstat doesn't do anything special to the locale settings and just uses the one chosen by the system, so try searching for the hGetContents: invalid argument (invalid byte sequence) in general, it's quite a popular error.
I assume this have been either solved or otherwise is irrelevant and thus should be closed?