mail2voice-devel Mailing List for Mail2Voice (Page 10)

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Hi all,

Remember: our next meeting Wednesday 2014-12-10 will be on our new 
mumble server !

Best regards,
Laurent CLAUDE

Hi all,

No Meeting notes today. Our meeting was canceled.

Next meeting: 2014-12-10.
We'll use Mail2Voice Mumble. I'll send you the connection parameters by PM.

As usual, questions or remarks are welcomed.
Best regards,
Laurent CLAUDE

Hi all,

Meeting notes are available on the project wiki at the following
address:http://wiki.mail2voice.org/doku.php/2014-11-12_meeting_notes

Agenda:
     Capitol du Libre (CdL) : Logistic
     A point on the tasks for beta2
     Capitol du Libre (CdL) : preparation of the conference
     Various topics

As usual, questions or remarks are welcomed.
Best regards,

Laurent CLAUDE

Le 05/11/2014 14:22, Matthieu Hazon a écrit :
> Hi team,
>
> As decided last week, here is my update on the beta 2 work.
>
> * Work done:
> - Translations files have been updated and script enhanced. I will also remove the default.lng file as it is exactly the same as the english.lng file (script will be updated accordingly).
> - Master branch now includes the voice strings so the code now embed all translatable strings.
> - I cleaned up some code and fixed strings in the about box (+ fix to avoid unwanted translation generation for version number, release date and authors' names).
> - Legal notices in source code are now up to date with Diana mentionned in authors section.
> - Additionnally, I provided Diana some support on bugs and software delivery.
>
> * Work in progress:
> - I'm now working on the HTML emails support on separate branch. I hope to have more visibility on this topic this evening to see if it's still feasible for next week.
>
> * Work postponed:
> - FOSDEM submission finalization
> - Locale script correctness fix
> - Update on presentation for Capitole du Libre
>
> That's quite all for now :)
>
>
> Best regards,
>
> Matthieu Hazon
>
Hi all,

Matthieu thank you for initiating this topic.

Let me remind that the actual object is to make the point with respect 
to our objectives of releasea beta forthe CdL.

To begin, I wish you all a big thank you. The work of the Dev team is 
concrete!
And I think our initial goal was pretty decent.

On your side Matthieu, things are clear, I think we reach the goal, or 
almost. That's cool.
On the side of tasks assigned to Diana, the bugtracker is clear. It's 
the same situation. That's cool too.
I'll let you finish the work in progress.

For my part, I mainly focused on communication tasks. The work is long 
and tedious, but it advance.
I also spent time for the preparation of the CdL conference. Work in 
progress ...
... And other tasks (next website and next collaboration tools) which 
will be discussed orally at Toulouse. Yes Matthieu, it's teasing;)

At our next meeting, I will wish that we devote only:
- to release the beta2
- to the preparation of the conference.

Continue like this and we'll be OK for a release!
I'll reiterate my thanks.
See you Wednesday.

Best regards,

Laurent CLAUDE

Hi team,

As decided last week, here is my update on the beta 2 work.

* Work done:
- Translations files have been updated and script enhanced. I will also remove the default.lng file as it is exactly the same as the english.lng file (script will be updated accordingly).
- Master branch now includes the voice strings so the code now embed all translatable strings.
- I cleaned up some code and fixed strings in the about box (+ fix to avoid unwanted translation generation for version number, release date and authors' names).
- Legal notices in source code are now up to date with Diana mentionned in authors section.
- Additionnally, I provided Diana some support on bugs and software delivery.

* Work in progress:
- I'm now working on the HTML emails support on separate branch. I hope to have more visibility on this topic this evening to see if it's still feasible for next week.

* Work postponed:
- FOSDEM submission finalization
- Locale script correctness fix
- Update on presentation for Capitole du Libre

That's quite all for now :)

Best regards,

Matthieu Hazon

Hi all,

Meeting notes are available on the project wiki at the following
address:http://wiki.mail2voice.org/doku.php/2014-10-29_meeting_notes
As usual, questions or remarks are welcomed.

Best regards,

Laurent CLAUDE

Le 28/10/2014 21:02, Laurent CLAUDE a écrit :
> Le 23/10/2014 10:16, Matthieu Hazon a écrit :
>> ----- Mail original -----
>>
>>
>>> You'll can find the abstract below or here :
>>> https://2014.rmll.info/conference245?lang=en
>>> Ok, we'll review it next meeting.
>>> Regards,
>>> Laurent CLAUDE
>> Hmm I know this page, but I thought we also submited an abstract in addition to the intro and description. But the intro we wrote is quite generic so I think I can take this :)
>>
>> Matthieu Hazon
> Hi Matthieu,
>
> I've just think this document. Was this what you were looking for?
> https://lite3.framapad.org/p/m2v/timeslider#1467
>
> Regards,
> Laurent CLAUDE
>
>

Re,
this link doesn't work in direct. You have to play with the timeline, 
and chosse the version 1467 on 2014-04-02.

Regards,
Laurent CLAUDE

Le 23/10/2014 10:16, Matthieu Hazon a écrit :
> ----- Mail original -----
>
>
>> You'll can find the abstract below or here :
>> https://2014.rmll.info/conference245?lang=en
>> Ok, we'll review it next meeting.
>> Regards,
>> Laurent CLAUDE
> Hmm I know this page, but I thought we also submited an abstract in addition to the intro and description. But the intro we wrote is quite generic so I think I can take this :)
>
> Matthieu Hazon
Hi Matthieu,

