I'm Marko from Germany. Just trying the DeltaChat Client with SailfishX and elementary OS 5.0
On elementary I get a error message after the npm start. Anyone the same problem here?
Gesendet mit SailfishX
Please explain the algorithm of delivery of messages: sometimes
they go in one direction for a few seconds, and sometimes this
time is from 5 to 10 minutes. Moreover, the rapid exchange of
messages (question-answer) does not work, or there or back
I want to understand the algorithm in order to communicate the
order of correspondence to their correspondents.
In case you are at the chaos communication conf (35c3)
in Leipzig -- several delta chat folks are hanging out
at !decentral, in hall 2.
Did a session with a bunch (15?) of people yesterday and
managed to get everyone setup with either android, desktop
or ios ... all using development versions even,
version 0.97 of both desktop and android and friedel's
development branch of delta/ios.
Our expert guides dependably work in a state of harmony with the necessities given to us, and this makes our task arrangement a perfect one. We provide best Assignment Help. https://www.allassignmenthelp.com/
tomorrow / monday dec 17th at around 9pm CEST (8pm UTC i think) at
#deltachat on freenode
let's try sync on the following topics:
- state of release work pre-ccc
- 35c3 updates
- needfinding report
in the last 3/4 days I've seen an huge rise of the DeltaChat translation
teams join requests. I've also noticed that many of them (4 pending user
at the moment, 3 Russians and 1 Ukrainian) have all signed up on
Transifex today. I suppose that some of them may be spammers or
something like that. I usually don't approve/deny any non-italian user
because the Language coordinators can do that, but I'm afraid that these
users can do something bad. On the other hand, these user could be real
users that just want to join the project... What should I do in your
opinion? It's better to leave the Language coordinators the choice to
approve/deny the users or it's better to send a message to these users
and see if they reply? Some big projects ask some questions just to be
sure if the users are real users.
we'd like to bootstrap the translations for android-dev and desktop soonish.
- our current plan is to create a new repository that is shared between
all apps then, currently android-dev (will become the normal android)
- source language will be english
- the translations in this repository will be empty initially, however,
afaik, transifex does suggestions also from other repos, so that it
should be rather easy to fill if there is already a similar string eg.
in the old android-version. some additional thoughts about this were
filed at https://github.com/deltachat/interface/issues/8
- there may be some system-specific string; these should be prefixed by
eg. `android_` and `desktop_` - or even `mac_` or `windows_`
- it's not yet clear which file format will be used (xml, json, po,
...), i know of the android-xml format that it supports "complex plural
forms", not sure about the other ones. otoh i've heard from some
translators that .po files may also be handy.
this approach is more effort for the developers as some scripts are
needed, however, it should be much easier for the translators to
maintain the - currently - 5 systems and to keep things consistent.
any suggestions on this are welcome :)
i suggest to discuss this and make a choice about the format in our next
weekly sync meeting - Dec 10 Monday 9pm CEST (8pm UTC) - everyone is
welcome there, esp. translators, of course.
if you cannot make it there and have some ideas, however, you can also
post them to this mailing list.
as Enrico mentioned in an older mail, this mailing list can also be used
for all other translation-depending issues and we'd like to invite all
translators to join it :)
best - cu on monday -,
hi all, today let's do another
freenode #deltachat sync 9pm CEST (8pm UTC)
with at the least the following topics:
- android/desktop translation (see also Bjoern's mail end last week)
- desktop and android release status (including timings of folks involved)
see you later,