Merge pull request #510 from radarhere/patch-1

Fixed typos
This commit is contained in:
Antonin Descampe 2015-06-16 14:01:53 +02:00
commit da3786d2d1
2 changed files with 3 additions and 3 deletions

2
NEWS
View File

@ -36,7 +36,7 @@ API/ABI modifications: (see abi_compat_report in dev-utils/scripts)
Misc: Misc:
* OpenJPEG is now officialy conformant with JPEG 2000 Part-1 * OpenJPEG is now officially conformant with JPEG 2000 Part-1
and will soon become official reference software at the and will soon become official reference software at the
JPEG committee. JPEG committee.
* Huge amount of bug fixes. See CHANGES for details. * Huge amount of bug fixes. See CHANGES for details.

View File

@ -36,11 +36,11 @@ See [NEWS](https://github.com/uclouvain/openjpeg/blob/master/NEWS) for user visi
## API/ABI ## API/ABI
OpenJPEG strives to provide a stable API/ABI for your applications. As such it OpenJPEG strives to provide a stable API/ABI for your applications. As such it
only exposes a limited subset of its functions. It uses a mecanism of only exposes a limited subset of its functions. It uses a mechanism of
exporting/hiding functions. If you are unsure which functions you can use in exporting/hiding functions. If you are unsure which functions you can use in
your applications, you should compile OpenJPEG using something similar to gcc: your applications, you should compile OpenJPEG using something similar to gcc:
`fvisibility=hidden` compilation flag. `fvisibility=hidden` compilation flag.
See also: http://gcc.gnu.org/wiki/Visibility See also: http://gcc.gnu.org/wiki/Visibility
On windows, MSVC directly supports export/hidding function and as such the only On windows, MSVC directly supports export/hiding function and as such the only
API available is the one supported by OpenJPEG. API available is the one supported by OpenJPEG.