I've just think this document. Was this what you were looking for?
https://lite3.framapad.org/p/m2v/timeslider#1467

Regards,
Laurent CLAUDE

Le 25/10/2014 17:55, Matthieu Hazon a écrit :
> Hi team,
>
> I just pushed a new branch which contains the work in progress around
> default voice strings integration. For this I added a dictionary in the
> speechObject and two methods: one to add a voice string, and one to
> retrieve such a string. I also fixed some other things that were not
> compatible with the integration (which were architecture design flaws).
> The generator script is also updated so you can now generate the
> complete default locale file.
>
> Don't hesitate to try this branch to see if the default voice strings
> are ok and if nothing is missing.
>
Hi All,

I made a general pass, at first glance this script seems to work.
I did not find any lack, either in words or in string voices.

Good work!

Laurent CLAUDE

Hi team,

I just pushed a new branch which contains the work in progress around 
default voice strings integration. For this I added a dictionary in the 
speechObject and two methods: one to add a voice string, and one to 
retrieve such a string. I also fixed some other things that were not 
compatible with the integration (which were architecture design flaws). 
The generator script is also updated so you can now generate the 
complete default locale file.

Don't hesitate to try this branch to see if the default voice strings 
are ok and if nothing is missing.

Then I will merge on master and update translations.

Best regards,

Matthieu Hazon

----- Mail original ----- 

> You'll can find the abstract below or here :
> https://2014.rmll.info/conference245?lang=en
> Ok, we'll review it next meeting.

> Regards,
> Laurent CLAUDE

Hmm I know this page, but I thought we also submited an abstract in addition to the intro and description. But the intro we wrote is quite generic so I think I can take this :)

Matthieu Hazon

Le 23/10/2014 00:55, Matthieu Hazon a écrit :
> Hi team!
>
> I created an account on the FOSDEM website to register our lighting
> talk. We can modify the entry until 20th of november. Currently, I'm
> just missing the abstract. Laurent, do you still have the abstract we
> wrote for RMLL event? It would be great.
>
> Then I suggest we do a review of the proposal during next meeting.
>
> Best regards,
>
> Matthieu Hazon
>
Hi Matthieu,

Great !
You'll can find the abstract below or here : 
https://2014.rmll.info/conference245?lang=en
Ok, we'll review it next meeting.

Regards,
Laurent CLAUDE

    Conference introduction

Giving back autonomy for using mail to people with cognitive 
disabilities or illiteracy, to elder people or young children.

    About speaker

  * *Name :* Laurent Claude, Matthieu Hazon
  * *URL :* http://www.Mail2Voice.org

      Biography

Laurent CLAUDE is by education an electronic engineer. He met disability 
15 years ago at a corner of his professional life, at the time for 
electronic development and an animator around computers. Today, he 
accompanies people with motor and cognitive disabilities. It is thus 
"from the field" that he wrote Mail2Voice.

Matthieu Hazon is by education a computer science engineer. Convinced by 
free software, he is interested in accessibility since several years and 
decided to contributing to software and accessibility by joining the 
Liberté 0 association and developing for the Mail2Voice project.

    Conference description

