Re: Nokia 8210
From Markus Gebhard <ukg...@rz.uni-karlsruhe.de>
· alt.ascii-art
· 2 Oct 2001 22:19 · View full thread
· report
Robert Bowmaker wrote: > > > A few days ago I have written a simple algorithm to correct documents > > with wrapped lines (this algorithm will be part of JavE 2.0). > > Unfortunately it only works when some assumptions are true for the > > wrapped image: > > - there is only one line break in each line > > That is kind of useless. How much bother could it be? I made a program that > does any given number. So you have to specify the number of pieces the lines are broken into? But how do you find out how many space characters you have to add between the pieces? What if some lines are broken once, others are broken twice? I do not see a way to solve this problems... Does your program work on the Nokia 8210 image? > > - each (correct) line has a character different from [space] at the > > first and last position > > ??? Why??? Sounds like a crappy algorithm. Consider a line "XXX___YYY__" (where '_' are spaces) broken into two pieces. As result you only get "XXX" and "YYY" - the space characters have been deleted by your mail client. Now I only can see two ways to find out the number of spaces the algorithm has to add between XXX and YYY: 1) You know the length of the line and there are no spaces after YYY. 2) You can try to find out the alignment of YYY by comparing the current line to the next and previous ones (context). 1) is how my new algorithm works... 2) Will not produce reliable results with iamge2ascii-images. However it does work quite well with line style ascii art, for there usually is enough context information. Using this I have already written another repair algorithm that was included in Jave 1.1 to repair "shaked lines": _________ _______ _______ _________ \__ __/( ____ \( ____ \\__ __/ ) ( | ( \/| ( \/ ) ( | | | (__ | (_____ | | | | | __) (_____ ) | | | | | ( ) | | | | | | (____/\/\____) | | | )_( (_______/\_______) )_( can be repaird to: _________ _______ _______ _________ \__ __/( ____ \( ____ \\__ __/ ) ( | ( \/| ( \/ ) ( | | | (__ | (_____ | | | | | __) (_____ ) | | | | | ( ) | | | | | | (____/\/\____) | | | )_( (_______/\_______) )_( I think combining both of my repair algorithms will not result in a good solution to the wrapping problem we discussed above. So how does your program do that? Can you explain it or may I have a look at it (binary or source)? > > - each line is wrapped > > We can assume that, unless all the lines are different lengths, which would > be bad ascii art. Ehm... Excuse me, but I do not consider this example here 'bad ascii art', although most of the lines are different in length: o .-""| |-""| | _,.-+. .|-"" '. '.' '. | '. _.-'| | + .-" J _.+ .....'.'| '.-" | _,.-" '. ..'88888888| | J''.. +:" '.'88888888888;-+. | _+.|8888: | \ _.-+88888888_." _.F F +:' '.8888'.... L \ _.-"" |8888_.-" _." J J J '. +88888888: | '+" |_.-" _.-" | | | + '.888888'._-'. .'8L L J _.-" | | | '. '.88_.-" '. :888| | J-" F F F '. _.-" '. :88888L L _, L J J J '|. '; :888888J | +-" \ L _.-+.|.+. F '. _.-"J :8888888| L L\ \| _.-" ' '. J '. .-" | :8888888.L | | \ ',_.-" '. | "..-" J'. :888888: | L L '. \ _,.-+. '. :+-. | F88'. :888888: L | | \ ;.-" '. :-" ":, J |88888: :888888: | L L +:"" '. _.-" .-" | | J:888888: :888888: L | | J \ '.-' _.-' J J F :888888: :88888: \ L L L \ _.-+ _.-' | | | :888888: :888888: \| | | '. _.-" |-" J J J :888888: :888888'. +'\ J \ _.-" F ,-T"\ | | .-' :888888: :888888 '. \ L +" J / | J J J .-' .'888888: :8888888 : \ | | | F '.|.-'+|-' .' 8888888: :8888888 : \ J | F J '... .' 888888888: :8888888 : \ L | J | \88'.''.''''.' 8888888888: :8888888 : \| | | .-'\ \8888888888888888888888: :8888888 '. J | F-' .'\ \8888888888888888888.' :88888888 : L | J : 8\ \8888888888888888.' :88888888 : | | .+ ...' 88\ \8888888888.''.' :88888888 : J | .-' .' 8888\ \'.'''.'.' :88888888 : \ | .-' .' 888888888.\ _-' :888888888 : \|-' .' 888888888.' \_-" '.88888888'.. : 8888888.' :88888888 ''''.''.' 88888888: hs :8888888888888888888888888888: :88888888888888888888888888: :888888888888888888888888: ''.8888888888888...'.''' '''''......'' Oops, it already wrapped... :-/ Markus
Original message headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f996b,b639181160774d8d X-Google-Attributes: gidf996b,public X-Google-ArrivalTime: 2001-10-02 15:19:46 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!newsfeeds.belnet.be!news.belnet.be!feed.news.nacamar.de!rz.uni-karlsruhe.de!news.rz.uni-karlsruhe.de!not-for-mail From: Markus Gebhard <ukg...@rz.uni-karlsruhe.de> Newsgroups: alt.ascii-art Subject: Re: Nokia 8210 Date: Wed, 03 Oct 2001 00:19:48 +0200 Organization: University of Karlsruhe, Germany Lines: 132 Message-ID: <3BB...@rz.uni-karlsruhe.de> References: <2GNs7.25353$Lc6...@news1.cableinet.net> <9pamf7$h3u3l$4...@ID-39741.news.dfncis.de> <3BB...@rz.uni-karlsruhe.de> <4pqu7.324$jc1...@news.xtra.co.nz> NNTP-Posting-Host: wn4-jarjar.wn4.uni-karlsruhe.de Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: news.rz.uni-karlsruhe.de 1002061184 29426 172.20.12.141 X-Complaints-To: use...@rz.uni-karlsruhe.de X-Mailer: Mozilla 4.78 [en] (Win98; U) X-Accept-Language: en Xref: archiver1.google.com alt.ascii-art:8281
Related ASCII art in the Gallery
Explore these categories from our collection of 11,000+ artworks:
//O\\
|\/\/\/| | | | | | (o)(o) C _) | ,___| | / /____\
|HHHHH/"\"\HHHHHHH| |HH`\|_.-)'|/'dP,H| |Hb.`\\_/_//'.oddH| |HHHb|`.\/\,'|HHHH| |HHHHHb/\/\/|HHHHH| |"""""""""""""""""| | |"" /\ \ / |"" | | |__/--\ \/ __| |
_________
/___ ___\
//@@@\ /@@@\\
\\@@@/ \@@@//
\___ " ___/
| - |
\_/ jrjc ______
/|_||_\`.__
( _ _ _\
=`-(_)--(_)-'
hjw .="=. _/.-.-.\_ ( ( o o ) ) |/ " \| \'---'/jgs /`"""`\\
Make your own ASCII art
Turn images, text or 3D into ASCII, or draw your own – right in your browser.
About this message.
This message was posted publicly to the newsgroup
alt.ascii-art
in 2001 and is mirrored here unchanged as part of the Historic Archives – only email addresses are masked.
The artwork and text belong to their original authors: if you copy a piece, keep the artist's initials or signature intact and credit them where you can.
Are you the author? Contact us to get your posts attributed, connected to your artist profile, or removed.
Report this message
Help us keep the archive clean and accurate. Reports are reviewed by a person – nothing is changed automatically.