[All] New version of the orrery program available

[Ken Young]

A new version of the orrery program has been uploaded to the
GForge site, and to opkg.org.   There are not many new user
features - the Monthly Moon Calendar is prettier, and both
moon calendars now show Blue Moons (including the one on
New Years Eve, this year).   Finger friendliness has been
improved in a few areas.

Several worthless features (stylus mode, etc) have been
dropped.

One of the most commonly cited bugs, which caused the program
to fail if it was run on a phone whose locale had been set
to a language which uses commas, rather than periods, as
the decimal place separator, has been fixed.   Thanks a bunch
to Heiko Stubner, who submitted a patch that fixed this bug.

Joshua Rosen make new configuration files for the GNU automake
tools, and VERY PATIENTLY showed me how to make them work.
The source tarball is no longer a pathetic parody of a
source file distribution.

Please note - I mistakenly uploaded a version labelled 2.8
to the GForge site.   I can't get rid of it; please ignore it.
The 2008.x packages labelled 2.8 and 2.7 on the GForge site
are actually both 2.7.

Here's a list of the changes:

Version 2.7:
New user features:

   Monthly moon calendar now uses moon images.
   Also, both moon calendars now show "Blue
   Moons", using the common definition that
   a Blue Moon is the second full moon in a
   calendar month.

   Enlarged and re-arranged buttons on the
   "opts" page, for enhanced finger
   friendliness.

   Got rid of "stylus mode".   The program is
   always in finger mode now.   There was
   never a significant difference between the
   two modes anyway.

   The program now always saves configuration
   changes in nonvolatile memory.   This is
   the standard behavior for handheld
   applications.

Bug Fixes:

   Build-related files completely redone so
   as to use GNU autotools properly.

   Program no longer crashes if run on a
   phone who's locale is set to a language
   which uses a comma for the decimal point.

   Improved handling of zoom gestures which
   originate in the panning area.   Before
   this fix, it was difficult or impossible
   to zoom an area near the horizon, because
   such a gesture would be interpreted as a
   "press" in the panning area, which would
   call up the azimuth compass.

   Removed the call to the popt library that
   parsed the command line arguments.   This
   caused problems, because not all Freerunner
   software stacks shipped with the popt
   library.   The program now parses its
   command line arguments with no call to any
   library.

   Fixed a bug which made it difficult to
   use the arrows at the bottom of the monthly
   moon calendar to change months.



___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: [QtMoko] triangle icon on shelf (top bar)

[Ali]

On Mon, 2009-11-30 at 15:27 -0800, Brolin Empey wrote:
> Hello World,
> 
> I am using QtMoko v14 on a US FreeRunner (rev A6).  Ever since I
> switched from Speak Out Wireless to Fido, QtEI shows a triangle icon
> on the shelf (top bar).  This triangle icon did not appear when I used
> Speak Out Wireless.  I Googled for “qtopia phone triangle icon” and
> found an IRC log (search for “triangle”) claiming the triangle icon
> means roaming.  Is this true?  If yes, how can I be roaming when I am
> (AFAIK) in my home area?  I live and work in Delta, British Columbia,
> Canada.
> 
> Thanks,
> Brolin
> 
 Hey Brolin! I have the same issue, also with Fido. For reference, I am
located in Vancouver BC. It's been like this with even the earlier
versions of qtopia. My cell bill never shows roaming time, so it's not
as if i'm charged for it. I've wanted to get on the phone with Fido and
see if it's their end, but haven't made time (i hate talking to tech
support). I recall seeing this in *every* stack since I got the
freerunner launch week. Even on the current SHR, under modem info in
settings, it shows roaming. Seeing as how it only showed up after you
switched to Fido and seeing as how almost no one else complained it
leads me to believe it's a Fido problem. 


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

[QtMoko] triangle icon on shelf (top bar)

[Brolin Empey]

Hello World,

I am using QtMoko v14 on a US FreeRunner (rev A6).  Ever since I switched
from Speak Out Wireless to Fido, QtEI shows a triangle icon on the shelf
(top bar).  This triangle icon did not appear when I used Speak Out
Wireless.  I Googled for “qtopia phone triangle icon” and found an IRC
log(search
for “triangle”) claiming the triangle icon means roaming.  Is this
true?  If yes, how can I be roaming when I am (AFAIK) in my home area?  I
live and work in Delta, British Columbia, Canada.

Thanks,
Brolin


-- 
Sometimes I forget how to do small talk: 

“If you have to ask why, you’re not a member of the intended audience.” —
Bob Zimbinski, 
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: [WikiReader] French Image

[David Reyes Samblas Martinez]

Had you generated a hash file? using hash-gen utility?
, regards.


David Reyes Samblas Martinez
http://www.tuxbrain.com
Open ultraportable & embedded solutions
Openmoko, Openpandora,  Arduino
Hey, watch out!!! There's a linux in your pocket!!!




2009/12/1 Thomas Hocedez :
> Hi people.
>
> I manage to generate a French image for the wikireader .. but it is not
> usable. A sad "Failed to load article " is always displayed.
> My image strangely a single 1.4Go file ... any idea ?
>
> Second bad news for tonight : as I dismantle the WR to be more
> convenient to change SD card (by soldering batteries outside), I check
> for some room to add leds to backlight the screen. In one hand there is
> no way to backlight screen (with AAA batteries I mean), in the other
> hand, my touchscreen doesn't respond anymore ! I will only use the
> "random" button  'till I found some spare parts (I think the ribbon
> might be broken) and I don't want to let the project down right now !
>
> I'm regenerating an image. using lasts scripts. We'll see tomorrow.
>
> Tilmasn did you manage to generate something good ?
>
> Regards
>
>
> Thomas
>
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community
>

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

[WikiReader] French Image

[Thomas Hocedez]

Hi people.

I manage to generate a French image for the wikireader .. but it is not 
usable. A sad "Failed to load article " is always displayed.
My image strangely a single 1.4Go file ... any idea ?

