Re: Font specifications
- From: al jones <alfredmjones@xxxxxxxxxxxx>
- Date: Sun, 16 Apr 2006 17:30:05 GMT
On Sun, 16 Apr 2006 14:51:38 +0100, Jack wrote:
al jones wrote:
In most cases I readily agree to 'stop wanting that' but in this case
it's an entirely different animal. I'm the author of a Visual Basic
program which, among other things lists the fonts one has on their
own system. One of my users requested that I output a list sorted by
his options (which is what FontOrg is all about) in HTML so he can
click on the link to bring up the font viewer.
Here there is a category error; the user's requirements have been
confused with a detail of the implementation. What the user requires is
the ability to click on an entry in 'a list sorted by his options', with
the list presumably including a demonstration of each installed font.
He (probably) does not *require* that the list be represented using
HTML, any more than he requires the application to be written in a
modular fashion, with comments in english in each module and each
subroutine. And even if he does require these things, they would be a
different class of requirements from those mentioned earlier, the former
being functional in nature, the latter being technical requirements.
What I'm suggesting, in my roundabout way, is that HTML may be the wrong
implementation technology to choose, given that this is a desktop
application. I take it you are planning to use a browser widget to
display the list, and that this is behind the need to represent the list
as HTML. my VB knowledge is pretty rusty, but some other kind of
rich-text widget would seem to be more appropriate.
Of course, your choice of HTML to represent the list may arise from
other exigencies that you haven't mentioned - after all, your original
post failed to mention the crucial fact that you are writing a desktop
application, not a web-page.
Trying not to sounds so pedantic as the responder - no, my question was
very pecific "is there a way to do this" and the reply should have been
just as specific "No."
While this group is 'www.authoring.html' I chose the aspect of authoring
html as the operative part - my mistake. How a web page is generated - by
hand in NotePad, programatically in one of the WYSIWYG editors or
programatically output from an application (Word, Open Office, or my
FontOrg) - should, IMHO, be secondary to the question asked. Of course
there are other considerations - my question was, in fact, very specific
"Is there a way to display these fonts directly from within an html
document?" (Paraphrased somewhat.)
Phils response, which never made it to my server - I ony see it in the
quote from Stan - was the operative answer: In some cases that might be
interesting (as in this one) but he knows of none.
I actually can tolerate Jacks answer - and I get really tired of 'stop
wanting that' - because he goes on to give reasons that one should 'not
want that' which make it a very acceptable answer.
Your esoteric cogitations (translate to read verbal flatulance) regarding
the users request - not requirement - which caused me to take a look at an
option in implementation that I hadn't previously, are entirely
unnecessary. Your third paragraph actually has meaning - but ignores the
fact that I just may have looked at the richtext / straight text options.
Is html and invoking the browser a poor choice? Possibly, but it is a
choice I'd presume to be able to make on my own, however, not being
all-knowing, I asked a question regarding the posssibility / feasibility of
another option.
enough, I have better things to do ...
Phil, Stan I thank you and do appreciate you input.
//al
.
- Follow-Ups:
- Re: Font specifications
- From: Jack
- Re: Font specifications
- References:
- Font specifications
- From: al jones
- Re: Font specifications
- From: phil-news-nospam
- Re: Font specifications
- From: Stan Brown
- Re: Font specifications
- From: al jones
- Re: Font specifications
- From: Jack
- Font specifications
- Prev by Date: Re: why a different tag for SVG images?
- Next by Date: Re: Font specifications
- Previous by thread: Re: Font specifications
- Next by thread: Re: Font specifications
- Index(es):
Relevant Pages
|