Back to General discussions forum
"Thus the first sum-of-digits which is divisible by 10 is for number 19. The next is for number 27."
It is 28 actually, the example is correct tho
input data:
3
1
2
10
answer:
19 28 109
Good catch!
As a general question, is this where we would report minor typos with the text of problems, even if they don't interfere with the values or actual problem?
For example in the text for Problem 198 (Prn Hex Str) it is written "...a character whith higher nibble...". Just noticing a few very minor things like that. Not a big issue but if it's a simple matter of pointing out an unnoticed spelling/grammar error to get it fixed then just wondering if this should be the place to do that :)
Friends, Hi, and thanks for help!
Fixed 28
and with
.
is this where we would report minor typos
Good question. The matter is we don't have better way, so doing this in forum should be fine. Perhaps, let me modify the title of this specific thread and somehow link it to problem descriptions everywhere a bit later. Then any further suggested corrections could be added here.
(at the very beginning there was a feature like, you know, select the typo and press ctrl-enter, but it was surprisingly unhandy)
UPD: added small link report typos
on the right side, below the title etc (just below the title, when you read problem page).
Wow, I just noticed that "report typos" button and felt silly having missed it before... But I guess that was just a case of lightning-fast implementation!
I've also found 2 more small typos on Problem #284:
1) "...and feels it with further values..." should be "...and fills..."
2) "insde" should be "inside". Using ctrl+F might just be the easiest way to locate that one on that page.
Thanks!
A few more on https://www.codeabbey.com/index/wiki/basic-language-manual
Use ctrl+F for the following: 1) "identation" 2) "is is" 3) "loarithm"
Just some more typos, hope I'm not being annoying or anything with all the doubleposts...
This time on Problem #366 "Image Cutting".
"But you do not want to loose lose
too much of your image. What is the biggest are area
of the image you can cut..."
"Input data: First line will contain number of images to be cut. Other lines will contain width and height of the image WxH and the aspect ratio of the dsiplay display
W:H separated by space.
Thanks!
One more in #83 "Graph Generator". Do ctrl+F for abouve
.
Oh, so silly about this "feel/fill". I remember laughing at my boss who wrote "I don't fill well" and now, hooray, I made similar typo :)
About "identation" - I remember interesting story of similar mistake in documents of US (?) soldiers during WW2, which Germans corrected in the forged documents and thus their spies were uncovered by lacking typo Ctrl-F for "indentification" here.
Fixed these - and "lose", "area", "display" and "above" also. Thanks a lot!
hope I'm not being annoying
no, for sure :) it would be silly to add reporting link and then not to fix typos. on contrary, thanks a lot for your attentiveness! it is good to get rid of such silly mistakes, especially given that they may confuse people for whom English is not native language!
Don't feel bad! I'm not too familiar with Slavic languages or Cyrillic, but I know that English vowel sounds in particular are often hard to predict from their letter and vice versa, compared to many other languages having much more consistent mapping.
That is an amazing story from WW2!
I also found one more on #109 "Lucky Tickets" - concidered
.
And I'm glad to help! Especially when helping is just making a note when I notice something :)
Another small one on Problem #281 "Basic Tokenizer". Ctrl+F for parce
.
not a typo, but a math error, in #102 a convex polygon is wrongly defined as having all angles less than pi/2 while that should say less than pi.
sorry that ironically was a typo, i meant #105 in previous post and cannot edit it for some reason
Oh, thanks a lot! I wonder, how this problem was there for perhaps almost 10
years, solved by 900+
persons and only
now this silly mistake was noticed :) it is fixed now!
Editing of the post is limited probably to about 1 hour (for case that some significant information was shared which we don't want author to remove in future out of some fancy). No worry though, it was plain which problem is in question.
Also thanks for bringing attention here - obviously I missed couple of messages from Kevin aka moxieman
above. Fixed
these too!
Rodion, thanks for Your quick response. Concerning my unability to edit, nevermind, this was definitely not a problem of the page, I was on an android device, which was buggy with edit forms. Today I edit another post and it worked fine!
Not a typo exactly, but in the Connect Four problem, the visualization link from the line "You may watch this visualization kindly created for us by our colleague Bloggermark
to understand the game better.", is apparently broken.
Ultimately this doesn't impact the solvability of the problem, although now I'm curious as to what the visualization may have originally been!
On Problem 66, the link to openabbey.com redirects to ... something else.