Second bad news for tonight : as I dismantle the WR to be more 
convenient to change SD card (by soldering batteries outside), I check 
for some room to add leds to backlight the screen. In one hand there is 
no way to backlight screen (with AAA batteries I mean), in the other 
hand, my touchscreen doesn't respond anymore ! I will only use the 
"random" button  'till I found some spare parts (I think the ribbon 
might be broken) and I don't want to let the project down right now !

I'm regenerating an image. using lasts scripts. We'll see tomorrow.

Tilmasn did you manage to generate something good ?

Regards


Thomas

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: OT: Where can I meet a female companion with similar interests and personality /in person/?

[Brolin Empey]

2009/11/12 Brolin Empey 

> Hello list,
>
> I am writing a follow-up/update to my original post just over 2 months
> later.
>
> What has changed since my original post?
>

Another update.  What has changed since my last update?


   1. I stopped hiring Dave McCormick because I did not want to spend so
   much money when I did not even know what to have him help me with.
   2. I signed a tenancy agreement to rent a 1-bedroom apartment in Ladner
   Village:  my tenancy begins on 2010-01-01.  Of course, I am already having
   regrets because I am afraid the apartment is too small, it has electric
   heating, it is on the 3rd floor but there is no elevator, I do not know
   where I will store my bicycle even though I almost never use it any more,
   ... Oh well, at least I chose something.  It could be much worse.
   3. I finally upgraded my FreeRunner from QtMoko v11 to v14.  That was a
   huge hassle (because I had to manually back up my QtMoko v11 installation,
   reflash QtMoko v14, then restore everything I needed from my backup) and
   took at least 8 hours over 1 weekend, but it was worth it because the video
   is much more responsive with QtMoko v14 than v11.  QX still does not seem to
   work, though:  I still always end up having to remove my FreeRunner’s
   battery after trying to use QX because my FreeRunner becomes unusable.
   (fail)  Debian needs to update the version of mc in lenny/stable because
   their current version has a regression which prevents mc from listing the
   contents of some tar archives, including the one I made to back up my QtMoko
   v11 installation. (fail)
   4. I still have not bought a MicroSDHC card so I still cannot install
   plain Debian so I still do not have a working X server so I still cannot run
   Navit, but my parents gave me a Garmin nuvi 755T road navigiation system
   (commonly and very imprecisely called “a GPS”), so I at least have a working
   road navigation system for now.  I used the nuvi 755T to drive to work
   today:  it seems to work OK, but the text-to-speech (TTS) engine is poor:
   it sounds very mechanical and would probably never be mistaken for a real
   human voice.  I have heard much better TTS voices, but I cannot remember
   their names so I cannot cite any examples.
   5. I have actually used Xubuntu 9.10 at work (it is *so* stable:  it has
   unexpectedly locked up only once so far! :P), but still not Ubuntu 9.10 nor
   Kubuntu 9.10.  Of course, making Xorg use 16-bit colour depth instead of the
   default 24-bit so the 4 MiB video card can drive a 17" LCD monitor at its
   native 1280x1024 mode was a huge hassle involving hours of playing
   (experimenting) with *xorg.conf*, checking *Xorg.0.log*, comparing and
   copying from *xorg.conf*s on other PCs with the same model of LCD
   monitor, ...
   6. I actually messaged one of the people (Janet) from the Ubuntu
   Vancouver LoCo, but she still has not replied and I have not met her since I
   messaged her.
   7. I bought a used Canon PowerShot G6 for about 275 CAD including
   shipping via an eBay auction because I did not want to spend >550 CAD on a
   new PowerShot G11 (the current model), which will be worth less than half
   that in 5 years or less.  Of course, I am already having regrets, but I
   probably would have regretted buying a G11 too because the G6 is sufficient.

I am still constantly overthinking, obsessing, overwhelmed with ambivalence,
indecision, and too much information.  I still have no female companion.  I
have no close friends in Ladner other than maybe Miles Husoy, but I have not
even seen him for months.  I am not surprised, though, because I continue to
isolate myself.  I always feel like I have too much crap to do but I still
lay in my bed at home and inevitably fall alseep because I am tired of
overthinking and obsessing and am too ambivalent to do some of the endless
things I should be doing.  Now I have to prepare for my Class 5 passenger
vehicle road test on 2010-01-22 because there is a new and incredibly
illogical law in British Columbia starting on 2010-01-01 that drivers with a
Class 7 passenger vehicle driver’s licence, such as me, cannot use
electronic devices, including road navigation systems, while driving because
they are “too distracting”.  Reality check:  which is more distracting:
looking away from driving to read a paper map or driving directions, or not
looking away from driving because the road navigation system speaks to me so
I do not need to look at its display?  I do not use cell phones while
driving because I know I cannot focus sufficiently on driving if I am trying
to have a conversation with someone else in my car, so how could I have a
conversation with someone via a cell phone while driving?  I always pull
over and stop before using a cell phone.

Brolin

-- 
Sometimes I forget how to do small talk: 

“If you have to ask why, you’re not a member of the intended audience.” —
Bob Zimbinski, 

[All] A Chance for some exposure

[Nick]

I subscribe to a very popular YouTube channel
(http://www.youtube.com/user/phonedog) that does reviews for mobile phones
and other tech gadgets. They have recently posted a video asking for people
to submit their own video about their favourite gadget, with the best
reviewer having a chance of the getting on their home page.

I thought this would be a perfect opportunity for some exposure of the Neo
FreeRunner (or even WikiReader) device.

Does anyone with a YouTube account and who is motivated enough to produce a
review want to submit a video?

Have a look at: http://www.youtube.com/watch?v=MyCyVU4n6sY

Nick 


 


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: [WikiReader] Sharing compiling sources.

[David Reyes Samblas Martinez]

Nice redo of my ugly hack , thanks a lot Tilman :)
David Reyes Samblas Martinez
http://www.tuxbrain.com
Open ultraportable & embedded solutions
Openmoko, Openpandora,  Arduino
Hey, watch out!!! There's a linux in your pocket!!!




