If I have a table which contains a set of ligatures in the 'Default' section so that it is available in all scripts and then I place a similar table which contains a subset of those ligatures in the 'Localisation' section of a country's script does that make the ligatures which were in the default set but were not in the subset unavailable in that country ?
Or put another way if in the default section I have a set of ligatures which contains the fi and ffi ligatures. If I put a localisation in the Turkish script which has the same ligatures except for the fi and ffi ligatures does that mean that the fi and ffi ligatures will not be available in Turkey ?
Open Type Localisation
-
Erwin Denissen
- Moderator
- Posts: 11501
- Joined: Fri Oct 04, 2002 12:41 am
- Location: Bilthoven, The Netherlands
- Contact:
Re: Open Type Localisation
Yes, that is how it will work.PJMiller wrote:If I have a table which contains a set of ligatures in the 'Default' section so that it is available in all scripts and then I place a similar table which contains a subset of those ligatures in the 'Localisation' section of a country's script does that make the ligatures which were in the default set but were not in the subset unavailable in that country ?
Or put another way if in the default section I have a set of ligatures which contains the fi and ffi ligatures. If I put a localisation in the Turkish script which has the same ligatures except for the fi and ffi ligatures does that mean that the fi and ffi ligatures will not be available in Turkey ?
You can test this behavior within Firefox (In FontCreator go to the main menu, click Font -> Test WOFF).
For default behavior set Language to "en" or leave it empty. For Turkish, use "tr".