Menu
▾
▴
trans-devel
|
From: Giulio P. <giu...@gm...> - 2013-08-12 08:47:57
Attachments:
1001_pt_localization_file.patch
1002_use_snack_sndfile_ext.patch
1003_make_alt_click_expand_signal.patch
1004_fix_trans_file_permissions.patch
1005_avoid_to_put_transcriber_in_background.patch
1006_fix_documentation.patch
1007_fix_html_conversion.patch
1008_update_contacts_and_urls.patch
1010_fix_cha_export.patch
|
Dear Transcriber Team, during the last year I have written several patches that I would like to see included in transcriber. Is it possible? Is it possible that a new bug-fix release of the legacy transcriber will be released in future? Attached are the patches that I think are ready to be included, they apply (in order) cleanly to the latest release on sourceforge. Bests, Giulio. |
|
From: Giulio P. <giu...@gm...> - 2013-08-06 15:36:14
Attachments:
1001_pt_localization_file.patch
1002_use_snack_sndfile_ext.patch
1003_make_alt_click_expand_signal.patch
1004_fix_trans_file_permissions.patch
1005_avoid_to_put_transcriber_in_background.patch
1006_fix_documentation.patch
1007_fix_html_conversion.patch
1008_update_contacts_and_urls.patch
1009_update_contacts_and_urls_in_doc.patch
1010_fix_cha_export.patch
|
Dear Transcriber Team, during the last year I have written several patches that I would like to see included in transcriber. Is it possible? Is it possible that a new bug-fix release of the legacy transcriber will be released in future? Attached are the patches that I think are ready to be included, they apply (in order) cleanly to the latest release on sourceforge. Bests, Giulio. |
|
From: Claude B. <Cla...@li...> - 2013-08-26 13:44:04
|
Hi Giulio, Thanks a lot for your contribution! As a matter of fact, updating the legacy Transcriber is long overdue (and binaries for modern versions of Windows and MacOS are missing), because of lacking time and resource. A newer C++ version (TransAG) has been developped in between even if it is currently not very active either. But if you can invest some time on it, you could become developer member on the Sourceforge site and include your updates yourself ? Let me know about your use of Transcriber and if you are interested ! Best, Claude Le 06/08/13 17:36, Giulio Paci a écrit : > Dear Transcriber Team, > during the last year I have written several patches that I would like to see included in transcriber. > Is it possible? Is it possible that a new bug-fix release of the legacy transcriber will be released in future? > > Attached are the patches that I think are ready to be included, they apply (in order) cleanly to the latest release on sourceforge. > > Bests, > Giulio. > > > ------------------------------------------------------------------------------ > Introducing Performance Central, a new site from SourceForge and > AppDynamics. Performance Central is your source for news, insights, > analysis and resources for efficient Application Performance Management. > Visit us today! > http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk > > > _______________________________________________ > Trans-devel mailing list > Tra...@li... > https://lists.sourceforge.net/lists/listinfo/trans-devel -- LIMSI-CNRS tel: +33 1 69 85 81 84 bat. 508, BP 133 fax: +33 1 69 85 80 88 Univ Paris-Sud 91403 Orsay cedex France web: http://www.limsi.fr/Individu/barras/ |
|
From: Giulio P. <giu...@gm...> - 2013-08-28 21:59:47
|
Il 26/08/2013 15:44, Claude Barras ha scritto: > Thanks a lot for your contribution! As a matter of fact, updating the legacy Transcriber is long overdue (and binaries for modern versions of Windows and MacOS are > missing), because of lacking time and resource. A newer C++ version (TransAG) has been developped in between even if it is currently not very active either. > But if you can invest some time on it, you could become developer member on the Sourceforge site and include your updates yourself? Let me know about your use of > Transcriber and if you are interested! I know about TransAG, but my colleagues (we are working only with audio) did not find it a viable alternative to the legacy transcriber (we are used to the legacy interface, shortcuts, ...). Moreover we also have several tools that automatically process .trs files that are not exported by TransAG. We are currently using transcriber to transcribe and annotate audio streams (mostly children interaction with a robot). I have very few time, but I will be more than happy to contribute to Transcriber (and eventually TransAG). Do you think it would be possible to convert the current repository to a git-based repository? I think it is much more convenient to use than CVS. Bests, Giulio. > Le 06/08/13 17:36, Giulio Paci a écrit : >> Dear Transcriber Team, >> during the last year I have written several patches that I would like to see included in transcriber. >> Is it possible? Is it possible that a new bug-fix release of the legacy transcriber will be released in future? >> >> Attached are the patches that I think are ready to be included, they apply (in order) cleanly to the latest release on sourceforge. >> >> Bests, >> Giulio. >> >> >> ------------------------------------------------------------------------------ >> Introducing Performance Central, a new site from SourceForge and >> AppDynamics. Performance Central is your source for news, insights, >> analysis and resources for efficient Application Performance Management. >> Visit us today! >> http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk >> >> >> _______________________________________________ >> Trans-devel mailing list >> Tra...@li... >> https://lists.sourceforge.net/lists/listinfo/trans-devel > > -- > LIMSI-CNRS tel: +33 1 69 85 81 84 > bat. 508, BP 133 fax: +33 1 69 85 80 88 > Univ Paris-Sud > 91403 Orsay cedex France web: http://www.limsi.fr/Individu/barras/ > |
|
From: Claude B. <Cla...@li...> - 2013-08-29 15:45:11
|
Hi, this is a good idea; I have also been using git for recent projects and I will have a look at the switch. Best, Claude Le 29/08/13 00:01, Giulio Paci a écrit : > Il 26/08/2013 15:44, Claude Barras ha scritto: >> Thanks a lot for your contribution! As a matter of fact, updating the legacy Transcriber is long overdue (and binaries for modern versions of Windows and MacOS are >> missing), because of lacking time and resource. A newer C++ version (TransAG) has been developped in between even if it is currently not very active either. >> But if you can invest some time on it, you could become developer member on the Sourceforge site and include your updates yourself? Let me know about your use of >> Transcriber and if you are interested! > I know about TransAG, but my colleagues (we are working only with audio) did not find it a viable alternative to the legacy transcriber (we are used to the legacy > interface, shortcuts, ...). > Moreover we also have several tools that automatically process .trs files that are not exported by TransAG. > > We are currently using transcriber to transcribe and annotate audio streams (mostly children interaction with a robot). > > I have very few time, but I will be more than happy to contribute to Transcriber (and eventually TransAG). Do you think it would be possible to convert the current > repository to a git-based repository? I think it is much more convenient to use than CVS. > > Bests, > Giulio. > >> Le 06/08/13 17:36, Giulio Paci a écrit : >>> Dear Transcriber Team, >>> during the last year I have written several patches that I would like to see included in transcriber. >>> Is it possible? Is it possible that a new bug-fix release of the legacy transcriber will be released in future? >>> >>> Attached are the patches that I think are ready to be included, they apply (in order) cleanly to the latest release on sourceforge. >>> >>> Bests, >>> Giulio. >>> >>> |
|
From: Giulio P. <giu...@gm...> - 2013-09-11 12:39:52
|
Hi Claude, any news? Bests, Giulio. On 29/08/2013 17:45, Claude Barras wrote: > Hi, this is a good idea; I have also been using git for recent projects > and I will have a look at the switch. > Best, > Claude > > > Le 29/08/13 00:01, Giulio Paci a écrit : >> Il 26/08/2013 15:44, Claude Barras ha scritto: >>> Thanks a lot for your contribution! As a matter of fact, updating the >>> legacy Transcriber is long overdue (and binaries for modern versions >>> of Windows and MacOS are >>> missing), because of lacking time and resource. A newer C++ version >>> (TransAG) has been developped in between even if it is currently not >>> very active either. >>> But if you can invest some time on it, you could become developer >>> member on the Sourceforge site and include your updates yourself? Let >>> me know about your use of >>> Transcriber and if you are interested! >> I know about TransAG, but my colleagues (we are working only with >> audio) did not find it a viable alternative to the legacy transcriber >> (we are used to the legacy >> interface, shortcuts, ...). >> Moreover we also have several tools that automatically process .trs >> files that are not exported by TransAG. >> >> We are currently using transcriber to transcribe and annotate audio >> streams (mostly children interaction with a robot). >> >> I have very few time, but I will be more than happy to contribute to >> Transcriber (and eventually TransAG). Do you think it would be >> possible to convert the current >> repository to a git-based repository? I think it is much more >> convenient to use than CVS. >> >> Bests, >> Giulio. >> >>> Le 06/08/13 17:36, Giulio Paci a écrit : >>>> Dear Transcriber Team, >>>> during the last year I have written several patches that I would >>>> like to see included in transcriber. >>>> Is it possible? Is it possible that a new bug-fix release of the >>>> legacy transcriber will be released in future? >>>> >>>> Attached are the patches that I think are ready to be included, they >>>> apply (in order) cleanly to the latest release on sourceforge. >>>> >>>> Bests, >>>> Giulio. >>>> >>>> > |
|
From: Giulio P. <giu...@gm...> - 2013-09-13 13:42:41
|
Hi Claude, I was curious about how to migrate a CVS repository to git, so I tried to migrate the current transcriber CVS repository. I used cvs2git to do the first conversion, then I manually replaced user names in the files generated by cvs2git, then I imported those files in a git repository and finally I cloned the repository. The two latest steps were to remove CVSROOT, to move transcriber content to the main directory of the repository and to rename the tags. I achieved this with: # CVSROOT removal git filter-branch -f --force --index-filter 'git rm -rf --cached --ignore-unmatch CVSROOT' --prune-empty --tag-name-filter cat -- --all rm -rf .git/refs/original/; git reflog expire --expire=now --all; git gc --prune=now; git gc --aggressive --prune=now # move transcriber content git filter-branch -f --force --index-filter --tree-filter 'if test -d transcriber; then (ls -d transcriber/*; echo .) | xargs mv ;fi' --prune-empty --tag-name-filter cat -- --all rm -rf .git/refs/original/; git reflog expire --expire=now --all; git gc --prune=now; git gc --aggressive --prune=now and finally manual tag renaming. The result is in https://github.com/giuliopaci/transcriber You can browse the history here: https://github.com/giuliopaci/transcriber/commits Maybe you can use this repository to migrate the old CVS repository on sourceforge to git. Bests, Giulio. On 11/09/2013 14:40, Giulio Paci wrote: > Hi Claude, > any news? > > Bests, > Giulio. > > On 29/08/2013 17:45, Claude Barras wrote: >> Hi, this is a good idea; I have also been using git for recent projects >> and I will have a look at the switch. >> Best, >> Claude >> >> >> Le 29/08/13 00:01, Giulio Paci a écrit : >>> Il 26/08/2013 15:44, Claude Barras ha scritto: >>>> Thanks a lot for your contribution! As a matter of fact, updating the >>>> legacy Transcriber is long overdue (and binaries for modern versions >>>> of Windows and MacOS are >>>> missing), because of lacking time and resource. A newer C++ version >>>> (TransAG) has been developped in between even if it is currently not >>>> very active either. >>>> But if you can invest some time on it, you could become developer >>>> member on the Sourceforge site and include your updates yourself? Let >>>> me know about your use of >>>> Transcriber and if you are interested! >>> I know about TransAG, but my colleagues (we are working only with >>> audio) did not find it a viable alternative to the legacy transcriber >>> (we are used to the legacy >>> interface, shortcuts, ...). >>> Moreover we also have several tools that automatically process .trs >>> files that are not exported by TransAG. >>> >>> We are currently using transcriber to transcribe and annotate audio >>> streams (mostly children interaction with a robot). >>> >>> I have very few time, but I will be more than happy to contribute to >>> Transcriber (and eventually TransAG). Do you think it would be >>> possible to convert the current >>> repository to a git-based repository? I think it is much more >>> convenient to use than CVS. >>> >>> Bests, >>> Giulio. >>> >>>> Le 06/08/13 17:36, Giulio Paci a écrit : >>>>> Dear Transcriber Team, >>>>> during the last year I have written several patches that I would >>>>> like to see included in transcriber. >>>>> Is it possible? Is it possible that a new bug-fix release of the >>>>> legacy transcriber will be released in future? >>>>> >>>>> Attached are the patches that I think are ready to be included, they >>>>> apply (in order) cleanly to the latest release on sourceforge. >>>>> >>>>> Bests, >>>>> Giulio. >>>>> >>>>> >> > |
|
From: Claude B. <Cla...@li...> - 2013-09-21 09:17:56
|
Hi Giulio, Sorry for the delay answering you, the start of the academic semester has been a bit busy for me... Thanks a lot for your exploration on CVS to Git conversion! I just activated a Git repository on the Sourceforge Transcriber project in addition to the initial CVS and I hope it will work as expected - I don't know if there is a difference between the Sourceforge and Github web interface for Git, anyway it doesn't hurt to have several git repository since it is not centralized. I will probably be able to import directly your project. As far as I remember, the CVS was not left in a stable state, and it would be safer to revert back to the distributed 1.5.1 version (but this can probably be easily handled at Git level). Best, Claude Le 13/09/13 15:42, Giulio Paci a écrit : > Hi Claude, > I was curious about how to migrate a CVS repository to git, so I tried > to migrate the current transcriber CVS repository. > > I used cvs2git to do the first conversion, then I manually replaced user > names in the files generated by cvs2git, then I imported those files in > a git repository and finally I cloned the repository. > > The two latest steps were to remove CVSROOT, to move transcriber content > to the main directory of the repository and to rename the tags. > > I achieved this with: > > # CVSROOT removal > git filter-branch -f --force --index-filter 'git rm -rf --cached > --ignore-unmatch CVSROOT' --prune-empty --tag-name-filter cat -- --all > rm -rf .git/refs/original/; git reflog expire --expire=now --all; git gc > --prune=now; git gc --aggressive --prune=now > > # move transcriber content > git filter-branch -f --force --index-filter --tree-filter 'if test -d > transcriber; then (ls -d transcriber/*; echo .) | xargs mv ;fi' > --prune-empty --tag-name-filter cat -- --all > rm -rf .git/refs/original/; git reflog expire --expire=now --all; git gc > --prune=now; git gc --aggressive --prune=now > > and finally manual tag renaming. > > The result is in https://github.com/giuliopaci/transcriber > > You can browse the history here: > https://github.com/giuliopaci/transcriber/commits > > Maybe you can use this repository to migrate the old CVS repository on > sourceforge to git. > > Bests, > Giulio. > > On 11/09/2013 14:40, Giulio Paci wrote: >> Hi Claude, >> any news? >> >> Bests, >> Giulio. >> >> On 29/08/2013 17:45, Claude Barras wrote: >>> Hi, this is a good idea; I have also been using git for recent projects >>> and I will have a look at the switch. >>> Best, >>> Claude >>> >>> >>> Le 29/08/13 00:01, Giulio Paci a écrit : >>>> Il 26/08/2013 15:44, Claude Barras ha scritto: >>>>> Thanks a lot for your contribution! As a matter of fact, updating the >>>>> legacy Transcriber is long overdue (and binaries for modern versions >>>>> of Windows and MacOS are >>>>> missing), because of lacking time and resource. A newer C++ version >>>>> (TransAG) has been developped in between even if it is currently not >>>>> very active either. >>>>> But if you can invest some time on it, you could become developer >>>>> member on the Sourceforge site and include your updates yourself? Let >>>>> me know about your use of >>>>> Transcriber and if you are interested! >>>> I know about TransAG, but my colleagues (we are working only with >>>> audio) did not find it a viable alternative to the legacy transcriber >>>> (we are used to the legacy >>>> interface, shortcuts, ...). >>>> Moreover we also have several tools that automatically process .trs >>>> files that are not exported by TransAG. >>>> >>>> We are currently using transcriber to transcribe and annotate audio >>>> streams (mostly children interaction with a robot). >>>> >>>> I have very few time, but I will be more than happy to contribute to >>>> Transcriber (and eventually TransAG). Do you think it would be >>>> possible to convert the current >>>> repository to a git-based repository? I think it is much more >>>> convenient to use than CVS. >>>> >>>> Bests, >>>> Giulio. >>>> >>>>> Le 06/08/13 17:36, Giulio Paci a écrit : >>>>>> Dear Transcriber Team, >>>>>> during the last year I have written several patches that I would >>>>>> like to see included in transcriber. >>>>>> Is it possible? Is it possible that a new bug-fix release of the >>>>>> legacy transcriber will be released in future? >>>>>> >>>>>> Attached are the patches that I think are ready to be included, they >>>>>> apply (in order) cleanly to the latest release on sourceforge. >>>>>> >>>>>> Bests, >>>>>> Giulio. >>>>>> >>>>>> -- LIMSI-CNRS tel: +33 1 69 85 81 84 bat. 508, BP 133 fax: +33 1 69 85 80 88 Univ Paris-Sud 91403 Orsay cedex France web: http://www.limsi.fr/Individu/barras/ |
|
From: Giulio P. <giu...@gm...> - 2013-09-23 13:45:36
|
Hi Claude, On 21/09/2013 11:17, Claude Barras wrote: > Thanks a lot for your exploration on CVS to Git conversion! I just > activated a Git repository on the Sourceforge Transcriber project in > addition to the initial CVS and I hope it will work as expected - I > don't know if there is a difference between the Sourceforge and Github > web interface for Git, anyway it doesn't hurt to have several git > repository since it is not centralized. There are differences in the web interface, but no difference as long as it concerns git. I have never used the sourceforge interface, but if it allows for better integration with what is already in place, I will use it instead of the one on github. > I will probably be able to import directly your project. Yes it should be easy to do. > As far as I > remember, the CVS was not left in a stable state, and it would be safer > to revert back to the distributed 1.5.1 version (but this can probably > be easily handled at Git level). I will try to do that in Git as soon as you populate the repository on sourceforge (e.g., by importing my repository). By the way, what about setting up a repository for transag as well? I think it will help very much collecting patches from outside and fixing issues. Bests, Giulio. > Le 13/09/13 15:42, Giulio Paci a écrit : >> Hi Claude, >> I was curious about how to migrate a CVS repository to git, so I >> tried >> to migrate the current transcriber CVS repository. >> >> I used cvs2git to do the first conversion, then I manually replaced user >> names in the files generated by cvs2git, then I imported those files in >> a git repository and finally I cloned the repository. >> >> The two latest steps were to remove CVSROOT, to move transcriber content >> to the main directory of the repository and to rename the tags. >> >> I achieved this with: >> >> # CVSROOT removal >> git filter-branch -f --force --index-filter 'git rm -rf --cached >> --ignore-unmatch CVSROOT' --prune-empty --tag-name-filter cat -- --all >> rm -rf .git/refs/original/; git reflog expire --expire=now --all; git gc >> --prune=now; git gc --aggressive --prune=now >> >> # move transcriber content >> git filter-branch -f --force --index-filter --tree-filter 'if test -d >> transcriber; then (ls -d transcriber/*; echo .) | xargs mv ;fi' >> --prune-empty --tag-name-filter cat -- --all >> rm -rf .git/refs/original/; git reflog expire --expire=now --all; git gc >> --prune=now; git gc --aggressive --prune=now >> >> and finally manual tag renaming. >> >> The result is in https://github.com/giuliopaci/transcriber >> >> You can browse the history here: >> https://github.com/giuliopaci/transcriber/commits >> >> Maybe you can use this repository to migrate the old CVS repository on >> sourceforge to git. >> >> Bests, >> Giulio. >> >> On 11/09/2013 14:40, Giulio Paci wrote: >>> Hi Claude, >>> any news? >>> >>> Bests, >>> Giulio. >>> >>> On 29/08/2013 17:45, Claude Barras wrote: >>>> Hi, this is a good idea; I have also been using git for recent projects >>>> and I will have a look at the switch. >>>> Best, >>>> Claude >>>> >>>> >>>> Le 29/08/13 00:01, Giulio Paci a écrit : >>>>> Il 26/08/2013 15:44, Claude Barras ha scritto: >>>>>> Thanks a lot for your contribution! As a matter of fact, updating the >>>>>> legacy Transcriber is long overdue (and binaries for modern versions >>>>>> of Windows and MacOS are >>>>>> missing), because of lacking time and resource. A newer C++ version >>>>>> (TransAG) has been developped in between even if it is currently not >>>>>> very active either. >>>>>> But if you can invest some time on it, you could become developer >>>>>> member on the Sourceforge site and include your updates yourself? Let >>>>>> me know about your use of >>>>>> Transcriber and if you are interested! >>>>> I know about TransAG, but my colleagues (we are working only with >>>>> audio) did not find it a viable alternative to the legacy transcriber >>>>> (we are used to the legacy >>>>> interface, shortcuts, ...). >>>>> Moreover we also have several tools that automatically process .trs >>>>> files that are not exported by TransAG. >>>>> >>>>> We are currently using transcriber to transcribe and annotate audio >>>>> streams (mostly children interaction with a robot). >>>>> >>>>> I have very few time, but I will be more than happy to contribute to >>>>> Transcriber (and eventually TransAG). Do you think it would be >>>>> possible to convert the current >>>>> repository to a git-based repository? I think it is much more >>>>> convenient to use than CVS. >>>>> >>>>> Bests, >>>>> Giulio. >>>>> >>>>>> Le 06/08/13 17:36, Giulio Paci a écrit : >>>>>>> Dear Transcriber Team, >>>>>>> during the last year I have written several patches that I >>>>>>> would >>>>>>> like to see included in transcriber. >>>>>>> Is it possible? Is it possible that a new bug-fix release of the >>>>>>> legacy transcriber will be released in future? >>>>>>> >>>>>>> Attached are the patches that I think are ready to be included, they >>>>>>> apply (in order) cleanly to the latest release on sourceforge. >>>>>>> >>>>>>> Bests, >>>>>>> Giulio. >>>>>>> >>>>>>> > |
|
From: Claude B. <Cla...@li...> - 2013-11-10 23:15:12
|
Dear Giulio, With some delay I finally did the import from your CVS conversion on Github to Sourceforge and everything went very smoothly. Thanks a lot for your help on that issue! Now the code is in order here: https://sourceforge.net/p/trans/git/ci/master/tree/ I took this occasion for including my own modifications floating around for a few years (export .trs fragment, video playback with mplayer) + I disabled the database explorer by default (it made my implementation crash, this needs some further checkings) and reverted back to the standard classic theme for limiting the change. So I think this is a good (re)-starting point. If you have a sourceforge account, I will add you as developer? Best, Claude Le 23/09/13 15:45, Giulio Paci a écrit : > Hi Claude, > > On 21/09/2013 11:17, Claude Barras wrote: >> Thanks a lot for your exploration on CVS to Git conversion! I just >> activated a Git repository on the Sourceforge Transcriber project in >> addition to the initial CVS and I hope it will work as expected - I >> don't know if there is a difference between the Sourceforge and Github >> web interface for Git, anyway it doesn't hurt to have several git >> repository since it is not centralized. > There are differences in the web interface, but no difference as long as > it concerns git. > I have never used the sourceforge interface, but if it allows for better > integration with what is already in place, I will use it instead of the > one on github. > >> I will probably be able to import directly your project. > Yes it should be easy to do. > >> As far as I >> remember, the CVS was not left in a stable state, and it would be safer >> to revert back to the distributed 1.5.1 version (but this can probably >> be easily handled at Git level). > I will try to do that in Git as soon as you populate the repository on > sourceforge (e.g., by importing my repository). > > > By the way, what about setting up a repository for transag as well? > I think it will help very much collecting patches from outside and > fixing issues. > > Bests, > Giulio. > >> Le 13/09/13 15:42, Giulio Paci a écrit : >>> Hi Claude, >>> I was curious about how to migrate a CVS repository to git, so I >>> tried >>> to migrate the current transcriber CVS repository. >>> >>> I used cvs2git to do the first conversion, then I manually replaced user >>> names in the files generated by cvs2git, then I imported those files in >>> a git repository and finally I cloned the repository. >>> >>> The two latest steps were to remove CVSROOT, to move transcriber content >>> to the main directory of the repository and to rename the tags. >>> >>> I achieved this with: >>> >>> # CVSROOT removal >>> git filter-branch -f --force --index-filter 'git rm -rf --cached >>> --ignore-unmatch CVSROOT' --prune-empty --tag-name-filter cat -- --all >>> rm -rf .git/refs/original/; git reflog expire --expire=now --all; git gc >>> --prune=now; git gc --aggressive --prune=now >>> >>> # move transcriber content >>> git filter-branch -f --force --index-filter --tree-filter 'if test -d >>> transcriber; then (ls -d transcriber/*; echo .) | xargs mv ;fi' >>> --prune-empty --tag-name-filter cat -- --all >>> rm -rf .git/refs/original/; git reflog expire --expire=now --all; git gc >>> --prune=now; git gc --aggressive --prune=now >>> >>> and finally manual tag renaming. >>> >>> The result is in https://github.com/giuliopaci/transcriber >>> >>> You can browse the history here: >>> https://github.com/giuliopaci/transcriber/commits >>> >>> Maybe you can use this repository to migrate the old CVS repository on >>> sourceforge to git. >>> >>> Bests, >>> Giulio. >>> >>> On 11/09/2013 14:40, Giulio Paci wrote: >>>> Hi Claude, >>>> any news? >>>> >>>> Bests, >>>> Giulio. >>>> >>>> On 29/08/2013 17:45, Claude Barras wrote: >>>>> Hi, this is a good idea; I have also been using git for recent projects >>>>> and I will have a look at the switch. >>>>> Best, >>>>> Claude >>>>> >>>>> >>>>> Le 29/08/13 00:01, Giulio Paci a écrit : >>>>>> Il 26/08/2013 15:44, Claude Barras ha scritto: >>>>>>> Thanks a lot for your contribution! As a matter of fact, updating the >>>>>>> legacy Transcriber is long overdue (and binaries for modern versions >>>>>>> of Windows and MacOS are >>>>>>> missing), because of lacking time and resource. A newer C++ version >>>>>>> (TransAG) has been developped in between even if it is currently not >>>>>>> very active either. >>>>>>> But if you can invest some time on it, you could become developer >>>>>>> member on the Sourceforge site and include your updates yourself? Let >>>>>>> me know about your use of >>>>>>> Transcriber and if you are interested! >>>>>> I know about TransAG, but my colleagues (we are working only with >>>>>> audio) did not find it a viable alternative to the legacy transcriber >>>>>> (we are used to the legacy >>>>>> interface, shortcuts, ...). >>>>>> Moreover we also have several tools that automatically process .trs >>>>>> files that are not exported by TransAG. >>>>>> >>>>>> We are currently using transcriber to transcribe and annotate audio >>>>>> streams (mostly children interaction with a robot). >>>>>> >>>>>> I have very few time, but I will be more than happy to contribute to >>>>>> Transcriber (and eventually TransAG). Do you think it would be >>>>>> possible to convert the current >>>>>> repository to a git-based repository? I think it is much more >>>>>> convenient to use than CVS. >>>>>> >>>>>> Bests, >>>>>> Giulio. >>>>>> >>>>>>> Le 06/08/13 17:36, Giulio Paci a écrit : >>>>>>>> Dear Transcriber Team, >>>>>>>> during the last year I have written several patches that I >>>>>>>> would >>>>>>>> like to see included in transcriber. >>>>>>>> Is it possible? Is it possible that a new bug-fix release of the >>>>>>>> legacy transcriber will be released in future? >>>>>>>> >>>>>>>> Attached are the patches that I think are ready to be included, they >>>>>>>> apply (in order) cleanly to the latest release on sourceforge. >>>>>>>> >>>>>>>> Bests, >>>>>>>> Giulio. >>>>>>>> >>>>>>>> |
|
From: Giulio P. <giu...@gm...> - 2013-11-13 19:35:53
|
Hi to all, here are a few updates about an issue I reported in a previous email. I will put further updates here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728833 without duplicating the bug issue. On 13/11/2013 16:02, Claude Barras wrote: > Le 13/11/13 13:16, Giulio Paci a écrit : >> On 11/11/2013 00:01, Claude Barras wrote: >> with tcl/tk 8.5, the waveform is not displayed anymore. I am investigating the >> issue > I know that there are compatibility issues between tcLex and Tcl/Tk 8.5. These has been solved in Debian and now it is possible to use tcLex with Tcl/Tk 8.5. > Concerning the waveform not displaying, I didn't observe it myself with > Tcl/Tk8.4, but I was once suggested to add a definition to > gcValues.line_width in src/wavfm.c > I just put it in the git repo > (https://sourceforge.net/p/trans/git/ci/master/tree/src/wavfm.c line > 501) in case it helps > (I also update src/axis.c and src/segmt.c accordingly). It may solve > this issue? No, it will not solve the issue. I was able to identify the problem (I guess): the problem is that in src/wavfm.c (and in src/segmt.c) transcriber is checking ".specFlags & TK_CONFIG_OPTION_SPECIFIED" that with Tcl/Tk 8.5 and above is always returning false. I was not yet able to understand how to properly fix the code, but this is supposed to be the main issue. Bests, Giulio. |
|
From: Claude B. <Cla...@li...> - 2013-11-13 20:57:32
|
Le 13/11/13 20:35, Giulio Paci a écrit : > Hi to all, > here are a few updates about an issue I reported in a previous email. > > I will put further updates here: > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728833 > without duplicating the bug issue. > > On 13/11/2013 16:02, Claude Barras wrote: >> Le 13/11/13 13:16, Giulio Paci a écrit : >>> On 11/11/2013 00:01, Claude Barras wrote: >>> with tcl/tk 8.5, the waveform is not displayed anymore. I am investigating the >>> issue >> I know that there are compatibility issues between tcLex and Tcl/Tk 8.5. > These has been solved in Debian and now it is possible to use tcLex with > Tcl/Tk 8.5. great ! >> Concerning the waveform not displaying, I didn't observe it myself with >> Tcl/Tk8.4, but I was once suggested to add a definition to >> gcValues.line_width in src/wavfm.c >> I just put it in the git repo >> (https://sourceforge.net/p/trans/git/ci/master/tree/src/wavfm.c line >> 501) in case it helps >> (I also update src/axis.c and src/segmt.c accordingly). It may solve >> this issue? > No, it will not solve the issue. I was able to identify the problem (I > guess): the problem is that in src/wavfm.c (and in src/segmt.c) > transcriber is checking > > ".specFlags & TK_CONFIG_OPTION_SPECIFIED" > > that with Tcl/Tk 8.5 and above is always returning false. > I was not yet able to understand how to properly fix the code, but this > is supposed to be the main issue. OK, I updated src/wavfm.c and src/segmt.c so that they do not rely on this deprecated flag any more. Best, Claude |
|
From: Giulio P. <giu...@gm...> - 2013-11-14 20:09:33
|
On 13/11/2013 21:57, Claude Barras wrote: > Le 13/11/13 20:35, Giulio Paci a écrit : >> I was able to identify the problem (I >> guess): the problem is that in src/wavfm.c (and in src/segmt.c) >> transcriber is checking >> >> ".specFlags & TK_CONFIG_OPTION_SPECIFIED" >> >> that with Tcl/Tk 8.5 and above is always returning false. >> I was not yet able to understand how to properly fix the code, but this >> is supposed to be the main issue. > OK, I updated src/wavfm.c and src/segmt.c so that they do not rely on > this deprecated flag any more. Ok, apparently this solved the issue on my system. Thank you very much. Now I will proceed importing changes from the Debian package into the transcriber repository. Cheers, Giulio. |
|
From: Claude B. <Cla...@li...> - 2013-11-14 21:40:26
|
Le 14/11/13 21:09, Giulio Paci a écrit : > On 13/11/2013 21:57, Claude Barras wrote: >> Le 13/11/13 20:35, Giulio Paci a écrit : >>> I was able to identify the problem (I >>> guess): the problem is that in src/wavfm.c (and in src/segmt.c) >>> transcriber is checking >>> >>> ".specFlags & TK_CONFIG_OPTION_SPECIFIED" >>> >>> that with Tcl/Tk 8.5 and above is always returning false. >>> I was not yet able to understand how to properly fix the code, but this >>> is supposed to be the main issue. >> OK, I updated src/wavfm.c and src/segmt.c so that they do not rely on >> this deprecated flag any more. > Ok, apparently this solved the issue on my system. > Thank you very much. > > Now I will proceed importing changes from the Debian package into the > transcriber repository. > > Cheers, > Giulio. Great! Thanks, Claude |
|
From: Giulio P. <giu...@gm...> - 2013-11-13 12:16:58
|
On 11/11/2013 00:01, Claude Barras wrote: > Dear Giulio, > With some delay I finally did the import from your CVS conversion on > Github to Sourceforge and everything went very smoothly. Thanks a lot > for your help on that issue! > Now the code is in order here: > https://sourceforge.net/p/trans/git/ci/master/tree/ > I took this occasion for including my own modifications floating around > for a few years (export .trs fragment, video playback with mplayer) + I > disabled the database explorer by default (it made my implementation > crash, this needs some further checkings) and reverted back to the > standard classic theme for limiting the change. > So I think this is a good (re)-starting point. Very good. I will check them as soon as possible, but I am trying to fix an issue that I have found an issue with the version of transcriber that is currently in Debian: with tcl/tk 8.5 and recent versions of tclex and snack2, the waveform is not displayed anymore. I am investigating the issue, but, up to now, without any luck. Do you have any suggestion? > If you have a sourceforge account, I will add you as developer? My sourceforge username is "giuliopaci". Bests, Giulio. > Le 23/09/13 15:45, Giulio Paci a écrit : >> Hi Claude, >> >> On 21/09/2013 11:17, Claude Barras wrote: >>> Thanks a lot for your exploration on CVS to Git conversion! I just >>> activated a Git repository on the Sourceforge Transcriber project in >>> addition to the initial CVS and I hope it will work as expected - I >>> don't know if there is a difference between the Sourceforge and Github >>> web interface for Git, anyway it doesn't hurt to have several git >>> repository since it is not centralized. >> There are differences in the web interface, but no difference as long as >> it concerns git. >> I have never used the sourceforge interface, but if it allows for better >> integration with what is already in place, I will use it instead of the >> one on github. >> >>> I will probably be able to import directly your project. >> Yes it should be easy to do. >> >>> As far as I >>> remember, the CVS was not left in a stable state, and it would be safer >>> to revert back to the distributed 1.5.1 version (but this can probably >>> be easily handled at Git level). >> I will try to do that in Git as soon as you populate the repository on >> sourceforge (e.g., by importing my repository). >> >> >> By the way, what about setting up a repository for transag as well? >> I think it will help very much collecting patches from outside and >> fixing issues. >> >> Bests, >> Giulio. >> >>> Le 13/09/13 15:42, Giulio Paci a écrit : >>>> Hi Claude, >>>> I was curious about how to migrate a CVS repository to git, so I >>>> tried >>>> to migrate the current transcriber CVS repository. >>>> >>>> I used cvs2git to do the first conversion, then I manually replaced >>>> user >>>> names in the files generated by cvs2git, then I imported those files in >>>> a git repository and finally I cloned the repository. >>>> >>>> The two latest steps were to remove CVSROOT, to move transcriber >>>> content >>>> to the main directory of the repository and to rename the tags. >>>> >>>> I achieved this with: >>>> >>>> # CVSROOT removal >>>> git filter-branch -f --force --index-filter 'git rm -rf --cached >>>> --ignore-unmatch CVSROOT' --prune-empty --tag-name-filter cat -- --all >>>> rm -rf .git/refs/original/; git reflog expire --expire=now --all; >>>> git gc >>>> --prune=now; git gc --aggressive --prune=now >>>> >>>> # move transcriber content >>>> git filter-branch -f --force --index-filter --tree-filter 'if test -d >>>> transcriber; then (ls -d transcriber/*; echo .) | xargs mv ;fi' >>>> --prune-empty --tag-name-filter cat -- --all >>>> rm -rf .git/refs/original/; git reflog expire --expire=now --all; >>>> git gc >>>> --prune=now; git gc --aggressive --prune=now >>>> >>>> and finally manual tag renaming. >>>> >>>> The result is in https://github.com/giuliopaci/transcriber >>>> >>>> You can browse the history here: >>>> https://github.com/giuliopaci/transcriber/commits >>>> >>>> Maybe you can use this repository to migrate the old CVS repository on >>>> sourceforge to git. >>>> >>>> Bests, >>>> Giulio. >>>> >>>> On 11/09/2013 14:40, Giulio Paci wrote: >>>>> Hi Claude, >>>>> any news? >>>>> >>>>> Bests, >>>>> Giulio. >>>>> >>>>> On 29/08/2013 17:45, Claude Barras wrote: >>>>>> Hi, this is a good idea; I have also been using git for recent >>>>>> projects >>>>>> and I will have a look at the switch. >>>>>> Best, >>>>>> Claude >>>>>> >>>>>> >>>>>> Le 29/08/13 00:01, Giulio Paci a écrit : >>>>>>> Il 26/08/2013 15:44, Claude Barras ha scritto: >>>>>>>> Thanks a lot for your contribution! As a matter of fact, >>>>>>>> updating the >>>>>>>> legacy Transcriber is long overdue (and binaries for modern >>>>>>>> versions >>>>>>>> of Windows and MacOS are >>>>>>>> missing), because of lacking time and resource. A newer C++ version >>>>>>>> (TransAG) has been developped in between even if it is currently >>>>>>>> not >>>>>>>> very active either. >>>>>>>> But if you can invest some time on it, you could become developer >>>>>>>> member on the Sourceforge site and include your updates >>>>>>>> yourself? Let >>>>>>>> me know about your use of >>>>>>>> Transcriber and if you are interested! >>>>>>> I know about TransAG, but my colleagues (we are working only with >>>>>>> audio) did not find it a viable alternative to the legacy >>>>>>> transcriber >>>>>>> (we are used to the legacy >>>>>>> interface, shortcuts, ...). >>>>>>> Moreover we also have several tools that automatically process .trs >>>>>>> files that are not exported by TransAG. >>>>>>> >>>>>>> We are currently using transcriber to transcribe and annotate audio >>>>>>> streams (mostly children interaction with a robot). >>>>>>> >>>>>>> I have very few time, but I will be more than happy to contribute to >>>>>>> Transcriber (and eventually TransAG). Do you think it would be >>>>>>> possible to convert the current >>>>>>> repository to a git-based repository? I think it is much more >>>>>>> convenient to use than CVS. >>>>>>> >>>>>>> Bests, >>>>>>> Giulio. >>>>>>> >>>>>>>> Le 06/08/13 17:36, Giulio Paci a écrit : >>>>>>>>> Dear Transcriber Team, >>>>>>>>> during the last year I have written several patches that I >>>>>>>>> would >>>>>>>>> like to see included in transcriber. >>>>>>>>> Is it possible? Is it possible that a new bug-fix release of the >>>>>>>>> legacy transcriber will be released in future? >>>>>>>>> >>>>>>>>> Attached are the patches that I think are ready to be included, >>>>>>>>> they >>>>>>>>> apply (in order) cleanly to the latest release on sourceforge. >>>>>>>>> >>>>>>>>> Bests, >>>>>>>>> Giulio. >>>>>>>>> >>>>>>>>> |
|
From: Claude B. <Cla...@li...> - 2013-11-13 15:02:17
|
Le 13/11/13 13:16, Giulio Paci a écrit : > On 11/11/2013 00:01, Claude Barras wrote: >> Dear Giulio, >> With some delay I finally did the import from your CVS conversion on >> Github to Sourceforge and everything went very smoothly. Thanks a lot >> for your help on that issue! >> Now the code is in order here: >> https://sourceforge.net/p/trans/git/ci/master/tree/ >> I took this occasion for including my own modifications floating around >> for a few years (export .trs fragment, video playback with mplayer) + I >> disabled the database explorer by default (it made my implementation >> crash, this needs some further checkings) and reverted back to the >> standard classic theme for limiting the change. >> So I think this is a good (re)-starting point. > Very good. I will check them as soon as possible, but I am trying to fix > an issue that I have found an issue with the version of transcriber that > is currently in Debian: with tcl/tk 8.5 and recent versions of tclex and > snack2, the waveform is not displayed anymore. I am investigating the > issue, but, up to now, without any luck. > > Do you have any suggestion? I know that there are compatibility issues between tcLex and Tcl/Tk 8.5. Up to now, as a work around, I just sticked to Tcl8.4 but this puts the additional burden of having a local install of an older Tcl version, which is not great. Another solution would be to just switch from tcLex to a standard XML parser (when Transcriber development started in 1998, XML was still an early recommendation and XML parsing in Tcl was not stabilized, but I believe that the situation has evolved since...) Concerning the waveform not displaying, I didn't observe it myself with Tcl/Tk8.4, but I was once suggested to add a definition to gcValues.line_width in src/wavfm.c I just put it in the git repo (https://sourceforge.net/p/trans/git/ci/master/tree/src/wavfm.c line 501) in case it helps (I also update src/axis.c and src/segmt.c accordingly). It may solve this issue? >> If you have a sourceforge account, I will add you as developer? > My sourceforge username is "giuliopaci". Great, I have you added as developer to the project, I hope it will let you commit your changes. Best, Claude > > Bests, > Giulio. > > >> Le 23/09/13 15:45, Giulio Paci a écrit : >>> Hi Claude, >>> >>> On 21/09/2013 11:17, Claude Barras wrote: >>>> Thanks a lot for your exploration on CVS to Git conversion! I just >>>> activated a Git repository on the Sourceforge Transcriber project in >>>> addition to the initial CVS and I hope it will work as expected - I >>>> don't know if there is a difference between the Sourceforge and Github >>>> web interface for Git, anyway it doesn't hurt to have several git >>>> repository since it is not centralized. >>> There are differences in the web interface, but no difference as long as >>> it concerns git. >>> I have never used the sourceforge interface, but if it allows for better >>> integration with what is already in place, I will use it instead of the >>> one on github. >>> >>>> I will probably be able to import directly your project. >>> Yes it should be easy to do. >>> >>>> As far as I >>>> remember, the CVS was not left in a stable state, and it would be safer >>>> to revert back to the distributed 1.5.1 version (but this can probably >>>> be easily handled at Git level). >>> I will try to do that in Git as soon as you populate the repository on >>> sourceforge (e.g., by importing my repository). >>> >>> >>> By the way, what about setting up a repository for transag as well? >>> I think it will help very much collecting patches from outside and >>> fixing issues. >>> >>> Bests, >>> Giulio. >>> >>>> Le 13/09/13 15:42, Giulio Paci a écrit : >>>>> Hi Claude, >>>>> I was curious about how to migrate a CVS repository to git, so I >>>>> tried >>>>> to migrate the current transcriber CVS repository. >>>>> >>>>> I used cvs2git to do the first conversion, then I manually replaced >>>>> user >>>>> names in the files generated by cvs2git, then I imported those files in >>>>> a git repository and finally I cloned the repository. >>>>> >>>>> The two latest steps were to remove CVSROOT, to move transcriber >>>>> content >>>>> to the main directory of the repository and to rename the tags. >>>>> >>>>> I achieved this with: >>>>> >>>>> # CVSROOT removal >>>>> git filter-branch -f --force --index-filter 'git rm -rf --cached >>>>> --ignore-unmatch CVSROOT' --prune-empty --tag-name-filter cat -- --all >>>>> rm -rf .git/refs/original/; git reflog expire --expire=now --all; >>>>> git gc >>>>> --prune=now; git gc --aggressive --prune=now >>>>> >>>>> # move transcriber content >>>>> git filter-branch -f --force --index-filter --tree-filter 'if test -d >>>>> transcriber; then (ls -d transcriber/*; echo .) | xargs mv ;fi' >>>>> --prune-empty --tag-name-filter cat -- --all >>>>> rm -rf .git/refs/original/; git reflog expire --expire=now --all; >>>>> git gc >>>>> --prune=now; git gc --aggressive --prune=now >>>>> >>>>> and finally manual tag renaming. >>>>> >>>>> The result is in https://github.com/giuliopaci/transcriber >>>>> >>>>> You can browse the history here: >>>>> https://github.com/giuliopaci/transcriber/commits >>>>> >>>>> Maybe you can use this repository to migrate the old CVS repository on >>>>> sourceforge to git. >>>>> >>>>> Bests, >>>>> Giulio. >>>>> >>>>> On 11/09/2013 14:40, Giulio Paci wrote: >>>>>> Hi Claude, >>>>>> any news? >>>>>> >>>>>> Bests, >>>>>> Giulio. >>>>>> >>>>>> On 29/08/2013 17:45, Claude Barras wrote: >>>>>>> Hi, this is a good idea; I have also been using git for recent >>>>>>> projects >>>>>>> and I will have a look at the switch. >>>>>>> Best, >>>>>>> Claude >>>>>>> >>>>>>> >>>>>>> Le 29/08/13 00:01, Giulio Paci a écrit : >>>>>>>> Il 26/08/2013 15:44, Claude Barras ha scritto: >>>>>>>>> Thanks a lot for your contribution! As a matter of fact, >>>>>>>>> updating the >>>>>>>>> legacy Transcriber is long overdue (and binaries for modern >>>>>>>>> versions >>>>>>>>> of Windows and MacOS are >>>>>>>>> missing), because of lacking time and resource. A newer C++ version >>>>>>>>> (TransAG) has been developped in between even if it is currently >>>>>>>>> not >>>>>>>>> very active either. >>>>>>>>> But if you can invest some time on it, you could become developer >>>>>>>>> member on the Sourceforge site and include your updates >>>>>>>>> yourself? Let >>>>>>>>> me know about your use of >>>>>>>>> Transcriber and if you are interested! >>>>>>>> I know about TransAG, but my colleagues (we are working only with >>>>>>>> audio) did not find it a viable alternative to the legacy >>>>>>>> transcriber >>>>>>>> (we are used to the legacy >>>>>>>> interface, shortcuts, ...). >>>>>>>> Moreover we also have several tools that automatically process .trs >>>>>>>> files that are not exported by TransAG. >>>>>>>> >>>>>>>> We are currently using transcriber to transcribe and annotate audio >>>>>>>> streams (mostly children interaction with a robot). >>>>>>>> >>>>>>>> I have very few time, but I will be more than happy to contribute to >>>>>>>> Transcriber (and eventually TransAG). Do you think it would be >>>>>>>> possible to convert the current >>>>>>>> repository to a git-based repository? I think it is much more >>>>>>>> convenient to use than CVS. >>>>>>>> >>>>>>>> Bests, >>>>>>>> Giulio. >>>>>>>> >>>>>>>>> Le 06/08/13 17:36, Giulio Paci a écrit : >>>>>>>>>> Dear Transcriber Team, >>>>>>>>>> during the last year I have written several patches that I >>>>>>>>>> would >>>>>>>>>> like to see included in transcriber. >>>>>>>>>> Is it possible? Is it possible that a new bug-fix release of the >>>>>>>>>> legacy transcriber will be released in future? >>>>>>>>>> >>>>>>>>>> Attached are the patches that I think are ready to be included, >>>>>>>>>> they >>>>>>>>>> apply (in order) cleanly to the latest release on sourceforge. >>>>>>>>>> >>>>>>>>>> Bests, >>>>>>>>>> Giulio. >>>>>>>>>> >>>>>>>>>> > > ------------------------------------------------------------------------------ > DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps > OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access > Free app hosting. Or install the open source package on any LAMP server. > Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! > http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk > _______________________________________________ > Trans-devel mailing list > Tra...@li... > https://lists.sourceforge.net/lists/listinfo/trans-devel -- LIMSI-CNRS tel: +33 1 69 85 81 84 bat. 508, BP 133 fax: +33 1 69 85 80 88 Univ Paris-Sud 91403 Orsay cedex France web: http://www.limsi.fr/Individu/barras/ |
|
From: Giulio P. <giu...@gm...> - 2013-08-12 08:43:17
Attachments:
1001_pt_localization_file.patch
1002_use_snack_sndfile_ext.patch
1003_make_alt_click_expand_signal.patch
1004_fix_trans_file_permissions.patch
1005_avoid_to_put_transcriber_in_background.patch
1006_fix_documentation.patch
1007_fix_html_conversion.patch
1008_update_contacts_and_urls.patch
1009_update_contacts_and_urls_in_doc.patch
1010_fix_cha_export.patch
|
Dear Transcriber Team, during the last year I have written several patches that I would like to see included in transcriber. Is it possible? Is it possible that a new bug-fix release of the legacy transcriber will be released in future? Attached are the patches that I think are ready to be included, they apply (in order) cleanly to the latest release on sourceforge. Bests, Giulio. |
Thanks for helping keep SourceForge clean.
X