Bitte um Hilfe: Aard2 findet .slob file nicht

[Wolf Haberbosch]

Hallo zusammen,

irgendwie stehe ich auf dem Schlauch. Ich habe seit ca. 6 Wochen ein Oneplus One (64GB,Aandroid 4.4.4), auf dem ich zunächst Aard Dictionary v. 1.6.11 installiert hatte mit den files dewiki-20140911.1_of_3.aar, dewiki-20140911.2_of_3 und dewiki-20140911.3_of_3. Die Datenfiles hatte ich im Hauptverzeichnis der internen SD-Karte gespeichert. Diese Konfiguration funktionierte bestens wie auch schon auf meinem vorherigen Galaxy Note 1 (16GB, Android 4.1.2), wobei sich die Datenfiles dort im Hauptverzeichnis der externen Speicherkarte befanden.

Vor einigen Tagen habe ich mir Aard2, v10 heruntergeladen und installiert. Das Datenfile dewiki-20141110.slob habe ich im Hauptverzeichnis der internen Speicherkarte gespeichert. Nach dem starten von Aard2 poppte das Programm auf mit der Tastatur und einem leeren Textbildschirm. Nach Eingabe des ersten Buchstabens im Suchfeld erschien im Textbildschirm das Lupensymbol und dahinter "Nichts gefunden". Ich konnte Wörter eingeben soviel ich wollte, an der Anzeige im Textbildschirm änderte sich nichts.

Ich habe in der Anwendung auch keine Möglichkeit gefunden, dass diese das Gerät nach dem Datenfile durchsucht. Gestern habe ich die Anwendung auf Aard2, v11 upgedated, aber es hat sich nichts verändert.

Ich bin für jeden Hinweis dankbar, der mir hilft, die Anwendung richtig zum laufen zu bringen.

Eine schöne Adventszeit und ein frohes Fest für alle wünscht

Wolf Haberbosch

[Markus Braun]

Aard2 has 5 very dark grey icons in the second row from the top. Use the second from the right.  The icon on top right will change. Push these two circle arrows. Aard2 will search for slob in your device and will find it.

--
You received this message because you are subscribed to the Google Groups "aarddict" group.
To unsubscribe from this group and stop receiving emails from it, send an email to aarddict+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Frank Röhm]

Am 21. Dezember 2014 01:36:14 MEZ, schrieb Markus Braun <markus...@googlemail.com>:

Aard2 has 5 very dark grey icons in the second row from the top. Use
the
second from the right.  The icon on top right will change. Push these
two

circle arrows. Aard2 will search for slob in your device and will find..

Like in the attachment.

[itkach]

Sounds like the app should automatically go to dictionaries tab and offer to scan device if started with no dictionaries.

[Markus Braun]

Nice idea.

A manual would could be helpful as well

Am 21.12.2014 03:04 schrieb "itkach" <itk...@gmail.com>:

Sounds like the app should automatically go to dictionaries tab and offer to scan device if started with no dictionaries.

--

[Frank Röhm]

Am 21. Dezember 2014 09:26:20 MEZ, schrieb Markus Braun <markus...@googlemail.com>:
>Nice idea.
>
>A manual would could be helpful as well

This is a very good idea!
I could write one in German and broken English.
What does Igor think about?

[Markus Braun]

Make it in German, I will translate it into English. A native speaker could optimise it then from UK english to US english :-)

[Frank Röhm]

OK, so best to do in github?
First I clone Aard 2 and then
I would make a open office document with done screenshots and explanations and then do a pull request?
Igor say something how this is done most professional or best.
I did not that many documentations in my career.

[Wolf Haberbosch]

@ MHBraun:  Thank you very much, this has made my day!
BTW, I too would welcome an instruction manual.
One more suggestion: A little more advertising would not hurt the app. To my knowledge there are currently only three usable offline reader for Wikipedia. These are:

- AardDictionary from aarddict.org
    Downloads: 10.000 - 50.000, PlayStore rating: 4.5