Presentation of the Mail2Voice software. Mail2voice is a mail management 
software dedicated to people with cognitive disabilities or illiteracy, 
to elder people or young children.
Mail2Voice uses a simplified graphical interface which permits to use a 
tactile display.
Outgoing messages are handled through audio recording (mp3 attached 
file), incoming messages are read by a speech synthesis, and address 
book contacts are reachable through a photo.

Le 21/10/2014 23:49, Matthieu Hazon a écrit :
> Le 21/10/2014 18:35, Laurent CLAUDE a écrit :
>> As you may have seen, I pushed a script (with better commands :) to the repository last weekend. Currently, this script generates an XML file containing all GUI strings to translate. However, the voice string are not yet included but this is work in progress. More specifically:
>>
>> - Default voices strings are not included in the code -> I'm including them but I have to find an appropriate place. There are some voice stuff in constant.cs but I'm not convinced this is the right place for this. Any idea?
>> - For each voice string, there is an identifier. Identifiers are already in the code but I'm prefixing them with VOICEID_ for better understanding.
>> - I'm thinking to create a Dictionary object to link IDs to voice strings. But same as first point, I don't know where to put this.
>>
>> What are your thoughts? Any suggestion?
>>
>> Matthieu Hazon
>>
>> A little too technical for me ...
>> I do not understand the need to have an extra file.
>> Is it not correct to put the default voices sentences hardcoded in the
>> code? As for the default words?
>>
>> Laurent CLAUDE
> A little misunderstanding here so let me rephrase my thinking.
> Currently, the voice strings are not included in the code but in the
> language files. As you say, the correct way is to have the default voice
> strings embedded somewhere in the code. This is a need because
> Mail2Voice has to work in standalone fine even without extra language file.
>
> I was just pointing an underlying issue that is: which part of the code
> files is the best to put voice strings in? Currently there are some
> voice IDs in the file constants.cs and in some other files. For me, this
> situation is inconsistant. My first intention was to provide a common
> way to store voice strings and link them with voice IDs (through a .Net
> Dictionary object for instance) and my first idea was to centralize all
> the voice IDs and strings in one place. Problem is, I don't think there
> is an appropriate place to do something like this for now (the
> constant.cs file is not the right place).
>
> Another approach would be to provide a central Dictionary, held by the
> speechObject. Then, each GUI part which needs some voices capacities
> register its own voice strings and IDs through the speechObject.
>
> I'm totally open for other options but my main concern is to avoid a
> completely heterogenous voice strings management through the source
> files. We need, one place for the storage and one API to access it.
>
> I'm hope it is more clear now :)
>
> What do you think about this?
>
> Matthieu Hazon
>
Thank you for these technical details.
It's more clear now, but I'm not sure to be very qualified to give a 
helping opinion.

Diana, do you have any idea?

Laurent CLAUDE

Hi team!

I created an account on the FOSDEM website to register our lighting 
talk. We can modify the entry until 20th of november. Currently, I'm 
just missing the abstract. Laurent, do you still have the abstract we 
wrote for RMLL event? It would be great.

Then I suggest we do a review of the proposal during next meeting.

Best regards,

Matthieu Hazon

Le 22/10/2014 21:11, Laurent CLAUDE a écrit :
> Hi team!
>
> I think we sould make a list of our needs in terms of collaboration 
> tools.
> I've just add this page on the wiki: 
> http://wiki.mail2voice.org/doku.php/future_collaboration_tools
>
> I invite you to complete it!
>
> Best regards,
> Laurent CLAUDE

Hi Laurent,

This is a very good idea! I will think about this in the next few days.

Matthieu Hazon

Hi team!

I think we sould make a list of our needs in terms of collaboration tools.
I've just add this page on the wiki: 
http://wiki.mail2voice.org/doku.php/future_collaboration_tools

I invite you to complete it!

Best regards,
Laurent CLAUDE
<http://wiki.mail2voice.org/doku.php/future_development_tools>

