Re: Sites for sore eyes

@nwillis  As example out-dated doc, but which 'should' be ported and
updated, there are the Python and native scripting description docs.  (
http://fontforge.org/python.html  http://fontforge.org/scripting.html)

In investigating just a few bugs therein (python.c) I've seen over a dozen
'new' APIs which are not documented!  And have no idea about APIs which
have changed. For instance, font.save() now has a second integer argument
for SFD file versioning contributed by @monkeyiq.

Echoing at least one other person, I think the scripting feature is a
killer app feature.  But yet certainly a lower priority doc than "how to
generate font files" usage info.

Can we establish any sort of ranking / priority / desirability for sections
and pages?

(I know I'd rather fix code that fix prose, but the prose gets people into
using the program...)


On Fri, Sep 5, 2014 at 3:14 PM, Nathan Willis <[email protected]>
wrote:
>
> On Fri, Sep 5, 2014 at 6:03 AM, Dave Crossland <[email protected]> wrote:
>>
>> We need to make the new one have all the info in the old one
>>
>
> OK. What's missing, specifically?  Surely we don't want to replicate all
> of the outdated docs as-is.  FTR, I did find the Github issue on this, but
> I'm not clear from that if new docs are needed or what....
>
>>
> Nate
> --
> nathan.p.willis
> [email protected] <http://identi.ca/n8>
>

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/

_______________________________________________
fontforge-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fontforge-devel
http://fontforge.10959.n7.nabble.com/Developer-f3.html