Hi Andres, I can help in anything needed to translate to Portuguese, I just need to be oriented in what ways I should do that, to conform to general procedures thx, robson On 11/25/06, csound-devel-request@lists.sourceforge.net < csound-devel-request@lists.sourceforge.net> wrote: > > Send Csound-devel mailing list submissions to > csound-devel@lists.sourceforge.net > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/csound-devel > or, via email, send a message with subject or body 'help' to > csound-devel-request@lists.sourceforge.net > > You can reach the person managing the list at > csound-devel-owner@lists.sourceforge.net > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Csound-devel digest..." > > > Today's Topics: > > 1. Re: Manual translations was: OLPC csound documentation > (Andres Cabrera) > 2. Re: Is there a virtual midi controller opcode, or it needs to > be coded? (Robson Cozendey) > 3. 64-bit csound and pvanal and pvoc opcodes (Andres Cabrera) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 25 Nov 2006 10:01:10 -0500 > From: Andres Cabrera > Subject: Re: [Cs-dev] Manual translations was: OLPC csound > documentation > To: Developer discussions > Message-ID: <45685AB6.6030109@geminiflux.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Hi Steven, > Thanks for your pointers, I've had a look and it seems that a separate > module is used for each translation. I'm thinking of doing it this way > and to keep track, I'll add a text file detailing which cvs version of > the file from the english manual is currently translated, and > translators would have to update this manually everytime they translate > a file. A bit awkward but I can think of no better way... > I'm doing a reorganization I've been meaning to do for a while, before > creating a french manual module. > > Cheers, > Andr?s > > > Steven Yi wrote: > > Hi Andres, > > > > I don't know if there's any good way to do this, but I haven't ever > > been involved with projects where documentation was multi-lingual. It > > might be interesting to look at projects like gnome and kde which have > > documentaiton in many languages and see how they set up their > > repositories in the source control systems. I couldn't figure out on > > kde's site how they organize in subversion, but they have a guide for > > translators which might be of use: > > > > http://l10n.kde.org/docs/translation-howto/doc-translation.html > > http://l10n.kde.org/ > > > > steven > > > > > > On 11/23/06, Andres Cabrera wrote: > > > >> Hi Francois, > >> Thanks very much for your contribution! I'm thinking about how to > >> integrate the translated documentation, to ease maintenance and to know > >> when a certain page is out of date with the main english sources. > >> Would it be a good idea to create a new module with each language > >> sources? Or would it be better to create branches in the same module? > >> > >> What would be the best way to know whether a transaltion is > synchronized > >> with the main sources? Should an informative tag be added on each > >> translated page referring to the cvs version number of the english > file, > >> or would it be better to handle that on a single unified file? > >> > >> Any thoughts on this are most welcome, since my expierience with this > is > >> very limited! > >> > >> Thanks, > >> Andr?s > >> > >> > >> Francois Pinot wrote: > >> > >>> csound-devel-request@lists.sourceforge.net a ?crit : > >>> > >>>> ... > >>>> It would also be great to start translations of the manual. Any > >>>> volunteers? > >>>> Does anyone know if it is possible to maintain -using docbook- a > >>>> single set > >>>> of sources and decide at compile time which language to build? > >>>> > >>>> Cheers, > >>>> Andres > >>>> > >>>> > >>>> > >>> Hi Andres, > >>> > >>> I can contribute to a translation in french. I join an example of the > >>> preface.xml file translated in french. The differences from the > >>> english version are the presence of diacritics characters and a space > >>> before any double ponctuation mark ( ie ; : ). The file uses > >>> ISO-8859-1 coding. It can be coded in utf8 if preferred. > >>> > >>> Cheers > >>> > >>> Francois Pinot > >>> > ------------------------------------------------------------------------ > >>> > >>>
> >>> > >>> > >>> Barry > >>> Vercoe > >>> > >>> MIT Media Lab > >>> > >>> > >>> > >>> > >>> Pr?face du Manuel de Csound > >>> > >>> > >>> par &namebarry;, MIT Media Lab > >>> > >>> > >>> > >>> La r?alisation de musique par ordinateur n?cessite la synth?se de > signaux audio avec des points discrets ou ?chantillons repr?sentant des > formes d'onde continues. Il y a de nombreuses fa?ons de faire ceci, chacune > offrant un type de contr?le diff?rent. La synth?se directe g?n?re des formes > d'onde en ?chantillonnant une fonction enregistr?e repr?sentant une simple > p?riode ; la synth?se additive g?n?re les nombreux partiels d'un son > complexe, chacun ayant sa propre enveloppe d'intensit? ; la synth?se > soustractive d?marre avec un son complexe pour le filtrer. La synth?se > non-lin?aire utilise la modulation de fr?quence et la distorsion > non-lin?aire pour donner des caract?ristiques complexes ? des signaux > simples, tandis que l'?chantillonnage et l'enregistrement d'un son naturel > permet de l'utiliser ? volont?. > >>> > >>> > >>> > >>> Comme la sp?cification d?taill?e d'un son point par point est vite > ennuyeuse, le contr?le est op?r? de deux mani?res : 1) ? partir > d'instruments dans un orchestre, et 2) ? partir d'?v?nements dans une > partition. Un orchestre est en fait un programme d'ordinateur qui peut > produire des sons, tandis qu'une partition est un ensemble de donn?es > auxquelles ce programme r?agit. Qu'une dur?e d'attaque soit une constante > fix?e dans un instrument, ou une variable de chaque note dans la partition, > d?pend de la fa?on dont l'utilisateur veut la contr?ler. > >>> > >>> > >>> > >>> Les instruments d'un orchestre de Csound (cf linkend="OrchTop">Syntaxe de l'Orchestre) sont > d?finis dans une syntaxe simple qui invoque des proc?dures de traitement > audio complexe. Une partition (cf La > Partition Num?rique Standard) pass?e ? cet orchestre > contient des informations de hauteur et de contr?le cod?es num?riquement > dans un format standard. Bien que la plupart des utilisateurs se contentent > de ce format, des langages de traitement de partition de plus haut niveau > sont souvent commodes. > >>> > >>> > >>> > >>> Les programmes constituant le syst?me Csound ont une longue > histoire de d?veloppement, qui a commenc? avec le programme Music 4 ?crit > aux Bell Telephone Laboratories au d?but des ann?es 1960 par Max Mathews. > C'est l? que furent con?us le concept de table d'onde ainsi qu'une grande > partie de la terminologie qui a permis depuis aux chercheurs de la musique > par ordinateur de communiquer. D'importantes additions furent apport?es ? > Princeton par feu Godfrey Winham dans Music 4B ; mon propre Music 360 (1968) > doit beaucoup ? ce travail. Avec Music 11 (1973) j'ai pris une voie > diff?rente : les deux structures distinctes des signaux de contr?le et des > signaux audio sont issues de mon engagement intensif dans les ann?es > pr?c?dentes dans la conception et l'?laboration de machines de synth?se > num?rique. Cette division a ?t? retenue dans Csound. > >>> > >>> > >>> > >>> Parce qu'il est enti?rement ?crit en C, on peut installer > facilement Csound sur n'importe quelle machine ?quip?e de Unix ou du langage > C. Au MIT il tourne sur des stations VAX/DEC sous Ultrix 4.2, sur des > machines SUN sous OS 4.1, sur SGI sous 5.0, sur IBM PC sous DOS 6.2 et > Windows 3.1, et sur le Macintosh d'Apple sous ThinkC 5.0. Avec ce seul > langage de d?finition de traitement num?rique du signal et des formats audio > portables comme AIFF et WAV, les utilisateurs peuvent passer facilement > d'une machine ? une autre. > >>> > >>> > >>> > >>> La version de 1991 apporta le vocodeur de phase, FOF, et les types > de donn?es spectrales. 1992 vit l'arriv?e des convertisseurs et des unit?s > de contr?le MIDI, permettant de piloter Csound depuis des fichiers MIDI > (midifiles) et des claviers externes. En 1994 les programmes d'analyse du > son (lpc, pvoc) furent int?gr?s dans le module principal, permettant de > lancer tous les traitement de Csound depuis un seul ex?cutable, et Cscore > pouvait passer les partitions directement ? l'orchestre pour une r?alisation > it?rative. La version de 1995 introduisit un ensemble MIDI ?tendu avec > linseg bas? sur MIDI, les filtres de Butterworth, la synth?se granulaire, et > un d?tecteur de hauteur am?lior? dans le domaine fr?quentiel. L'addition > d'outils de g?n?ration d'?v?nements en temps-r?el (Cscore et MIDI) fut > particuli?rement importante, permettant des configurations > excitation/r?ponse en temps-r?el qui rendent possible la composition et > l'exp?rimentation interactives. Il est apparu qu > e la synth?se num?rique par programme en temps-r?el est maintenant > r?ellement prometteuse. > >>> > >>>
> >>> > >>> > >>> > ------------------------------------------------------------------------ > >>> > >>> > ------------------------------------------------------------------------- > >>> Take Surveys. Earn Cash. Influence the Future of IT > >>> Join SourceForge.net's Techsay panel and you'll get the chance to > share your > >>> opinions on IT & business topics through brief surveys - and earn cash > >>> > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > >>> > ------------------------------------------------------------------------ > >>> > >>> _______________________________________________ > >>> Csound-devel mailing list > >>> Csound-devel@lists.sourceforge.net > >>> https://lists.sourceforge.net/lists/listinfo/csound-devel > >>> > >>> > >> > >> > ------------------------------------------------------------------------- > >> Take Surveys. Earn Cash. Influence the Future of IT > >> Join SourceForge.net's Techsay panel and you'll get the chance to share > your > >> opinions on IT & business topics through brief surveys - and earn cash > >> > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > >> _______________________________________________ > >> Csound-devel mailing list > >> Csound-devel@lists.sourceforge.net > >> https://lists.sourceforge.net/lists/listinfo/csound-devel > >> > >> > > > > > ------------------------------------------------------------------------- > > Take Surveys. Earn Cash. Influence the Future of IT > > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > > opinions on IT & business topics through brief surveys - and earn cash > > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > > Csound-devel mailing list > > Csound-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/csound-devel > > > > > > > > > > ------------------------------ > > Message: 2 > Date: Sat, 25 Nov 2006 13:03:51 -0200 > From: "Robson Cozendey" > Subject: Re: [Cs-dev] Is there a virtual midi controller opcode, or > it > needs to be coded? > To: "Developer discussions" > Message-ID: > <324c3750611250703u20865f87v5cd8ba05f7181188@mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > Ok, I could read it in the tagged way :-) > Now I?m moving to the general list, thanks for the good news! > > > On 11/25/06, Robson Cozendey wrote: > > > > Thank you, Steven! > > > > I downloaded the XML manual page, but it?s not being recognized by > > Internet Explorer. Is it expected, should I get another browser to work? > > > > thx again, > > robson > > > > ps: I know that this discussion is going away of the dev purpose... as > > soon as possible, I will move it to the general list :-) > > > > > > On 11/25/06, Steven Yi wrote: > > > > > > Hi Robson, > > > > > > Yes, the virtual keyboard is in CVS and also was released in 5.04. > > > There is a manual entry but it wasn't done until after 5.04 was > > > released, so you have to get it from CVS. (You can see the xml here: > > > > > > > http://csound.cvs.sourceforge.net/csound/manual/midi/virtual.xml?revision=1.2&view=markup > > > > > > > > > and image here: > > > > > > > http://csound.cvs.sourceforge.net/csound/manual/images/virtualkeyboard.png?revision=1.1&view=markup > > > > > > > > > steven > > > > > > > > > On 11/25/06, Robson Cozendey wrote: > > > > > > > > Hello everyone, > > > > > > > > Thanks for the help on building CSound, in the other topic :) > > > > > > > > One of the reasons I entered the list, is that I did not found an > > > opcode > > > > with the functionality I needed, so I wondered that I would need to > > > code it, > > > > so here I am. > > > > > > > > The opcode I need and didn?t found was a virtual midi controller, > that > > > would > > > > turn the PC keyboard into a midi controller, and each keystroke > would > > > send a > > > > midi message to CSound. > > > > > > > > But before starting it, I would like to know if I didn?t missed > > > something, > > > > maybe already exists such an opcode, and I would not need to > re-invent > > > the > > > > wheel > > > > > > > > I?m saying that because I read (in the Steven Yi deferred plug-in > > > topic) > > > > that he was working on some sort of a virtual keyboard driver, so > > > maybe > > > > somewhere inside CSound there is such a functionality already. I > would > > > be > > > > glad to find that is such a case > > > > Otherwise, I would start my homework asap... > > > > > > > > thanks in advance, > > > > robson > > > > > > > > ------------------------------------------------------------------------- > > > > Take Surveys. Earn Cash. Influence the Future of IT > > > > Join SourceForge.net's Techsay panel and you'll get the chance to > > > share your > > > > opinions on IT & business topics through brief surveys - and earn > cash > > > > > > > > > > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > > > > > > > _______________________________________________ > > > > Csound-devel mailing list > > > > Csound-devel@lists.sourceforge.net > > > > https://lists.sourceforge.net/lists/listinfo/csound-devel > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------------------------- > > > Take Surveys. Earn Cash. Influence the Future of IT > > > Join SourceForge.net's Techsay panel and you'll get the chance to > share > > > your > > > opinions on IT & business topics through brief surveys - and earn cash > > > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > > > > > _______________________________________________ > > > Csound-devel mailing list > > > Csound-devel@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/csound-devel > > > > > > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://sourceforge.net/mailarchive/forum.php?forum=csound-devel/attachments/20061125/70ef5232/attachment.html > > ------------------------------ > > Message: 3 > Date: Sat, 25 Nov 2006 13:13:56 -0500 > From: Andres Cabrera > Subject: [Cs-dev] 64-bit csound and pvanal and pvoc opcodes > To: Developer discussions > Message-ID: <456887E4.1050205@geminiflux.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Hi all, > Is this sentence in the manual still true? > > For 64-bit Csound, use of pvanal and pvoc opcodes are not currently > supported. If your work file uses pvoc, use Csound. (This is a temporary > issue relating to older file formats and is currently being addressed > and worked on.) > > > I'm revising, and I think this might be corrected already? > > > Cheers, > Andr?s > > > > > ------------------------------ > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > ------------------------------ > > _______________________________________________ > Csound-devel mailing list > Csound-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/csound-devel > > > End of Csound-devel Digest, Vol 7, Issue 69 > ******************************************* >