Le 21/10/2014 18:23, Laurent CLAUDE a écrit :
> Le 21/10/2014 13:57, Matthieu Hazon a écrit :
>>> Hi all,
>>>
>>> It is indeed an event that we have to consider with importance for
>>> Mail2Voice.
>>> International scope is what sorely lacking in Mail2Voice now.
>>>
>>> I am very supportive of what we are studying our presence at this
>>> event.
>>> And indeed we must hurry.
>>>
>>> Unfortunately I am not a resource to speak in English.
>>> I mean of course participate in the preparation of this task, but ...
>>> who feels able to intervene?
>>>
>>> Many thanks,
>>> Laurent CLAUDE
>>>
>> Hi Laurent, Diana,
>>
>> What I propose is to submit our proposal now. In the worst case, I can speak alone. I guess it's a bit premature for you, Diana, to consider a participation in the talk, but in one or two months, you will be more confident and you may decide to go for it.
>>
>> So, Laurent, do I have greenlight to submit the proposal?
>>
>> Best regards,
>>
>> Matthieu Hazon
> Hi Matthieu, Diana,
>
> Totally agree with you about an intervention by Diana. It's premature.
> The purpose of my post was to get your position explained here. Thank you.
>
> Yes, of course you have my greenlight to the proposal!
>
> Best regards,
> Laurent
Great, I will apply tomorrow and keep you informed about this.

Have a good night,

Matthieu Hazon

Le 21/10/2014 18:35, Laurent CLAUDE a écrit :
> As you may have seen, I pushed a script (with better commands :) to the repository last weekend. Currently, this script generates an XML file containing all GUI strings to translate. However, the voice string are not yet included but this is work in progress. More specifically:
>
> - Default voices strings are not included in the code -> I'm including them but I have to find an appropriate place. There are some voice stuff in constant.cs but I'm not convinced this is the right place for this. Any idea?
> - For each voice string, there is an identifier. Identifiers are already in the code but I'm prefixing them with VOICEID_ for better understanding.
> - I'm thinking to create a Dictionary object to link IDs to voice strings. But same as first point, I don't know where to put this.
>
> What are your thoughts? Any suggestion?
>
> Matthieu Hazon
>
> A little too technical for me ...
> I do not understand the need to have an extra file.
> Is it not correct to put the default voices sentences hardcoded in the
> code? As for the default words?
>
> Laurent CLAUDE

A little misunderstanding here so let me rephrase my thinking. 
Currently, the voice strings are not included in the code but in the 
language files. As you say, the correct way is to have the default voice 
strings embedded somewhere in the code. This is a need because 
Mail2Voice has to work in standalone fine even without extra language file.

I was just pointing an underlying issue that is: which part of the code 
files is the best to put voice strings in? Currently there are some 
voice IDs in the file constants.cs and in some other files. For me, this 
situation is inconsistant. My first intention was to provide a common 
way to store voice strings and link them with voice IDs (through a .Net 
Dictionary object for instance) and my first idea was to centralize all 
the voice IDs and strings in one place. Problem is, I don't think there 
is an appropriate place to do something like this for now (the 
constant.cs file is not the right place).

Another approach would be to provide a central Dictionary, held by the 
speechObject. Then, each GUI part which needs some voices capacities 
register its own voice strings and IDs through the speechObject.

I'm totally open for other options but my main concern is to avoid a 
completely heterogenous voice strings management through the source 
files. We need, one place for the storage and one API to access it.

I'm hope it is more clear now :)

What do you think about this?

Matthieu Hazon

Le 21/10/2014 13:43, Matthieu Hazon a écrit :
> Hi Laurent,
>
> I would like to add an objective for the CdL. If you remember last time in RMLL event, we had a display issue because of bad screen resolution. Could we plan a task on this to make sure we have a beautiful Mail2Voice to show?
>
> Best regards,
>
> Matthieu Hazon
Hi Matthieu,

Of course, we must add this task.
It'll still be a bit tricky, because it is impossible to compile with 
visual studio since we moved to Mono.
So, I do not know if we'll be able to rework the screens before the Cdl...

Regards,
Laurent CLAUDE