2009/11/30 Thomas HOCEDEZ :
> Tilman Baumann a écrit :
>> I think I cracked the nut, but have a look if you would be so kind.
>> I'm not sure I completely got it.
>>
>> (Please ignore the first commit. I did not test correctly before checking
>> in. :-/ )
>>
>> Regards
>>  Tilman Baumann
>>
>
> I just had an eye on it, it looks nice. I'll try it tonight for french
> version.
>
> Cheers
> Thomas
>
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community
>

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: [WikiReader] Sharing compiling sources.

[Thomas HOCEDEZ]

Tilman Baumann a écrit :
> I think I cracked the nut, but have a look if you would be so kind.
> I'm not sure I completely got it.
>
> (Please ignore the first commit. I did not test correctly before checking
> in. :-/ )
>
> Regards
>  Tilman Baumann
>   

I just had an eye on it, it looks nice. I'll try it tonight for french 
version.

Cheers
Thomas

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: [WikiReader] Sharing compiling sources.

[Tilman Baumann]

I realized that it does not apply to the latest version.
So I took the liberty of making a fork on github and merged it.
http://github.com/tbaumann/wikireader

I think I cracked the nut, but have a look if you would be so kind.
I'm not sure I completely got it.

(Please ignore the first commit. I did not test correctly before checking
in. :-/ )

Regards
 Tilman Baumann


David Reyes Samblas Martinez wrote:
> Here you have :)
>
> David Reyes Samblas Martinez
> http://www.tuxbrain.com
> Open ultraportable & embedded solutions
> Openmoko, Openpandora,  Arduino
> Hey, watch out!!! There's a linux in your pocket!!!
>
>
>
>
> 2009/11/30 Tilman Baumann :
>> Hi,
>>
>> can you maybe release this as a patch?
>> I like to inegrate this in github. But I fear I might miss something if
>> I
>> try to fiddle out the changes by hand.
>>
>> Thanks
>>
>> David Reyes Samblas Martinez wrote:
>>> Sorry for the wait Thomas,
>>> I was working to solve the broken pipe issue that stops the parser
>>> when it finds an error. I have applied a quick and dirty workaround
>>> using try-catch technique and now the process will not stop  and just
>>> skip the faulty article and keeps going :) it logs the faulty ones in
>>> a text file (title and position) for posterior forensics, but my first
>>> guesses in that is not a codification issue with utf8 is more an
>>> unexpected formating tag the php parser don't know how to deal with
>>> Actually parsing the german wikipedia with more than 1.3 million
>>> articles
>>>
>>> Count: 1043000
>>> Failing count: 2
>>>
>>> and keeps going I supose we can sacrificate two articles for having
>>> one milion available now :)
>>>
>>> as you requested I uploaded my working compiled tools[1]  but without
>>> any xml sources it's about 113Mb, but if you have a working tools on
>>> your system you just have to change
>>> host-tools/offline-renderer/ArticleParser.py by the attached on this
>>> mail and you can forget to cry like a child that his ice cream has
>>> fall to the floor when after more than 24h parsing hundred of thousand
>>> articles pased the process you see this ugly python error backtrace
>>> blablabla and not your desired file :)
>>>
>>> by the way the faultyarticles.txt is saved at same
>>> host-tools/offline-renderer directory, (i'm too lazy to put a
>>> parameter for change that and I hardcoded the name of the file ,
>>> yes... don't waste typing on correct that bad habit, I know)
>>>
>>> If you have curiosity of what articles on the german wiki are causing
>>> troubles
>>> on dewiki-latest-pages-articles.xml (date 2009-11-20)
>>>
>>> ~Storck Bicycle
>>> 832673
>>> ~Musculus serratus posterior inferior
>>> 857334
>>>
>>> Regards I hope I will upload the German wikipedia on Sunday... and
>>> will be available on Monday, sorry for the wait but my Asymmetric DSL
>>> is very asymmetric and upload 1.5-2 Gb (expected file size) will take
>>> a bunch of hours.
>>>
>>> For those than wants to compile his own , go for it :) the
>>> Quickreference in the doc directory on the souce is all you need to
>>> start working,  just remember than if you have a 64 bit system you
>>> will have to follow the 64 bits method to compile the tools,
>>>
>>> Regards
>>> [1]http://tuxbrain.org/downloads/wikireader/wikireaderbinaries20091127_dsamblas_modified_trycatch.tar.bz2
>>> David Reyes Samblas Martinez
>>> http://www.tuxbrain.com
>>> Open ultraportable & embedded solutions
>>> Openmoko, Openpandora,  Arduino
>>> Hey, watch out!!! There's a linux in your pocket!!!
>>>
>>>
>>>
>>>
>>> 2009/11/27 Thomas HOCEDEZ :
 Thomas HOCEDEZ a écrit :
>
> Hi DAvid,
>
> Can you share your scripts & configs to do the same in French (and
> other
> languages) ?
> Thanks
>
> Thomas
>
>

 As the Mailing list seems to be broken (or users started hibernating
 for
 winter...) I find by myself the way to compile things step by step.
 I'm for now rendering the French Wikipedia. As it started a few
 minutes
 ago,
 the result will be availabel during the weekend (I hope).

 I'll also post the way I managed to do so ! (I'm at the office for
 now,
 and
 I'm leaving...)

 Regards to you all !

 Thomas

>>> ___
>>> Openmoko community mailing list
>>> community@lists.openmoko.org
>>> http://lists.openmoko.org/mailman/listinfo/community
>>>
>>
>>
>> --
>>
>>
>>
>> ___
>> Openmoko community mailing list
>> community@lists.openmoko.org
>> http://lists.openmoko.org/mailman/listinfo/community
>>
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community
>


