I looked for the white spaces in the manifest values. There are some bug
reports and changes in the specification. The history is interesting.
- Version 4.0.1, 1.4.2,
"Spaces (’ ’ \u0020) are ignored unless specifically noted." - seems
that the white spaces are allowed and igrored
- Version 4.1, 1.3.2,
That sentence is missing. Furthermore, there is:
"Whitespaces in the previous definitions are only allowed when the
values are quoted."
and
"Any value that contains a space, a comma, semi-colon, colon, equal sign
or any other character that is part of a terminal in the grammar must be
quoted."
Does the second quotation contain the first one?
I think that the nice sentence in the 4.0.1 should be returned.
Am I missing something? Any comments?
Thanks in advance, Evgeni!
--
-----------------------------------------------------------------------------------
Evgeni Grigorov . Software Engineer/Development Tools
ProSyst Software GmbH
Tel. +359 2 953 05 88 . Fax +359 2 953 26 17
Mobile +359 878 17 41 51
http://www.prosyst.com . e.grigo...@prosyst.com
-----------------------------------------------------------------------------------
stay in touch with your product.
-----------------------------------------------------------------------------------
_______________________________________________
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev
