1 ## International Components for Unicode (ICU4J) v64.2
2
3 ### ICU4J License
4
5 COPYRIGHT AND PERMISSION NOTICE (ICU 58 and later)
6
7 Copyright © 1991-2019 Unicode, Inc. All rights reserved.
8 Distributed under the Terms of Use in https://www.unicode.org/copyright.html.
9
10 Permission is hereby granted, free of charge, to any person obtaining
11 a copy of the Unicode data files and any associated documentation
12 (the "Data Files") or Unicode software and any associated documentation
13 (the "Software") to deal in the Data Files or Software
14 without restriction, including without limitation the rights to use,
15 copy, modify, merge, publish, distribute, and/or sell copies of
16 the Data Files or Software, and to permit persons to whom the Data Files
17 or Software are furnished to do so, provided that either
18 (a) this copyright and permission notice appear with all copies
19 of the Data Files or Software, or
20 (b) this copyright and permission notice appear in associated
21 Documentation.
22
23 THE DATA FILES AND SOFTWARE ARE PROVIDED "AS IS", WITHOUT WARRANTY OF
370 ICU uses the public domain data and code derived from Time Zone
371 Database for its time zone support. The ownership of the TZ database
372 is explained in BCP 175: Procedure for Maintaining the Time Zone
373 Database section 7.
374
375 # 7. Database Ownership
376 #
377 # The TZ database itself is not an IETF Contribution or an IETF
378 # document. Rather it is a pre-existing and regularly updated work
379 # that is in the public domain, and is intended to remain in the
380 # public domain. Therefore, BCPs 78 [RFC5378] and 79 [RFC3979] do
381 # not apply to the TZ Database or contributions that individuals make
382 # to it. Should any claims be made and substantiated against the TZ
383 # Database, the organization that is providing the IANA
384 # Considerations defined in this RFC, under the memorandum of
385 # understanding with the IETF, currently ICANN, may act in accordance
386 # with all competent court orders. No ownership claims will be made
387 # by ICANN or the IETF Trust on the database or the code. Any person
388 # making a contribution to the database or code waives all rights to
389 # future claims in that contribution or in the TZ Database.
|
1 ## International Components for Unicode (ICU4J) v64.2
2
3 ### ICU4J License
4 ```
5
6 COPYRIGHT AND PERMISSION NOTICE (ICU 58 and later)
7
8 Copyright © 1991-2019 Unicode, Inc. All rights reserved.
9 Distributed under the Terms of Use in https://www.unicode.org/copyright.html.
10
11 Permission is hereby granted, free of charge, to any person obtaining
12 a copy of the Unicode data files and any associated documentation
13 (the "Data Files") or Unicode software and any associated documentation
14 (the "Software") to deal in the Data Files or Software
15 without restriction, including without limitation the rights to use,
16 copy, modify, merge, publish, distribute, and/or sell copies of
17 the Data Files or Software, and to permit persons to whom the Data Files
18 or Software are furnished to do so, provided that either
19 (a) this copyright and permission notice appear with all copies
20 of the Data Files or Software, or
21 (b) this copyright and permission notice appear in associated
22 Documentation.
23
24 THE DATA FILES AND SOFTWARE ARE PROVIDED "AS IS", WITHOUT WARRANTY OF
371 ICU uses the public domain data and code derived from Time Zone
372 Database for its time zone support. The ownership of the TZ database
373 is explained in BCP 175: Procedure for Maintaining the Time Zone
374 Database section 7.
375
376 # 7. Database Ownership
377 #
378 # The TZ database itself is not an IETF Contribution or an IETF
379 # document. Rather it is a pre-existing and regularly updated work
380 # that is in the public domain, and is intended to remain in the
381 # public domain. Therefore, BCPs 78 [RFC5378] and 79 [RFC3979] do
382 # not apply to the TZ Database or contributions that individuals make
383 # to it. Should any claims be made and substantiated against the TZ
384 # Database, the organization that is providing the IANA
385 # Considerations defined in this RFC, under the memorandum of
386 # understanding with the IETF, currently ICANN, may act in accordance
387 # with all competent court orders. No ownership claims will be made
388 # by ICANN or the IETF Trust on the database or the code. Any person
389 # making a contribution to the database or code waives all rights to
390 # future claims in that contribution or in the TZ Database.
391
392 ```
393
|