OP solved it, closing

Your current solution still fails for cases that contain numeric characters (0-9) because they are considered valid characters but your code discards them

can python translation be pushed / approved?

Random test:

"n6N" is not a palindrome: expected true to equal false

Sample test:

test("RotaTor", true);

and Kata text says results are case insensitive.

So exactly how is "n6N" not a palindrome?

Aporoprivilagized

Java Translation.
Ready for review.

Or create a fork of your fork and I'll try with that.

The description was recently changed by Hobovsky and I changed my fork's description (created before the description change) to match that. The current description of the fork is the most up-to-date. The "older" was how the description was before the update.

Should I change it to how it was or keep the most up-to-date version?

It seems the problem is in the Notes part. At least when I fork your fork, I see this:

Notes:

<<<<<<< older

• reverse/reverse! have been disabled for String/Array and reverse() for JS.
• reverse cannot get used in Haskell either
• the empty string "" can be read forward or backward the same, it's a palindrome in our case.
  =======
  The empty string "" can be read forward or backward the same, it's a palindrome in our case.

yours

Can you try again? I think it's because I changed something in the code last minute. The description looks up to date (changed number of random tests to 50).

Description cannot be approved, recent changes from related record must be merged first.

Unless you've made some changes to the kata's description, click on translate like you were doing a new translation and copy/paste current description to your fork.

I guess it won't but, make sure solutions like this won't pass: https://www.codewars.com/kata/reviews/5304de75fe87e4905e000ccc/groups/63485a7f21228f0001f22c8b

I'm working in JavaScript fyi
thanks!

thank you for the resource page Chrono,

regarding reverse command, I didn't use that in my solution, but I will try to debug and get back to you. still throwing the same error.

thanks!