The @font-face definitions in this proof are for this limited proof only.
These are not intended as templates or bulletproof examples on how these fonts need to be deployed. Please follow best practice or established rules for writing these rules.
For instance, it might be a good idea to shorten the font file names. For support of some older platforms it might be necessary to also send .ttf files. But note that the .ttf files are significantly larger than the .woff and .eot versions. For some more protection it might be a good idea to encode the fonts into base64 hex strings that can be embedded in a single css file.
Version 3.000: initial release
Version 3.001: Changes to the name tables to make the fonts compatible (again) with tools as InDesign.
These are pages showing key characters of the fonts in different sizes.
Oldstyle figures are controlled by the onum feature. This is currently supported in Chrome, Firefox. Not in Safari
Some kerning combinations, in case the browser supports it.
Each font contains a set of arrows.
Rights: By ministerial order of 16 June 2008 (Government Gazette 2008, no. 115), the State of the Netherlands (Ministry of General Affairs) entered a copyright reservation, as referred to in section 15b of the Copyright Act 1912, concerning the use and application of central government's general purpose Rijkslogo and visual identity, including the fonts Rijksoverheid Serif and Rijksoverheid Sans. This reservation does not apply to parties to whom central government has supplied the Rijkslogo and the visual identity for use in carrying out activities or services commissioned by central government. Any use in any form or by any means, electronic, mechanical, photocopying, recording or otherwise is prohibited unless prior written authorisation has been obtained from central government. To obtain authorisation, you should apply to the Government Information Service.