-- 



___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: [WikiReader] Sharing compiling sources.

[Thomas HOCEDEZ]

Tim Besard a écrit :
> Hi,
>
> It seems that the Dutch wikipedia contains some UTF-8 only characters,
> which crashes the parser after all due to the "system echo" in the
> exception handler. Changing the offending line to
> os.system('echo \"%s\" >> fault_articles.txt' %
> title.encode("utf8"))
> fixes the issue.
>
> Tim
>   
Well, thanks a lot Tim, the error occured also on the french parsing. 
And as I told before, I'm a Pythonbeginner, so the only way I found to 
avoid this was to ... remove the line, and keep the counter alive.

For information I finished rendering wfrench Wikipedia dump :
1 140 000 articles
61 false articles
parsing took 12 hours
rendering 18  hours

The image weights 1,6 Gigs, but only in one file (don't sure it is normal ?)
All this was done on a QuadCore 2.2Ghz, 2Go Ram.
I have to notice that the disk is NTFS, perhaps a ext4 would be better 
(my mount process dramatically worked during those processes).

The image is readable by the emulator, but as it was finish while I'm at 
the office, I could only try with a deported X display  (through SSH)
I Will post later (at home) when the file will be in the reader. Some 
friends will host the file, and I'm working on a automated script 
(weekly french image ?)

See you tonight

Thomas from "Wikilecteur" Team


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: SHR buildhost: unstable gta01 images gone?

[Marc Bantle]

Hi Sebastian,

Sebastian Krzyszkowiak schrieb:
> On 11/26/09, Andy Poling  wrote:
>   
>> The http://build.shr-project.org/shr-unstable/images/om-gta01 directory has
>>  seemingly vanished.  The om-gta02 directory is still there.
>>
>>  Is this permanent?  That was my favorite place to get kernels.  :(
>>
>>  -Andy
>>
>>  It ain't what you don't know that gets you into trouble.
>>  It's what you know for sure that just ain't so. - Mark Twain
>> 
>
> Don't worry, we'll try to build om-gta01 kernel and image soon :)
>   
Great news! Thanks for not letting the GTA01 down.

Cheers,
Marc




signature.asc
Description: OpenPGP digital signature
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: [WikiReader] Sharing compiling sources.

[David Reyes Samblas Martinez]

I have modified the python config to work with utf8 by default, that's
why I have no notice any conversion error, thanks for the tip Tim.
David Reyes Samblas Martinez
http://www.tuxbrain.com
Open ultraportable & embedded solutions
Openmoko, Openpandora,  Arduino
Hey, watch out!!! There's a linux in your pocket!!!




2009/11/30 Tim Besard :
> Hi,
>
> It seems that the Dutch wikipedia contains some UTF-8 only characters,
> which crashes the parser after all due to the "system echo" in the
> exception handler. Changing the offending line to
>    os.system('echo \"%s\" >> fault_articles.txt' %
> title.encode("utf8"))
> fixes the issue.
>
> Tim
>
> Op maandag 30-11-2009 om 14:49 uur [tijdzone +0100], schreef David Reyes
> Samblas Martinez:
>> Here you have :)
>>
>> David Reyes Samblas Martinez
>> http://www.tuxbrain.com
>> Open ultraportable & embedded solutions
>> Openmoko, Openpandora,  Arduino
>> Hey, watch out!!! There's a linux in your pocket!!!
>>
>>
>>
>>
>> 2009/11/30 Tilman Baumann :
>> > Hi,
>> >
>> > can you maybe release this as a patch?
>> > I like to inegrate this in github. But I fear I might miss something if I
>> > try to fiddle out the changes by hand.
>> >
>> > Thanks
>> >
>> > David Reyes Samblas Martinez wrote:
>> >> Sorry for the wait Thomas,
>> >> I was working to solve the broken pipe issue that stops the parser
>> >> when it finds an error. I have applied a quick and dirty workaround
>> >> using try-catch technique and now the process will not stop  and just
>> >> skip the faulty article and keeps going :) it logs the faulty ones in
>> >> a text file (title and position) for posterior forensics, but my first
>> >> guesses in that is not a codification issue with utf8 is more an
>> >> unexpected formating tag the php parser don't know how to deal with
>> >> Actually parsing the german wikipedia with more than 1.3 million articles
>> >>
>> >> Count: 1043000
>> >> Failing count: 2
>> >>
>> >> and keeps going I supose we can sacrificate two articles for having
>> >> one milion available now :)
>> >>
>> >> as you requested I uploaded my working compiled tools[1]  but without
>> >> any xml sources it's about 113Mb, but if you have a working tools on
>> >> your system you just have to change
>> >> host-tools/offline-renderer/ArticleParser.py by the attached on this
>> >> mail and you can forget to cry like a child that his ice cream has
>> >> fall to the floor when after more than 24h parsing hundred of thousand
>> >> articles pased the process you see this ugly python error backtrace
>> >> blablabla and not your desired file :)
>> >>
>> >> by the way the faultyarticles.txt is saved at same
>> >> host-tools/offline-renderer directory, (i'm too lazy to put a
>> >> parameter for change that and I hardcoded the name of the file ,
>> >> yes... don't waste typing on correct that bad habit, I know)
>> >>
>> >> If you have curiosity of what articles on the german wiki are causing
>> >> troubles
>> >> on dewiki-latest-pages-articles.xml (date 2009-11-20)
>> >>
>> >> ~Storck Bicycle
>> >> 832673
>> >> ~Musculus serratus posterior inferior
>> >> 857334
>> >>
>> >> Regards I hope I will upload the German wikipedia on Sunday... and
>> >> will be available on Monday, sorry for the wait but my Asymmetric DSL
>> >> is very asymmetric and upload 1.5-2 Gb (expected file size) will take
>> >> a bunch of hours.
>> >>
>> >> For those than wants to compile his own , go for it :) the
>> >> Quickreference in the doc directory on the souce is all you need to
>> >> start working,  just remember than if you have a 64 bit system you
>> >> will have to follow the 64 bits method to compile the tools,
>> >>
>> >> Regards
>> >> [1]http://tuxbrain.org/downloads/wikireader/wikireaderbinaries20091127_dsamblas_modified_trycatch.tar.bz2
>> >> David Reyes Samblas Martinez
>> >> http://www.tuxbrain.com
>> >> Open ultraportable & embedded solutions
>> >> Openmoko, Openpandora,  Arduino
>> >> Hey, watch out!!! There's a linux in your pocket!!!
>> >>
>> >>
>> >>
>> >>
>> >> 2009/11/27 Thomas HOCEDEZ :
>> >>> Thomas HOCEDEZ a écrit :
>> 
>>  Hi DAvid,
>> 
>>  Can you share your scripts & configs to do the same in French (and
>>  other
>>  languages) ?
>>  Thanks
>> 
>>  Thomas
>> 
>> 
>> >>>
>> >>> As the Mailing list seems to be broken (or users started hibernating for
>> >>> winter...) I find by myself the way to compile things step by step.
>> >>> I'm for now rendering the French Wikipedia. As it started a few minutes
>> >>> ago,
>> >>> the result will be availabel during the weekend (I hope).
>> >>>
>> >>> I'll also post the way I managed to do so ! (I'm at the office for now,
>> >>> and
>> >>> I'm leaving...)
>> >>>
>> >>> Regards to you all !
>> >>>
>> >>> Thomas
>> >>>
>> >> ___
>> >> Openmoko community mailing list
>> >> community@lists.openmoko.org
>> >> http://lists.openmoko.org/mailman/listinfo/community
>> >>
>> >
>> >
>> > --
>> >
>> 

