Corrected the A+B+C.zip file naming convention #8
Conversation
README.md
Outdated
| **Resulting transaction file** | ||
| Because `date in GMT of the oldest` < `date in GMT of the youngest`, | ||
| {date in GMT}={X}+{Y}+{Z}.zip | ||
| Resulting transaction file Based on alphabetical order, say if `X < Y`, then: {date in GMT}={X}+{Y}+{Z}.zip |
There was a problem hiding this comment.
Were you able to confirm through experiment that is indeed the case?
There was a problem hiding this comment.
Yes,
date in GMT of the oldest < date in GMT of the youngest OR
date in GMT of the oldest > date in GMT of the youngest
has no effect on resulting file name
README.md
Outdated
| Because `date in GMT of the oldest` < `date in GMT of the youngest`, | ||
| {date in GMT}={X}+{Y}+{Z}.zip | ||
| Resulting transaction file Based on alphabetical order, say if `X < Y`, then: {date in GMT}={X}+{Y}+{Z}.zip | ||
| Hence, in all P+Q+R.zip type filenames, alphabetically `P < Q` |
There was a problem hiding this comment.
+Hence, in all P+Q+R.zip type filenames, alphabetically
P < Q
This is an observation that can be made on any OmniFocus.ofocus file: https://www.google.co.in/search?biw=1670&bih=1320&q=inurl:OmniFocus.ofocus/&oq=inurl:OmniFocus.ofocus/&gs_l=serp.3...7590.7590.0.8081.1.1.0.0.0.0.139.139.0j1.1.0....0...1c.1.64.serp..0.0.0.UGJvzosBWME&gws_rd=cr&ei=1Z71V8WkLMPtvASAhJeQBQ
There was a problem hiding this comment.
I've only found one example going through those links, but I'll assume it's a better assumption than the initial one.
However, what I was saying is that this sentence is incomplete (furthermore, it appears to repeat what was said just above).
There was a problem hiding this comment.
Removed the duplicate now
but, why incomplete?
| Resulting transaction file Based on alphabetical order, say if `X < Y`, then: {date in GMT}={X}+{Y}+{Z}.zip | ||
| Hence, in all P+Q+R.zip type filenames, alphabetically `P < Q` | ||
|
|
||
| Any transaction file generated next will henceforth be named {date in GMT}={Z}+{C}.zip, where Z is the randomId generated for the resulting transaction file. |
There was a problem hiding this comment.
This is a duplicate of the line just below.
2 participants
Fixes #7