Le 21/10/2014 14:23, Matthieu Hazon a écrit :
>
> ----- Mail original -----
>> Hi,
>> great news, because from my side I have not found anything with
>> Visual...
>>
>> Regards,
>> Laurent CLAUDE
>>
>>
>> Le 17/10/2014 14:27, Matthieu Hazon a écrit :
>>> Hi team,
>>>
>>> I now have a debut of script core for locale file generation from
>>> source code. I now have the following perl command (tested in
>>> MinGW shipped with Git under Windows):
>>>
>>> user@xxxx /C/share/Mail2Voice/gui/panels
>>> $ perl -ne '/([a-zA-Z0-9]*).Text *= *"(.*)"/ && print "    <setting
>>> name=\"$1\" value=\"$2\" />\n"' configurationControl.Designer.cs
>
> As you may have seen, I pushed a script (with better commands :) to the repository last weekend. Currently, this script generates an XML file containing all GUI strings to translate. However, the voice string are not yet included but this is work in progress. More specifically:
>
> - Default voices strings are not included in the code -> I'm including them but I have to find an appropriate place. There are some voice stuff in constant.cs but I'm not convinced this is the right place for this. Any idea?
> - For each voice string, there is an identifier. Identifiers are already in the code but I'm prefixing them with VOICEID_ for better understanding.
> - I'm thinking to create a Dictionary object to link IDs to voice strings. But same as first point, I don't know where to put this.
>
> What are your thoughts? Any suggestion?
>
> Matthieu Hazon
>
A little too technical for me ...
I do not understand the need to have an extra file.
Is it not correct to put the default voices sentences hardcoded in the 
code? As for the default words?

Laurent CLAUDE

Le 21/10/2014 13:57, Matthieu Hazon a écrit :
>> Hi all,
>>
>> It is indeed an event that we have to consider with importance for
>> Mail2Voice.
>> International scope is what sorely lacking in Mail2Voice now.
>>
>> I am very supportive of what we are studying our presence at this
>> event.
>> And indeed we must hurry.
>>
>> Unfortunately I am not a resource to speak in English.
>> I mean of course participate in the preparation of this task, but ...
>> who feels able to intervene?
>>
>> Many thanks,
>> Laurent CLAUDE
>>
> Hi Laurent, Diana,
>
> What I propose is to submit our proposal now. In the worst case, I can speak alone. I guess it's a bit premature for you, Diana, to consider a participation in the talk, but in one or two months, you will be more confident and you may decide to go for it.
>
> So, Laurent, do I have greenlight to submit the proposal?
>
> Best regards,
>
> Matthieu Hazon
Hi Matthieu, Diana,

Totally agree with you about an intervention by Diana. It's premature.
The purpose of my post was to get your position explained here. Thank you.

Yes, of course you have my greenlight to the proposal!

Best regards,
Laurent

----- Mail original -----
> 
> Hi,
> great news, because from my side I have not found anything with
> Visual...
> 
> Regards,
> Laurent CLAUDE
> 
> 
> Le 17/10/2014 14:27, Matthieu Hazon a écrit :
> > Hi team,
> >
> > I now have a debut of script core for locale file generation from
> > source code. I now have the following perl command (tested in
> > MinGW shipped with Git under Windows):
> >
> > user@xxxx /C/share/Mail2Voice/gui/panels
> > $ perl -ne '/([a-zA-Z0-9]*).Text *= *"(.*)"/ && print "    <setting
> > name=\"$1\" value=\"$2\" />\n"' configurationControl.Designer.cs

As you may have seen, I pushed a script (with better commands :) to the repository last weekend. Currently, this script generates an XML file containing all GUI strings to translate. However, the voice string are not yet included but this is work in progress. More specifically:

- Default voices strings are not included in the code -> I'm including them but I have to find an appropriate place. There are some voice stuff in constant.cs but I'm not convinced this is the right place for this. Any idea?
- For each voice string, there is an identifier. Identifiers are already in the code but I'm prefixing them with VOICEID_ for better understanding.
- I'm thinking to create a Dictionary object to link IDs to voice strings. But same as first point, I don't know where to put this.

What are your thoughts? Any suggestion?

Matthieu Hazon

> Hi all,
> 
> It is indeed an event that we have to consider with importance for
> Mail2Voice.
> International scope is what sorely lacking in Mail2Voice now.
> 
> I am very supportive of what we are studying our presence at this
> event.
> And indeed we must hurry.
> 
> Unfortunately I am not a resource to speak in English.
> I mean of course participate in the preparation of this task, but ...
> who feels able to intervene?
> 
> Many thanks,
> Laurent CLAUDE
> 