- Kiwix from kiwix.org
    Downloads: 50.000 -100.000, PlayStore rating: 4.4
- Wikipedia Encyclopedia from apps-unlimited.co.uk
    Downloads: 500.000 -1.000.000, Playstore rating: 4.2

Apparently, not only in my opinion, AardDiktionary is currently the best offline reader for Wikipedia. And the new app aard2 is, though in beta stage, yet much better.

Although I have no idea how to raise the awareness of the app - she deserves it anyway. Maybe it would go with lobbying etc. in popular journals such as android news & TV, androidnext, android user, Androidwelt, Softonic, GIGA, pocketpc.ch or similar ..

Anyway, thanks again for the help and happy holidays.

Wolf Haberbosch

[itkach]

Github - yes, OpenOffice - absolutely, categorically no.

But let's not get ahead of ourselves:

I am not sure "manual" is necessary, at least not yet.

First of all, this particular issue indicates that setting up dictionaries on first launch is not discoverable enough - it's better to fix it in code rather than documentation.

Second, I plan to expand README at https://github.com/itkach/aard2-android to include an overview of features and behaviors - some things are not obvious and will remain so, like "tapping on logo opens random article" or "bookmarks and history are limited to 100 records".

This is not going to be a detailed "manual", so if you still feel like authoring a document to fill in the gaps (or to translate information)  - of course, please do.

Github offers several tools for writing docs (that can be automatically rendered as nice-looking, mobile-friendly html), of which wiki is probably the easiest to get started with (others being Gists and GitHub Pages). Any Github user can edit wiki pages, so https://github.com/itkach/aard2-android/wiki would be the place to start. Use one of text markup languages supported at Github - markdown is probably the easiest, reStructured text and Org-mode are also fine choices. Keep it simple and straight to the point.

Github wikis are also git repos, so users can clone and edit in their favorite text editor and merge and so on. Or you can just edit in the browsers. Text written in a markup language like markdown or restructured text is still just text - easy to read without special tools like office suite, diff and merge, unlike binary formats such as openoffice. 

 

On Sunday, December 21, 2014 9:50:25 AM UTC-5, franc wrote:

OK, so best to do in github?
First I clone Aard 2 and then
I would make a open office document with done screenshots and explanations and then do a pull request?
Igor say something how this is done most professional or best.
I did not that many documentations in my career.

Am 21. Dezember 2014 10:10:02 MEZ, schrieb Markus Braun

Make it in German, I will translate it into English. A native speaker could optimise it then from UK english to US english :-)

Am 21.12.2014 09:59 schrieb "Frank Röhm"

Am 21. Dezember 2014 09:26:20 MEZ, schrieb Markus Braun 

[mhbraun]

You are welcome.

For advertising the app, somebody needs to take care of it, who knows how to do it, I guess. probably it makes sense with the launch of Aard2.

[itkach]

Am Sonntag, 21. Dezember 2014 16:07:10 UTC+1 schrieb Wolf Haberbosch:

@ MHBraun:  Thank you very much, this has made my day!
BTW, I too would welcome an instruction manual.
One more suggestion: A little more advertising would not hurt the app.

I'm pretty sure it would, and if number of installs for the apps you mention is any indication financial outcome is not worth the potential alienation of users and increased project complexity.

My impression that in such programs content is the key, user interface and everything else is rather secondary. The biggest source of high quality freely distributeable content is Wikipedia and sister projects. Those are freely available in many different ways and monetizing it is difficult.

Although I have no idea how to raise the awareness of the app - she deserves it anyway. Maybe it would go with lobbying etc. in popular journals such as android news & TV, androidnext, android user, Androidwelt, Softonic, GIGA, pocketpc.ch or similar .

Me neither. I guess just tell people you know about it :)

[franc]

Am Sonntag, 21. Dezember 2014 16:20:40 UTC+1 schrieb itkach:

Github - yes, OpenOffice - absolutely, categorically no.

But let's not get ahead of ourselves:

I am not sure "manual" is necessary, at least not yet.

First of all, this particular issue indicates that setting up dictionaries on first launch is not discoverable enough - it's better to fix it in code rather than documentation.

Second, I plan to expand README at https://github.com/itkach/aard2-android to include an overview of features and behaviors - some things are not obvious and will remain so, like "tapping on logo opens random article" or "bookmarks and history are limited to 100 records".

This is not going to be a detailed "manual", so if you still feel like authoring a document to fill in the gaps (or to translate information)  - of course, please do.

Github offers several tools for writing docs (that can be automatically rendered as nice-looking, mobile-friendly html), of which wiki is probably the easiest to get started with (others being Gists and GitHub Pages). Any Github user can edit wiki pages, so https://github.com/itkach/aard2-android/wiki would be the place to start. Use one of text markup languages supported at Github - markdown is probably the easiest, reStructured text and Org-mode are also fine choices. Keep it simple and straight to the point. ...

So I made a little start, please look if this kind of style is ok.
 

I would like to add nice screenshots into the text, but I think this not the github-wiki style is it? So I added screenshots from abload.de an image uploader, not knowing if this is the right style as well. No way to upload img to github into the wiki, is it?

So should I continue like this? Or am I on the wrong steamer?

[itkach]

https://help.github.com/articles/adding-images-to-wikis/

http://stackoverflow.com/questions/10045517/embedding-images-inside-a-github-wiki-gollum-repository

Wikis on Github are themselves git repositories, so images can be added. 

So should I continue like this? Or am I on the wrong steamer?

 

I'm not sure I like this style. Many of the sentences are vague or cryptic or contain irrelevant references. 

"Mostly they are not neccessary" Don't write things that are not necessary. Don't undermine written things that actually are useful by prefacing them like this.

Who is the target audience of this document? Experienced users who want to try something that's not in the Play Store? They don't need instructions for sideloading. Newbies? There's not enough clearly presented information here.   

"After or even before the installation you need dictionaries of the newer type, slob-files. " Newer type? Was there an older type? Why do I (as a user) care? slob-files? You mean dictionaries are files with .slob extension? So before or after? Does it matter? I am confused now.

"Aard2 will find them." How? Do I need to do anything?

"To use any dictionary, you first need to let them search through Aard2 to activate them." This is utterly confusing. Is there some special "activation process"  without which dictionaries won't work, like I need to register them at a website or something? Now, steps that follow are not very well structured. Contrast this with the style of aforementioned Github help page: https://help.github.com/articles/adding-images-to-wikis/ with specific simple, ordered steps, most of which are illustrated.

"The history tab, the third one," it may be second or forth or one hundred seventeenth tomorrow, so with things like this you are setting this document up to be outdated very quickly unless you are prepared to be really on top of things.  Same goes for "Aard2 is not yet on Google Play".

"shows all opened entries of all dictionaries." No, it does not. Shows recently visited articles. None of these are "opened" if you are looking at history tab (but they were in the past). I'm not sure concept of history really needs an explanation.

"same as the Favorites." There are no favorites. There are bookmarks. 

This needs to be better to be useful, otherwise it does more harm than good.

   

 

[franc]

Am Freitag, 26. Dezember 2014 17:32:04 UTC+1 schrieb itkach:

https://help.github.com/articles/adding-images-to-wikis/

http://stackoverflow.com/questions/10045517/embedding-images-inside-a-github-wiki-gollum-repository

Wikis on Github are themselves git repositories, so images can be added. 

I have no write access to your  repo. But now clear how to add external pictures.

 

Who is the target audience of this document? Experienced users who want to try something that's not in the Play Store? They don't need instructions for sideloading. Newbies? There's not enough clearly presented information here.   

 
Its for Newbies! Who else? People like me, stumbling onto this great thing and there is no intro or any documentation for it. Only the googlegroups which could be a annoying thing to go through to understand it.
Very often I find Github repos and on the wiki page there is just nothing because the developer doesn't have the time to explain his great work.
Documentation is so often neglected by the developers, this is very wellknown. Here the same, by the way.
 

