collect requests for the upcomming FITS standard

[ritchieGitHub]

This issue is to collect a list of notes to the upcomming standard and the things we wan't to propose there.

• the long string adaptions like making room for longer comments by splitiing up strings.
• long values and comments for non string values (more precission by using BigDecimal / BigInteger)

@TomMcGlynn any Ideas what to bring in?

[TomMcGlynn]

There are several issues with the various proposals that are being
reviewed that would have impact on the library and I plan to make a
number of comments when I get back to work on Thursday. My initial
impression is that at least one and possible two of the conventions
should not be adopted into the standard, but I've not had a chance to
consider them particularly in the light of our library. Why do these
things come out when I'm on vacation!

Richard van Nieuwenhoven wrote:

This issue is to collect a list of notes to the upcomming standard and
the things we wan't to propose there.

• the long string adaptions like making room for longer comments by
  splitiing up strings.
• long values and comments for non string values (more precission by
  using BigDecimal / BigInteger)

@TomMcGlynn https://github.com/TomMcGlynn any Ideas what to bring in?

—
Reply to this email directly or view it on GitHub
#33.

[ritchieGitHub]

just the links the current discussions:

https://listmgr.nrao.edu/pipermail/fitsbits/2015-June/thread.html
https://listmgr.nrao.edu/pipermail/fitsbits/2015-July/thread.html

[attipaci]

I assume this issue can be closed. If not, feel free to reopen it again.

On a related note, version 1.16 adds support for long comments with long strings (see #173).