Re: [WikiReader] Sharing compiling sources.

[Tim Besard]

Hi,

It seems that the Dutch wikipedia contains some UTF-8 only characters,
which crashes the parser after all due to the "system echo" in the
exception handler. Changing the offending line to
os.system('echo \"%s\" >> fault_articles.txt' %
title.encode("utf8"))
fixes the issue.

Tim

Op maandag 30-11-2009 om 14:49 uur [tijdzone +0100], schreef David Reyes
Samblas Martinez:
> Here you have :)
> 
> David Reyes Samblas Martinez
> http://www.tuxbrain.com
> Open ultraportable & embedded solutions
> Openmoko, Openpandora,  Arduino
> Hey, watch out!!! There's a linux in your pocket!!!
> 
> 
> 
> 
> 2009/11/30 Tilman Baumann :
> > Hi,
> >
> > can you maybe release this as a patch?
> > I like to inegrate this in github. But I fear I might miss something if I
> > try to fiddle out the changes by hand.
> >
> > Thanks
> >
> > David Reyes Samblas Martinez wrote:
> >> Sorry for the wait Thomas,
> >> I was working to solve the broken pipe issue that stops the parser
> >> when it finds an error. I have applied a quick and dirty workaround
> >> using try-catch technique and now the process will not stop  and just
> >> skip the faulty article and keeps going :) it logs the faulty ones in
> >> a text file (title and position) for posterior forensics, but my first
> >> guesses in that is not a codification issue with utf8 is more an
> >> unexpected formating tag the php parser don't know how to deal with
> >> Actually parsing the german wikipedia with more than 1.3 million articles
> >>
> >> Count: 1043000
> >> Failing count: 2
> >>
> >> and keeps going I supose we can sacrificate two articles for having
> >> one milion available now :)
> >>
> >> as you requested I uploaded my working compiled tools[1]  but without
> >> any xml sources it's about 113Mb, but if you have a working tools on
> >> your system you just have to change
> >> host-tools/offline-renderer/ArticleParser.py by the attached on this
> >> mail and you can forget to cry like a child that his ice cream has
> >> fall to the floor when after more than 24h parsing hundred of thousand
> >> articles pased the process you see this ugly python error backtrace
> >> blablabla and not your desired file :)
> >>
> >> by the way the faultyarticles.txt is saved at same
> >> host-tools/offline-renderer directory, (i'm too lazy to put a
> >> parameter for change that and I hardcoded the name of the file ,
> >> yes... don't waste typing on correct that bad habit, I know)
> >>
> >> If you have curiosity of what articles on the german wiki are causing
> >> troubles
> >> on dewiki-latest-pages-articles.xml (date 2009-11-20)
> >>
> >> ~Storck Bicycle
> >> 832673
> >> ~Musculus serratus posterior inferior
> >> 857334
> >>
> >> Regards I hope I will upload the German wikipedia on Sunday... and
> >> will be available on Monday, sorry for the wait but my Asymmetric DSL
> >> is very asymmetric and upload 1.5-2 Gb (expected file size) will take
> >> a bunch of hours.
> >>
> >> For those than wants to compile his own , go for it :) the
> >> Quickreference in the doc directory on the souce is all you need to
> >> start working,  just remember than if you have a 64 bit system you
> >> will have to follow the 64 bits method to compile the tools,
> >>
> >> Regards
> >> [1]http://tuxbrain.org/downloads/wikireader/wikireaderbinaries20091127_dsamblas_modified_trycatch.tar.bz2
> >> David Reyes Samblas Martinez
> >> http://www.tuxbrain.com
> >> Open ultraportable & embedded solutions
> >> Openmoko, Openpandora,  Arduino
> >> Hey, watch out!!! There's a linux in your pocket!!!
> >>
> >>
> >>
> >>
> >> 2009/11/27 Thomas HOCEDEZ :
> >>> Thomas HOCEDEZ a écrit :
> 
>  Hi DAvid,
> 
>  Can you share your scripts & configs to do the same in French (and
>  other
>  languages) ?
>  Thanks
> 
>  Thomas
> 
> 
> >>>
> >>> As the Mailing list seems to be broken (or users started hibernating for
> >>> winter...) I find by myself the way to compile things step by step.
> >>> I'm for now rendering the French Wikipedia. As it started a few minutes
> >>> ago,
> >>> the result will be availabel during the weekend (I hope).
> >>>
> >>> I'll also post the way I managed to do so ! (I'm at the office for now,
> >>> and
> >>> I'm leaving...)
> >>>
> >>> Regards to you all !
> >>>
> >>> Thomas
> >>>
> >> ___
> >> Openmoko community mailing list
> >> community@lists.openmoko.org
> >> http://lists.openmoko.org/mailman/listinfo/community
> >>
> >
> >
> > --
> >
> >
> >
> > ___
> > Openmoko community mailing list
> > community@lists.openmoko.org
> > http://lists.openmoko.org/mailman/listinfo/community
> >
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community



