FontLab Forum
2012-05-21, 00:09:22 *
Welcome, Guest. Please login or register.

Login with username, password and session length
News: Welcome to the FontLab forum, read how to use it! Update: Archives from old MSN forums are now available on our forum.
 
   Home   Help Search Calendar Downloads Tags Login Register  
Del.icio.us Digg FURL FaceBook Stumble Upon Reddit SlashDot

Pages: [1]
  Print  
Author Topic: WEFT 2 hangs on analyzing / Proxy Prob? / Manual encoding possible?  (Read 1184 times)
ArchivePoster
Guest
« on: 2000-03-21, 09:59:00 »

Posted by: Manni
         

Logged
ArchivePoster
Guest
« Reply #1 on: 2000-03-21, 16:06:00 »

Posted by: rwp780
         

Hello fellow weft victim,

This WEFT has to be the most unstable program i have ever seen and had the discomfort of using. I too did the overnight thing on an extremely simple web page with a tiled background and 6, yes 6 characters i wanted to embed. Did not budge even 1/2  a percentile point in 10 hours. I use a 700mhz PIII w/ 256MB of RAM. That's  A LOT of muscle and the program still sits there spinning it's wheels FOR 10 HOURS!!!!! I've opend up the font objects files(*.eot) in notepad and there is a legible directories typed in there. That's the key to the whole thing. Those directories are what dictates which files can use the object. I tried to change the directory manually. Couldn't get it to reliably work. Can't get WEFT to reliably work either though so it's no surprise. I also have a problem jus getting the thing to create the object in the first place. I created a Felix Titling object last week. I tried it today for a different  directory (since manually won't work for me) and the program now tells me the font is too complex/machine out of resources. BETA, go figure. I keep on it and let you know waht i get.

-Logic 


Logged
ArchivePoster
Guest
« Reply #2 on: 2000-03-21, 18:40:00 »

Posted by: mjan
         

There is an "expert create fonts" menu in WEFT that will let you create an EOT without having to go through the wizard.

Note however that you need to fully understand the concept of the "bind roots" and such before using it. I recommend using the new version of WEFT.

Also, the progress indicator will only advance once a complete page has been processed. If you only have one page, then it will go from 0 to 100 in one step.

I'd be glad to look into this problem if you could provide some additional information, such as the url to the page. Post it here or send it to simonda@microsoft.com and mjan@borware.se

An interim solution may be for you to process a local copy of the page on your own machine, and then publish it to your server. Just remember to add the url to your web server by clicking on the "mirror sites" button on the "create web fonts" page of the wizard.

Here is some information regarding why WEFT analyzes pages and why it needs to know where the pages are located:

The fonts you are using is owned by various font vendors. In the license agreement for some of these font products, you have been given the right to use the fonts in *your* documents. As such, you may not make copies (in any format) and re-distribute them freely (that is called stealing ;-).

This is why WEFT "binds" the font to those web pages that *you* have created. The font objects (the eot files) are thus branded with the url of the pages that is supposed to use the font. Also, this prevents people from simply copying the files and using them on other servers.

When WEFT analyzes a page, it determines exactly what characters are used for each font on a pages. This makes for small font files, as un-used characters are not included in the created font objects (eot files).

 


Logged
Tags:
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF | SMF © 2011, Simple Machines Valid XHTML 1.0! Valid CSS!