"The history tab, the third one," it may be second or forth or one hundred seventeenth tomorrow, so with things like this you are setting this document up to be outdated very quickly unless you are prepared to be really on top of things.  Same goes for "Aard2 is not yet on Google Play".

Yes, this true. If you make an accurate documentation or How-To, you have to be really on top of things, software can change fast, the documentation should change with it each time. Thats how it is. No way to get out, if you want it exact.
If Aard2 comes to GP this should be immediately changed etc.

 

This needs to be better to be useful, otherwise it does more harm than good.

So I already cleaned some of your other well right critics, and I repeat, this is only the beginning it is far away to be complete.
But the main question is still alive: do you want this or not?
I could spend more time on it, be more exact, make screenshots and pictures and complete all this, but I won't if you don't want it.
It is your child, so tell.
Normally a good way to make volunteers working it is not only to tell the negative things, but at least some positive, as you don't I assume a bit, you don't like this kind of contribution, something is principally wrong with it?

[itkach]

On Friday, December 26, 2014 5:31:46 PM UTC-5, franc wrote:

Am Freitag, 26. Dezember 2014 17:32:04 UTC+1 schrieb itkach:

https://help.github.com/articles/adding-images-to-wikis/

http://stackoverflow.com/questions/10045517/embedding-images-inside-a-github-wiki-gollum-repository

Wikis on Github are themselves git repositories, so images can be added. 

I have no write access to your  repo. But now clear how to add external pictures.

Wiki itself is a repo, you wrote in it, so you do have write access, so I'm not sure what you mean.

And if you really don't have write access to some repo you can fork it, modify as you see fit and then create pull request.

 

 

Who is the target audience of this document? Experienced users who want to try something that's not in the Play Store? They don't need instructions for sideloading. Newbies? There's not enough clearly presented information here.   

 
Its for Newbies! Who else?

Then the document must reflect this: assume no knowledge of anything at all, be clearly structured and be very detailed.  

 

People like me

You yourself appear to be rather confused about this, because people like you - wanting to create and use their own CSS, trying to compile dictionaries themselves and writing guides for others - can hardly be described as "newbies".  

 

, stumbling onto this great thing and there is no intro or any documentation for it. Only the googlegroups which could be a annoying thing to go through to understand it.
Very often I find Github repos and on the wiki page there is just nothing because the developer doesn't have the time to explain his great work.
Documentation is so often neglected by the developers, this is very wellknown. Here the same, by the way.
 

"The history tab, the third one," it may be second or forth or one hundred seventeenth tomorrow, so with things like this you are setting this document up to be outdated very quickly unless you are prepared to be really on top of things.  Same goes for "Aard2 is not yet on Google Play".

Yes, this true. If you make an accurate documentation or How-To, you have to be really on top of things, software can change fast, the documentation should change with it each time. Thats how it is. No way to get out, if you want it exact.
If Aard2 comes to GP this should be immediately changed etc.

 

This needs to be better to be useful, otherwise it does more harm than good.

So I already cleaned some of your other well right critics, and I repeat, this is only the beginning it is far away to be complete.
But the main question is still alive: do you want this or not?
I could spend more time on it, be more exact, make screenshots and pictures and complete all this, but I won't if you don't want it.
It is your child, so tell.

I'm pretty sure I said 

"""

But let's not get ahead of ourselves:

I am not sure "manual" is necessary, at least not yet.

"""

 

Normally a good way to make volunteers working it is not only to tell the negative things, but at least some positive, as you don't I assume a bit,

That's not how it works. Volunteers do work because they feel like it, without anyone "making" them, and the reason they "feel like it" is often because they have an itch to scratch.

I certainly don't want to "make" anyone work.   

you don't like this kind of contribution, something is principally wrong with it?

I like all _kinds_ of contributions, but I like (and expect) them to be quality work.