___
Openmoko community mailing list
community@lists.openmoko.org
http://li

Re: [WikiReader] Sharing compiling sources.

[David Reyes Samblas Martinez]

Here you have :)

David Reyes Samblas Martinez
http://www.tuxbrain.com
Open ultraportable & embedded solutions
Openmoko, Openpandora,  Arduino
Hey, watch out!!! There's a linux in your pocket!!!




2009/11/30 Tilman Baumann :
> Hi,
>
> can you maybe release this as a patch?
> I like to inegrate this in github. But I fear I might miss something if I
> try to fiddle out the changes by hand.
>
> Thanks
>
> David Reyes Samblas Martinez wrote:
>> Sorry for the wait Thomas,
>> I was working to solve the broken pipe issue that stops the parser
>> when it finds an error. I have applied a quick and dirty workaround
>> using try-catch technique and now the process will not stop  and just
>> skip the faulty article and keeps going :) it logs the faulty ones in
>> a text file (title and position) for posterior forensics, but my first
>> guesses in that is not a codification issue with utf8 is more an
>> unexpected formating tag the php parser don't know how to deal with
>> Actually parsing the german wikipedia with more than 1.3 million articles
>>
>> Count: 1043000
>> Failing count: 2
>>
>> and keeps going I supose we can sacrificate two articles for having
>> one milion available now :)
>>
>> as you requested I uploaded my working compiled tools[1]  but without
>> any xml sources it's about 113Mb, but if you have a working tools on
>> your system you just have to change
>> host-tools/offline-renderer/ArticleParser.py by the attached on this
>> mail and you can forget to cry like a child that his ice cream has
>> fall to the floor when after more than 24h parsing hundred of thousand
>> articles pased the process you see this ugly python error backtrace
>> blablabla and not your desired file :)
>>
>> by the way the faultyarticles.txt is saved at same
>> host-tools/offline-renderer directory, (i'm too lazy to put a
>> parameter for change that and I hardcoded the name of the file ,
>> yes... don't waste typing on correct that bad habit, I know)
>>
>> If you have curiosity of what articles on the german wiki are causing
>> troubles
>> on dewiki-latest-pages-articles.xml (date 2009-11-20)
>>
>> ~Storck Bicycle
>> 832673
>> ~Musculus serratus posterior inferior
>> 857334
>>
>> Regards I hope I will upload the German wikipedia on Sunday... and
>> will be available on Monday, sorry for the wait but my Asymmetric DSL
>> is very asymmetric and upload 1.5-2 Gb (expected file size) will take
>> a bunch of hours.
>>
>> For those than wants to compile his own , go for it :) the
>> Quickreference in the doc directory on the souce is all you need to
>> start working,  just remember than if you have a 64 bit system you
>> will have to follow the 64 bits method to compile the tools,
>>
>> Regards
>> [1]http://tuxbrain.org/downloads/wikireader/wikireaderbinaries20091127_dsamblas_modified_trycatch.tar.bz2
>> David Reyes Samblas Martinez
>> http://www.tuxbrain.com
>> Open ultraportable & embedded solutions
>> Openmoko, Openpandora,  Arduino
>> Hey, watch out!!! There's a linux in your pocket!!!
>>
>>
>>
>>
>> 2009/11/27 Thomas HOCEDEZ :
>>> Thomas HOCEDEZ a écrit :

 Hi DAvid,

 Can you share your scripts & configs to do the same in French (and
 other
 languages) ?
 Thanks

 Thomas


>>>
>>> As the Mailing list seems to be broken (or users started hibernating for
>>> winter...) I find by myself the way to compile things step by step.
>>> I'm for now rendering the French Wikipedia. As it started a few minutes
>>> ago,
>>> the result will be availabel during the weekend (I hope).
>>>
>>> I'll also post the way I managed to do so ! (I'm at the office for now,
>>> and
>>> I'm leaving...)
>>>
>>> Regards to you all !
>>>
>>> Thomas
>>>
>> ___
>> Openmoko community mailing list
>> community@lists.openmoko.org
>> http://lists.openmoko.org/mailman/listinfo/community
>>
>
>
> --
>
>
>
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community
>
From f1495f933a425e9c0f3fe23ac188662008be0654 Mon Sep 17 00:00:00 2001
From: David Samblas 
Date: Mon, 30 Nov 2009 13:54:27 +0100
Subject: [PATCH] Make the parser phase don't stop for one faulty page

---
 host-tools/offline-renderer/ArticleParser.py |   19 ---
 1 files changed, 16 insertions(+), 3 deletions(-)

diff --git a/host-tools/offline-renderer/ArticleParser.py b/host-tools/offline-renderer/ArticleParser.py
index 22baff2..1e250b2 100755
--- a/host-tools/offline-renderer/ArticleParser.py
+++ b/host-tools/offline-renderer/ArticleParser.py
@@ -69,6 +69,7 @@ def main():
 global verbose
 global PARSER_COMMAND
 global total_articles
