Ireal pro copy paste code#

However that does not preclude them from being standards it just means that they could be improved. We leave in a messy world, where even supposedly clearly defined standards often contain crucial ambiguities, flaws, and rival definitions. the myriad of standards relating to email), and finally compare how strictly those are ratified and adhered to by implementations, relative to CSV. You are not disappointing me, because I entirely disagree -) That is a separate discussion which probably does not belong on this forum, but the starting point would be to consider what is a reasonable definition of 'standard', then to consider some other popular standards in the computing world (e.g. The de facto standard defined in RFC 4180 is a good starting point. I'm sorry to disappoint you, but although well-known, there is no such thing as a standard for CSV formatted data files. it's the very well-known CSV (or Comma-Separated Values) format'. (01-19-2016, 10:57 PM)sciurius Wrote: A final remark: the github page reads '. And it allows for additional, optional information without affecting tools that to do not understand this. For example, an index entry could use either 'startpage' and 'endpage', or a more powerful 'pagerange'. With a headings row, it would already be more flexible. (01-19-2016, 10:57 PM)sciurius Wrote: It would be great to employ a more generic data standard for these indices. and any other implementation would find it easy to do the same.

Ireal pro copy paste code#

Oh dear, you seem to have a very dim view of my programming skills -) However you can set your fears to rest my code easily handles this, e.g. This would mean that song 'Airegin' runs from page 17 thru 433, and 'All or nothing at all' will probably crash the program. (01-19-2016, 10:57 PM)sciurius Wrote: Another potential trap of these indices is 'The final page number is optional, because it can often be automatically inferred by the starting page of the next tune. Yes - also easily corrected, and I agree that it obviously needs to be. (01-19-2016, 10:57 PM)sciurius Wrote: Also, there's no provision for information like key, composer, artist. '5-8,10,9,11-' would mean the same as above but with pages 9 and 10 swapped round and assuming that the song doesn't finish before page 11.'5-' would mean page 5 and all subsequent pages until the next page not claimed by any other song.Very good point, but this is extremely easy to fix! For example we could collapse the page selection into a single field which supports different types of values: If two pages were swapped in your copy of the book -and this happens- this cannot be dealt with. (01-19-2016, 10:57 PM)sciurius Wrote: They contain just a starting and ending page, not page ranges. (01-19-2016, 10:57 PM)sciurius Wrote: However, looking at your CSVs I think they're too limited.Ībsolutely - that's why I asked for feedback in the first place :-) The existing repo is just a prototype. Thanks! And I very much appreciate your useful feedback! (01-19-2016, 10:57 PM)sciurius Wrote: I think that a collective approach towards fakebook indices is very good, and I appreciate you taking initiatives!