[PD] multi-language help patches

Lucas Cordiviola lucarda27 at hotmail.com
Sat Feb 27 01:03:55 CET 2016


Are you shure you want to use the wikipedia for that?

Mensaje telepatico asistido por maquinas.

Date: Fri, 26 Feb 2016 23:44:49 +0000
To: danomatika at gmail.com
CC: pd-list at lists.iem.at
Subject: Re: [PD] multi-language help patches
From: pd-list at lists.iem.at

Ok, so which html reference system should I leverage here?  Where will 
the html files get stored, and how do we get from clicking the link in the 
help patch (I'm assuming we're still using the current help patches to show 
a simple demo of the object) to opening the html doc in the correct language? 
-Jonathan 

    On Friday, February 26, 2016 4:34 PM, Dan Wilcox <danomatika at gmail.com> wrote:
  

 I think what implying is that maybe Pd *doesn’t* need to handle it. Simply, Pd could open a local webpage, similar to how the Processing “Find in reference” context menu option works when highlighting a function in the editor.Not to say you/we can’t work out a file format/system to handle alot of this, but I’m thinking that html reference already works well for many other contexts an doesn’t require building new formats/systems to solve alot of the same problems.
--------Dan Wilcox at danomatikadanomatika.comrobotcowboy.com


On Feb 26, 2016, at 2:08 PM, Jonathan Wilkes <jancsika at yahoo.com> wrote:html could be leveraged, but I'm really looking for a spec for how Pd handles it.  Is it a GUI widget?  An abstraction?  A canvas method?  A new "#" directive?Do the translations get saved along with the help patch, or are they stored in a directory and fetched when needed?  Etc.-Jonathan     On Friday, February 26, 2016 1:02 PM, Dan Wilcox <danomatika at gmail.com> wrote:   I'll implement any *clear* spec for multi-language help patches someone comes up with with the following constraints:1. it separates design from content.2. in only requires documentation writers to care about content.3. it does not pigeonhole help patches into having a single, ugly design4. documentation writers will be guaranteed that whatever they write, it won't overlap patch content.5. it is maintainable and scalableSounds like .html.
--------Dan Wilcox at danomatikadanomatika.comrobotcowboy.com_______________________________________________Pd-list@lists.iem.at mailing listUNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list     

     
_______________________________________________
Pd-list at lists.iem.at mailing list
UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20160227/fb609313/attachment-0001.html>


More information about the Pd-list mailing list