+global fault_articles
 
 try:
 opts, args = getopt.getopt(sys.argv[1:], 'hvx:s:c:o:jn',
@@ -146,6 +147,8 @@ def main():
 current_file_id = None
 f = None
 total_articles = 0
+fault_articles = 0
+articles_length = 0

Re: [WikiReader] Sharing compiling sources.

[Tilman Baumann]

Actually the tar file seems to be broken. So much for potentially missing
stuff. ;)

Tilman Baumann wrote:
> Hi,
>
> can you maybe release this as a patch?
> I like to inegrate this in github. But I fear I might miss something if I
> try to fiddle out the changes by hand.
>
> Thanks
>
> David Reyes Samblas Martinez wrote:
>> Sorry for the wait Thomas,
>> I was working to solve the broken pipe issue that stops the parser
>> when it finds an error. I have applied a quick and dirty workaround
>> using try-catch technique and now the process will not stop  and just
>> skip the faulty article and keeps going :) it logs the faulty ones in
>> a text file (title and position) for posterior forensics, but my first
>> guesses in that is not a codification issue with utf8 is more an
>> unexpected formating tag the php parser don't know how to deal with
>> Actually parsing the german wikipedia with more than 1.3 million
>> articles
>>
>> Count: 1043000
>> Failing count: 2
>>
>> and keeps going I supose we can sacrificate two articles for having
>> one milion available now :)
>>
>> as you requested I uploaded my working compiled tools[1]  but without
>> any xml sources it's about 113Mb, but if you have a working tools on
>> your system you just have to change
>> host-tools/offline-renderer/ArticleParser.py by the attached on this
>> mail and you can forget to cry like a child that his ice cream has
>> fall to the floor when after more than 24h parsing hundred of thousand
>> articles pased the process you see this ugly python error backtrace
>> blablabla and not your desired file :)
>>
>> by the way the faultyarticles.txt is saved at same
>> host-tools/offline-renderer directory, (i'm too lazy to put a
>> parameter for change that and I hardcoded the name of the file ,
>> yes... don't waste typing on correct that bad habit, I know)
>>
>> If you have curiosity of what articles on the german wiki are causing
>> troubles
>> on dewiki-latest-pages-articles.xml (date 2009-11-20)
>>
>> ~Storck Bicycle
>> 832673
>> ~Musculus serratus posterior inferior
>> 857334
>>
>> Regards I hope I will upload the German wikipedia on Sunday... and
>> will be available on Monday, sorry for the wait but my Asymmetric DSL
>> is very asymmetric and upload 1.5-2 Gb (expected file size) will take
>> a bunch of hours.
>>
>> For those than wants to compile his own , go for it :) the
>> Quickreference in the doc directory on the souce is all you need to
>> start working,  just remember than if you have a 64 bit system you
>> will have to follow the 64 bits method to compile the tools,
>>
>> Regards
>> [1]http://tuxbrain.org/downloads/wikireader/wikireaderbinaries20091127_dsamblas_modified_trycatch.tar.bz2
>> David Reyes Samblas Martinez
>> http://www.tuxbrain.com
>> Open ultraportable & embedded solutions
>> Openmoko, Openpandora,  Arduino
>> Hey, watch out!!! There's a linux in your pocket!!!
>>
>>
>>
>>
>> 2009/11/27 Thomas HOCEDEZ :
>>> Thomas HOCEDEZ a écrit :

 Hi DAvid,

 Can you share your scripts & configs to do the same in French (and
 other
 languages) ?
 Thanks

 Thomas


>>>
>>> As the Mailing list seems to be broken (or users started hibernating
>>> for
>>> winter...) I find by myself the way to compile things step by step.
>>> I'm for now rendering the French Wikipedia. As it started a few minutes
>>> ago,
>>> the result will be availabel during the weekend (I hope).
>>>
>>> I'll also post the way I managed to do so ! (I'm at the office for now,
>>> and
>>> I'm leaving...)
>>>
>>> Regards to you all !
>>>
>>> Thomas
>>>
>> ___
>> Openmoko community mailing list
>> community@lists.openmoko.org
>> http://lists.openmoko.org/mailman/listinfo/community
>>
>
>
> --
>
>


-- 



___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: [WikiReader] Sharing compiling sources.

[Tilman Baumann]

Hi,

can you maybe release this as a patch?
I like to inegrate this in github. But I fear I might miss something if I
try to fiddle out the changes by hand.

Thanks

