Start. Prepare glyph data. Create metadata file. Create script file. Create source file. Copyright (c) 2000-2011 by George Williams. Executable based on sources from 23:14 GMT 25-Feb-2011-ML. Library based on sources from 13:48 GMT 22-Feb-2011. 0u014A 0u014B 0u0186 0u018F 0u01A9 0u01B1 0u01B7 0u0245 0u0251 0u0252 0u0254 0u0259 0u025C 0u0261 0u026A 0u0283 0u028A 0u028C 0u0292 0u2C6D 0u2C70 0u0398 0u03B8 0u0041 There already exists a 'cvt' table, perhaps legacy. FontForge can use it, but can't make any assumptions on values stored there, so generated instructions will be of lower quality. If legacy hinting is to be scrapped, it is suggested to clear the `cvt` and repeat autoinstructing. There exists a 'prep' code incompatible with FontForge's. It can't be guaranteed it will work well. It is suggested to allow FontForge to insert its code and then append user's own. 0u0042 0u0044 0u0045 0u0046 0u0048 0u0049 There already exists a 'cvt' table, perhaps legacy. FontForge can use it, but can't make any assumptions on values stored there, so generated instructions will be of lower quality. If legacy hinting is to be scrapped, it is suggested to clear the `cvt` and repeat autoinstructing. There exists a 'prep' code incompatible with FontForge's. It can't be guaranteed it will work well. It is suggested to allow FontForge to insert its code and then append user's own. 0u004A There already exists a 'cvt' table, perhaps legacy. FontForge can use it, but can't make any assumptions on values stored there, so generated instructions will be of lower quality. If legacy hinting is to be scrapped, it is suggested to clear the `cvt` and repeat autoinstructing. There exists a 'prep' code incompatible with FontForge's. It can't be guaranteed it will work well. It is suggested to allow FontForge to insert its code and then append user's own. 0u004B There already exists a 'cvt' table, perhaps legacy. FontForge can use it, but can't make any assumptions on values stored there, so generated instructions will be of lower quality. If legacy hinting is to be scrapped, it is suggested to clear the `cvt` and repeat autoinstructing. There exists a 'prep' code incompatible with FontForge's. It can't be guaranteed it will work well. It is suggested to allow FontForge to insert its code and then append user's own. 0u004C There already exists a 'cvt' table, perhaps legacy. FontForge can use it, but can't make any assumptions on values stored there, so generated instructions will be of lower quality. If legacy hinting is to be scrapped, it is suggested to clear the `cvt` and repeat autoinstructing. There exists a 'prep' code incompatible with FontForge's. It can't be guaranteed it will work well. It is suggested to allow FontForge to insert its code and then append user's own. 0u004D There already exists a 'cvt' table, perhaps legacy. FontForge can use it, but can't make any assumptions on values stored there, so generated instructions will be of lower quality. If legacy hinting is to be scrapped, it is suggested to clear the `cvt` and repeat autoinstructing. There exists a 'prep' code incompatible with FontForge's. It can't be guaranteed it will work well. It is suggested to allow FontForge to insert its code and then append user's own. 0u004E There already exists a 'cvt' table, perhaps legacy. FontForge can use it, but can't make any assumptions on values stored there, so generated instructions will be of lower quality. If legacy hinting is to be scrapped, it is suggested to clear the `cvt` and repeat autoinstructing. There exists a 'prep' code incompatible with FontForge's. It can't be guaranteed it will work well. It is suggested to allow FontForge to insert its code and then append user's own. 0u4E00 There already exists a 'cvt' table, perhaps legacy. FontForge can use it, but can't make any assumptions on values stored there, so generated instructions will be of lower quality. If legacy hinting is to be scrapped, it is suggested to clear the `cvt` and repeat autoinstructing. There exists a 'prep' code incompatible with FontForge's. It can't be guaranteed it will work well. It is suggested to allow FontForge to insert its code and then append user's own. 0u004F There already exists a 'cvt' table, perhaps legacy. FontForge can use it, but can't make any assumptions on values stored there, so generated instructions will be of lower quality. If legacy hinting is to be scrapped, it is suggested to clear the `cvt` and repeat autoinstructing. There exists a 'prep' code incompatible with FontForge's. It can't be guaranteed it will work well. It is suggested to allow FontForge to insert its code and then append user's own. 0u0050 There already exists a 'cvt' table, perhaps legacy. FontForge can use it, but can't make any assumptions on values stored there, so generated instructions will be of lower quality. If legacy hinting is to be scrapped, it is suggested to clear the `cvt` and repeat autoinstructing. There exists a 'prep' code incompatible with FontForge's. It can't be guaranteed it will work well. It is suggested to allow FontForge to insert its code and then append user's own. 0u0052 There already exists a 'cvt' table, perhaps legacy. FontForge can use it, but can't make any assumptions on values stored there, so generated instructions will be of lower quality. If legacy hinting is to be scrapped, it is suggested to clear the `cvt` and repeat autoinstructing. There exists a 'prep' code incompatible with FontForge's. It can't be guaranteed it will work well. It is suggested to allow FontForge to insert its code and then append user's own. 0u0053 There already exists a 'cvt' table, perhaps legacy. FontForge can use it, but can't make any assumptions on values stored there, so generated instructions will be of lower quality. If legacy hinting is to be scrapped, it is suggested to clear the `cvt` and repeat autoinstructing. There exists a 'prep' code incompatible with FontForge's. It can't be guaranteed it will work well. It is suggested to allow FontForge to insert its code and then append user's own. 0u0054 There already exists a 'cvt' table, perhaps legacy. FontForge can use it, but can't make any assumptions on values stored there, so generated instructions will be of lower quality. If legacy hinting is to be scrapped, it is suggested to clear the `cvt` and repeat autoinstructing. There exists a 'prep' code incompatible with FontForge's. It can't be guaranteed it will work well. It is suggested to allow FontForge to insert its code and then append user's own. 0u0055 There already exists a 'cvt' table, perhaps legacy. FontForge can use it, but can't make any assumptions on values stored there, so generated instructions will be of lower quality. If legacy hinting is to be scrapped, it is suggested to clear the `cvt` and repeat autoinstructing. There exists a 'prep' code incompatible with FontForge's. It can't be guaranteed it will work well. It is suggested to allow FontForge to insert its code and then append user's own. 0u0056 There already exists a 'cvt' table, perhaps legacy. FontForge can use it, but can't make any assumptions on values stored there, so generated instructions will be of lower quality. If legacy hinting is to be scrapped, it is suggested to clear the `cvt` and repeat autoinstructing. There exists a 'prep' code incompatible with FontForge's. It can't be guaranteed it will work well. It is suggested to allow FontForge to insert its code and then append user's own. 0u0057 There already exists a 'cvt' table, perhaps legacy. FontForge can use it, but can't make any assumptions on values stored there, so generated instructions will be of lower quality. If legacy hinting is to be scrapped, it is suggested to clear the `cvt` and repeat autoinstructing. There exists a 'prep' code incompatible with FontForge's. It can't be guaranteed it will work well. It is suggested to allow FontForge to insert its code and then append user's own. 0u005A There already exists a 'cvt' table, perhaps legacy. FontForge can use it, but can't make any assumptions on values stored there, so generated instructions will be of lower quality. If legacy hinting is to be scrapped, it is suggested to clear the `cvt` and repeat autoinstructing. There exists a 'prep' code incompatible with FontForge's. It can't be guaranteed it will work well. It is suggested to allow FontForge to insert its code and then append user's own. 0u0061 There already exists a 'cvt' table, perhaps legacy. FontForge can use it, but can't make any assumptions on values stored there, so generated instructions will be of lower quality. If legacy hinting is to be scrapped, it is suggested to clear the `cvt` and repeat autoinstructing. There exists a 'prep' code incompatible with FontForge's. It can't be guaranteed it will work well. It is suggested to allow FontForge to insert its code and then append user's own. 0u0062 There already exists a 'cvt' table, perhaps legacy. FontForge can use it, but can't make any assumptions on values stored there, so generated instructions will be of lower quality. If legacy hinting is to be scrapped, it is suggested to clear the `cvt` and repeat autoinstructing. There exists a 'prep' code incompatible with FontForge's. It can't be guaranteed it will work well. It is suggested to allow FontForge to insert its code and then append user's own. 0u0064 There already exists a 'cvt' table, perhaps legacy. FontForge can use it, but can't make any assumptions on values stored there, so generated instructions will be of lower quality. If legacy hinting is to be scrapped, it is suggested to clear the `cvt` and repeat autoinstructing. There exists a 'prep' code incompatible with FontForge's. It can't be guaranteed it will work well. It is suggested to allow FontForge to insert its code and then append user's own. 0u0065 There already exists a 'cvt' table, perhaps legacy. FontForge can use it, but can't make any assumptions on values stored there, so generated instructions will be of lower quality. If legacy hinting is to be scrapped, it is suggested to clear the `cvt` and repeat autoinstructing. There exists a 'prep' code incompatible with FontForge's. It can't be guaranteed it will work well. It is suggested to allow FontForge to insert its code and then append user's own. 0u0066 There already exists a 'cvt' table, perhaps legacy. FontForge can use it, but can't make any assumptions on values stored there, so generated instructions will be of lower quality. If legacy hinting is to be scrapped, it is suggested to clear the `cvt` and repeat autoinstructing. There exists a 'prep' code incompatible with FontForge's. It can't be guaranteed it will work well. It is suggested to allow FontForge to insert its code and then append user's own. 0u0068 There already exists a 'cvt' table, perhaps legacy. FontForge can use it, but can't make any assumptions on values stored there, so generated instructions will be of lower quality. If legacy hinting is to be scrapped, it is suggested to clear the `cvt` and repeat autoinstructing. There exists a 'prep' code incompatible with FontForge's. It can't be guaranteed it will work well. It is suggested to allow FontForge to insert its code and then append user's own. 0u0069 There already exists a 'cvt' table, perhaps legacy. FontForge can use it, but can't make any assumptions on values stored there, so generated instructions will be of lower quality. If legacy hinting is to be scrapped, it is suggested to clear the `cvt` and repeat autoinstructing. There exists a 'prep' code incompatible with FontForge's. It can't be guaranteed it will work well. It is suggested to allow FontForge to insert its code and then append user's own. 0u006A There already exists a 'cvt' table, perhaps legacy. FontForge can use it, but can't make any assumptions on values stored there, so generated instructions will be of lower quality. If legacy hinting is to be scrapped, it is suggested to clear the `cvt` and repeat autoinstructing. There exists a 'prep' code incompatible with FontForge's. It can't be guaranteed it will work well. It is suggested to allow FontForge to insert its code and then append user's own. 0u006B There already exists a 'cvt' table, perhaps legacy. FontForge can use it, but can't make any assumptions on values stored there, so generated instructions will be of lower quality. If legacy hinting is to be scrapped, it is suggested to clear the `cvt` and repeat autoinstructing. There exists a 'prep' code incompatible with FontForge's. It can't be guaranteed it will work well. It is suggested to allow FontForge to insert its code and then append user's own. 0u006C There already exists a 'cvt' table, perhaps legacy. FontForge can use it, but can't make any assumptions on values stored there, so generated instructions will be of lower quality. If legacy hinting is to be scrapped, it is suggested to clear the `cvt` and repeat autoinstructing. There exists a 'prep' code incompatible with FontForge's. It can't be guaranteed it will work well. It is suggested to allow FontForge to insert its code and then append user's own. 0u006D There already exists a 'cvt' table, perhaps legacy. FontForge can use it, but can't make any assumptions on values stored there, so generated instructions will be of lower quality. If legacy hinting is to be scrapped, it is suggested to clear the `cvt` and repeat autoinstructing. There exists a 'prep' code incompatible with FontForge's. It can't be guaranteed it will work well. It is suggested to allow FontForge to insert its code and then append user's own. 0u006E There already exists a 'cvt' table, perhaps legacy. FontForge can use it, but can't make any assumptions on values stored there, so generated instructions will be of lower quality. If legacy hinting is to be scrapped, it is suggested to clear the `cvt` and repeat autoinstructing. There exists a 'prep' code incompatible with FontForge's. It can't be guaranteed it will work well. It is suggested to allow FontForge to insert its code and then append user's own. 0u006F There already exists a 'cvt' table, perhaps legacy. FontForge can use it, but can't make any assumptions on values stored there, so generated instructions will be of lower quality. If legacy hinting is to be scrapped, it is suggested to clear the `cvt` and repeat autoinstructing. There exists a 'prep' code incompatible with FontForge's. It can't be guaranteed it will work well. It is suggested to allow FontForge to insert its code and then append user's own. 0u0070 There already exists a 'cvt' table, perhaps legacy. FontForge can use it, but can't make any assumptions on values stored there, so generated instructions will be of lower quality. If legacy hinting is to be scrapped, it is suggested to clear the `cvt` and repeat autoinstructing. There exists a 'prep' code incompatible with FontForge's. It can't be guaranteed it will work well. It is suggested to allow FontForge to insert its code and then append user's own. 0u0072 There already exists a 'cvt' table, perhaps legacy. FontForge can use it, but can't make any assumptions on values stored there, so generated instructions will be of lower quality. If legacy hinting is to be scrapped, it is suggested to clear the `cvt` and repeat autoinstructing. There exists a 'prep' code incompatible with FontForge's. It can't be guaranteed it will work well. It is suggested to allow FontForge to insert its code and then append user's own. 0u0073 There already exists a 'cvt' table, perhaps legacy. FontForge can use it, but can't make any assumptions on values stored there, so generated instructions will be of lower quality. If legacy hinting is to be scrapped, it is suggested to clear the `cvt` and repeat autoinstructing. There exists a 'prep' code incompatible with FontForge's. It can't be guaranteed it will work well. It is suggested to allow FontForge to insert its code and then append user's own. 0u0074 There already exists a 'cvt' table, perhaps legacy. FontForge can use it, but can't make any assumptions on values stored there, so generated instructions will be of lower quality. If legacy hinting is to be scrapped, it is suggested to clear the `cvt` and repeat autoinstructing. There exists a 'prep' code incompatible with FontForge's. It can't be guaranteed it will work well. It is suggested to allow FontForge to insert its code and then append user's own. 0u0075 There already exists a 'cvt' table, perhaps legacy. FontForge can use it, but can't make any assumptions on values stored there, so generated instructions will be of lower quality. If legacy hinting is to be scrapped, it is suggested to clear the `cvt` and repeat autoinstructing. There exists a 'prep' code incompatible with FontForge's. It can't be guaranteed it will work well. It is suggested to allow FontForge to insert its code and then append user's own. 0u0076 There already exists a 'cvt' table, perhaps legacy. FontForge can use it, but can't make any assumptions on values stored there, so generated instructions will be of lower quality. If legacy hinting is to be scrapped, it is suggested to clear the `cvt` and repeat autoinstructing. There exists a 'prep' code incompatible with FontForge's. It can't be guaranteed it will work well. It is suggested to allow FontForge to insert its code and then append user's own. 0u0077 There already exists a 'cvt' table, perhaps legacy. FontForge can use it, but can't make any assumptions on values stored there, so generated instructions will be of lower quality. If legacy hinting is to be scrapped, it is suggested to clear the `cvt` and repeat autoinstructing. There exists a 'prep' code incompatible with FontForge's. It can't be guaranteed it will work well. It is suggested to allow FontForge to insert its code and then append user's own. 0u007A There already exists a 'cvt' table, perhaps legacy. FontForge can use it, but can't make any assumptions on values stored there, so generated instructions will be of lower quality. If legacy hinting is to be scrapped, it is suggested to clear the `cvt` and repeat autoinstructing. There exists a 'prep' code incompatible with FontForge's. It can't be guaranteed it will work well. It is suggested to allow FontForge to insert its code and then append user's own. 0uA7AB There already exists a 'cvt' table, perhaps legacy. FontForge can use it, but can't make any assumptions on values stored there, so generated instructions will be of lower quality. If legacy hinting is to be scrapped, it is suggested to clear the `cvt` and repeat autoinstructing. There exists a 'prep' code incompatible with FontForge's. It can't be guaranteed it will work well. It is suggested to allow FontForge to insert its code and then append user's own. 0uA7AC There already exists a 'cvt' table, perhaps legacy. FontForge can use it, but can't make any assumptions on values stored there, so generated instructions will be of lower quality. If legacy hinting is to be scrapped, it is suggested to clear the `cvt` and repeat autoinstructing. There exists a 'prep' code incompatible with FontForge's. It can't be guaranteed it will work well. It is suggested to allow FontForge to insert its code and then append user's own. 0uA7AE There already exists a 'cvt' table, perhaps legacy. FontForge can use it, but can't make any assumptions on values stored there, so generated instructions will be of lower quality. If legacy hinting is to be scrapped, it is suggested to clear the `cvt` and repeat autoinstructing. There exists a 'prep' code incompatible with FontForge's. It can't be guaranteed it will work well. It is suggested to allow FontForge to insert its code and then append user's own. 0u00C6 There already exists a 'cvt' table, perhaps legacy. FontForge can use it, but can't make any assumptions on values stored there, so generated instructions will be of lower quality. If legacy hinting is to be scrapped, it is suggested to clear the `cvt` and repeat autoinstructing. There exists a 'prep' code incompatible with FontForge's. It can't be guaranteed it will work well. It is suggested to allow FontForge to insert its code and then append user's own. 0u00D0 There already exists a 'cvt' table, perhaps legacy. FontForge can use it, but can't make any assumptions on values stored there, so generated instructions will be of lower quality. If legacy hinting is to be scrapped, it is suggested to clear the `cvt` and repeat autoinstructing. There exists a 'prep' code incompatible with FontForge's. It can't be guaranteed it will work well. It is suggested to allow FontForge to insert its code and then append user's own. 0u00E6 There already exists a 'cvt' table, perhaps legacy. FontForge can use it, but can't make any assumptions on values stored there, so generated instructions will be of lower quality. If legacy hinting is to be scrapped, it is suggested to clear the `cvt` and repeat autoinstructing. There exists a 'prep' code incompatible with FontForge's. It can't be guaranteed it will work well. It is suggested to allow FontForge to insert its code and then append user's own. 0u00F0 There already exists a 'cvt' table, perhaps legacy. FontForge can use it, but can't make any assumptions on values stored there, so generated instructions will be of lower quality. If legacy hinting is to be scrapped, it is suggested to clear the `cvt` and repeat autoinstructing. There exists a 'prep' code incompatible with FontForge's. It can't be guaranteed it will work well. It is suggested to allow FontForge to insert its code and then append user's own. Generate .ttf file. Convert .ttf to XML file. Add xAvgCharWidth data into XML file. Convert XML file to .ttf file. Padding to a 4-byte boundary. Done.