Hi Laurent, Diana,

What I propose is to submit our proposal now. In the worst case, I can speak alone. I guess it's a bit premature for you, Diana, to consider a participation in the talk, but in one or two months, you will be more confident and you may decide to go for it.

So, Laurent, do I have greenlight to submit the proposal?

Best regards,

Matthieu Hazon

Hi Laurent,

I would like to add an objective for the CdL. If you remember last time in RMLL event, we had a display issue because of bad screen resolution. Could we plan a task on this to make sure we have a beautiful Mail2Voice to show?

Best regards,

Matthieu Hazon

Hi Diana,

This is great news! Thanks a lot.
So we have some good evenings work ahead of us;-) We will make a point 
next week.

Best regards,
Laurent

Le 19/10/2014 11:14, Diana Ibanescu a écrit :
> Hello Laurent,
>
> I've looked in the bug tracker and I think the tasks assigned to me 
> seem to be reasonable to finish them in this release. I don't know to 
> estimate very precisely because I don't have a very clearly view of 
> the components, but I'll try to do all the best to finish them in time ;-)
>
> Best regards,
> Diana
>
> 2014-10-15 23:56 GMT+02:00 Laurent CLAUDE <lau...@fr... 
> <mailto:lau...@fr...>>:
>
>     Hi Diana, Hi Matthieu,
>     Already: Diana thank you for your participation tonight in spite
>     of your health.
>
>     Diana, I'm sorry to inform you of this through that channel, but
>     with Matthieu we had a bright idea tonight ;-)
>
>     Indeed, at the end of our meeting today we discussed whether to
>     publish a beta 2 before the "Capitol du Libre."
>     Beyond simply want to come up with a new version, the challenges
>     are many:
>     - Invite contributions from translators
>     - To show that we are really active (compared to Montpellier in July)
>     - To show that the project grown gradually, especially also
>     because now you're here(and it will be for us the oportunity,
>     during the conference, to present you as a full member of the
>     project)
>
>     Release a beta 2 and complete all current tasks bugtracker are two
>     different things.
>     We can still decide what should be done to achieve this goal.
>     This imposes certain constraints, and we all three need to engage
>     ourselves on the feasibility of this goal.
>
>     We had theopportunity with Matthieu to defining engagements. But
>     knowing you least, here's my question: On what are you able to
>     hire you?
>     I realize that the hardest part for you is to dive into the code,
>     rather than to carry out the tasks.
>     But I'd like you to list the work you could accomplish, given the
>     time allotted to us.
>
>     So, Diana, what do you think of this goal work?
>
>     Many thanks
>     Laurent
>
>     ------------------------------------------------------------------------------
>     Comprehensive Server Monitoring with Site24x7.
>     Monitor 10 servers for $9/Month.
>     Get alerted through email, SMS, voice calls or mobile push
>     notifications.
>     Take corrective actions from your mobile device.
>     http://p.sf.net/sfu/Zoho
>     _______________________________________________
>     Mail2voice-devel mailing list
>     Mai...@li...
>     <mailto:Mai...@li...>
>     https://lists.sourceforge.net/lists/listinfo/mail2voice-devel
>
>

2013	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug (1)	Sep (9)	Oct (11)	Nov (10)	Dec (1)
2014	Jan (8)	Feb (2)	Mar (5)	Apr (3)	May (2)	Jun (3)	Jul (3)	Aug (3)	Sep (5)	Oct (29)	Nov (4)	Dec (17)
2015	Jan (9)	Feb (7)	Mar (23)	Apr (7)	May (8)	Jun (4)	Jul (1)	Aug (4)	Sep (3)	Oct (2)	Nov (3)	Dec (1)
2016	Jan (9)	Feb (11)	Mar (9)	Apr (3)	May (3)	Jun (3)	Jul (2)	Aug (3)	Sep (4)	Oct (2)	Nov (2)	Dec (3)
2017	Jan (7)	Feb (23)	Mar (25)	Apr (13)	May (12)	Jun (2)	Jul	Aug (1)	Sep	Oct	Nov	Dec

mail2voice-devel Mailing List for Mail2Voice (Page 10)

E-Mail software for people with cognitive impairment and illiteracy.

mail2voice-devel — Development mailing list