David Reyes Samblas Martinez wrote:
> Sorry for the wait Thomas,
> I was working to solve the broken pipe issue that stops the parser
> when it finds an error. I have applied a quick and dirty workaround
> using try-catch technique and now the process will not stop  and just
> skip the faulty article and keeps going :) it logs the faulty ones in
> a text file (title and position) for posterior forensics, but my first
> guesses in that is not a codification issue with utf8 is more an
> unexpected formating tag the php parser don't know how to deal with
> Actually parsing the german wikipedia with more than 1.3 million articles
>
> Count: 1043000
> Failing count: 2
>
> and keeps going I supose we can sacrificate two articles for having
> one milion available now :)
>
> as you requested I uploaded my working compiled tools[1]  but without
> any xml sources it's about 113Mb, but if you have a working tools on
> your system you just have to change
> host-tools/offline-renderer/ArticleParser.py by the attached on this
> mail and you can forget to cry like a child that his ice cream has
> fall to the floor when after more than 24h parsing hundred of thousand
> articles pased the process you see this ugly python error backtrace
> blablabla and not your desired file :)
>
> by the way the faultyarticles.txt is saved at same
> host-tools/offline-renderer directory, (i'm too lazy to put a
> parameter for change that and I hardcoded the name of the file ,
> yes... don't waste typing on correct that bad habit, I know)
>
> If you have curiosity of what articles on the german wiki are causing
> troubles
> on dewiki-latest-pages-articles.xml (date 2009-11-20)
>
> ~Storck Bicycle
> 832673
> ~Musculus serratus posterior inferior
> 857334
>
> Regards I hope I will upload the German wikipedia on Sunday... and
> will be available on Monday, sorry for the wait but my Asymmetric DSL
> is very asymmetric and upload 1.5-2 Gb (expected file size) will take
> a bunch of hours.
>
> For those than wants to compile his own , go for it :) the
> Quickreference in the doc directory on the souce is all you need to
> start working,  just remember than if you have a 64 bit system you
> will have to follow the 64 bits method to compile the tools,
>
> Regards
> [1]http://tuxbrain.org/downloads/wikireader/wikireaderbinaries20091127_dsamblas_modified_trycatch.tar.bz2
> David Reyes Samblas Martinez
> http://www.tuxbrain.com
> Open ultraportable & embedded solutions
> Openmoko, Openpandora,  Arduino
> Hey, watch out!!! There's a linux in your pocket!!!
>
>
>
>
> 2009/11/27 Thomas HOCEDEZ :
>> Thomas HOCEDEZ a écrit :
>>>
>>> Hi DAvid,
>>>
>>> Can you share your scripts & configs to do the same in French (and
>>> other
>>> languages) ?
>>> Thanks
>>>
>>> Thomas
>>>
>>>
>>
>> As the Mailing list seems to be broken (or users started hibernating for
>> winter...) I find by myself the way to compile things step by step.
>> I'm for now rendering the French Wikipedia. As it started a few minutes
>> ago,
>> the result will be availabel during the weekend (I hope).
>>
>> I'll also post the way I managed to do so ! (I'm at the office for now,
>> and
>> I'm leaving...)
>>
>> Regards to you all !
>>
>> Thomas
>>
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community
>


-- 



___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Distributor list

[David Reyes Samblas Martinez]

Really disappointing for us to , that Sean has decided to not maintain
an "official" distributors list,
This drain a little the interest on making business and be so
participative on making the marketing stuff Openmoko Inc has decided
not to do.
I really believe in the project of a freephone, I really believe in of
open hardware but I'm starting to not believe in Openmoko Inc.
And Sean please not argue than FreeRunner responsibilities has been
transfered to community because hardware are still sold  by Openmoko
Inc.

Regards from a very sad distributor

David Reyes Samblas Martinez
http://www.tuxbrain.com
Open ultraportable & embedded solutions
Openmoko, Openpandora,  Arduino
Hey, watch out!!! There's a linux in your pocket!!!




2009/11/30 Dr. H. Nikolaus Schaller :
>
> Am 30.11.2009 um 08:14 schrieb Christoph Pulster:
>
>>> http://wiki.openmoko.org/wiki/Distributors
>>
>> Being one of your resellers, I appreciate your effords.
>
> Also being one of the resellers, I admit that I am not at all happy
> with how this list is treated. What I really expect is that the
> manufacturer who has a network of distributors takes care of listing
> them properly. And not through an anonymous community.
>
> Unfortunately Sean declined to continue responsibility. So they simply
> linked to the wiki page. And only after insisting to at least inform
> the community, he wrote this request to find a volunteer.
>
> Translated into bold words it means: "We, Openmoko, have no interest
> in organizing anything that helps that our products are being provided
> to interested parties. And the community will solve our problems."
>
>> The list of distributors badly needs an update. Not on the wiki, but
>> in
>> real life.
>>
>> I think it is confusing for the customer to see so many shops listed,
>> which are obviously not seem to be active anymore. English shop
>> Truebox
>> and German Trisoft to mention just two (both still have a christmas
>> 2008
>> offer online...).
>
> I think you just want less competition being visible - raising your
> own visibility :)
> We have an open market and everyone can display his own offer as good
> as he likes.
>
> And, (especially for the Freerunner) I believe in educated customers
> who can compare themselves what the best and most up-to-date offer is.
> And they can IMHO also convert and compare currencies.
>
>> Besides, a lot of resellers quit selling Openmoko products, because
>> they
>> are unhappy how it worked out in the past. Swedish Openmoko.se shop
>> and
>> Spanish Blitz shop to mention just two.
>
> It is the lack of sales organization of Openmoko which makes it
> difficult for distributors to continue to work with them.
>
>
> Nikolaus
> http://www.handheld-linux.com
>
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community
>

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Distributor list

[Dr. H. Nikolaus Schaller]

Am 30.11.2009 um 08:14 schrieb Christoph Pulster:

>> http://wiki.openmoko.org/wiki/Distributors
>
> Being one of your resellers, I appreciate your effords.

Also being one of the resellers, I admit that I am not at all happy  
with how this list is treated. What I really expect is that the  
manufacturer who has a network of distributors takes care of listing  
them properly. And not through an anonymous community.

Unfortunately Sean declined to continue responsibility. So they simply  
linked to the wiki page. And only after insisting to at least inform  
the community, he wrote this request to find a volunteer.

Translated into bold words it means: "We, Openmoko, have no interest  
in organizing anything that helps that our products are being provided  
to interested parties. And the community will solve our problems."

> The list of distributors badly needs an update. Not on the wiki, but  
> in
> real life.
>
> I think it is confusing for the customer to see so many shops listed,
> which are obviously not seem to be active anymore. English shop  
> Truebox
> and German Trisoft to mention just two (both still have a christmas  
> 2008
> offer online...).

I think you just want less competition being visible - raising your  
own visibility :)
We have an open market and everyone can display his own offer as good  
as he likes.

And, (especially for the Freerunner) I believe in educated customers  
who can compare themselves what the best and most up-to-date offer is.  
And they can IMHO also convert and compare currencies.

> Besides, a lot of resellers quit selling Openmoko products, because  
> they
> are unhappy how it worked out in the past. Swedish Openmoko.se shop  
> and
> Spanish Blitz shop to mention just two.

It is the lack of sales organization of Openmoko which makes it  
difficult for distributors to continue to work with them.


Nikolaus
http://www.handheld-linux.com

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community