CRxTRDude

Okay, I'll divide this onto sections, starting with: ### Introduction All of them use XML 1.0 PList 1.0 Specs. Date is formatted like this, with time formatted in Zulu: (YYYY-MM-DD)T(HH:MM:SS)Z...

Key: Activity Value: `` ``` Set in Day One, determined also through 'motion activity'. ``` Key: Creation Date Value: `` ``` Date the entry is created ```

Key: Creator Value: `` ``` Sets the application used to create the DOENTRY ``` [Start of Creator dict] Key: Device Agent Value: `` ``` The device the application is on...

Key: Entry Text Value: `` ``` The main body of the document formatted in Markdown. In Journaley, MarkdownDeep is used to parse it. MarkdownDeep combines features found in Markdown as...

Key: Location Value: `` The location of the device that the DOENTRY was created/generated Can be set in Day One [Start of Location Dict] Key: Administrative Area Value: `` ```...

Key: Starred Value: `` or `` ``` Is this entry starred/bookmarked? For the starred category in Day One. ``` Key: Tags Value: `` ``` Array of tags. When present, the...

Key: Weather Value: Dict ``` Weather information tagged in the entry. ``` [Start of Weather Dict] Key: Celsius Value: String ``` Temperature in celsius (metric) ``` Key: Description Value: String...

That's got to be all what is currently in an XML file of an entry with everything turned on. If not specified, the Weather dict and Location Dict could be...

BTW, for the time zones, we could implement that, using [Noda Time](http://nodatime.org/), which has a Nuget version by the way, and this thing that I found in [Stack Overflow](http://stackoverflow.com/questions/17348807/how-to-translate-between-windows-and-iana-time-zones)

I'll repost this as reference: > I understand why you did that, but I still think it was incorrect for a few reasons. > > First, it wouldn't necessarily match...