You are not logged in.
Hello.
I'm experimenting with the program and have found a problem with the Spanish language.
The program does not recognize the character "ñ" as valid and do not rename the files that contain it.
There is solution for this problem?
Thank you!
Offline
I can't confirm that, I'm spanish but it doesn't give me any problems.
Which version are you using? And is it the english or the translated version?
I tried both but it went as expected.
Maybe it is one of these other reasons?:
http://www.den4b.com/wiki/ReNamer:Failed_renaming
Last edited by SafetyCar (2013-07-29 11:49)
If this software has helped you, consider getting your pro version. :)
Offline
I was using the English version.
I downloaded the version in Spanish and I have no longer the problem.
Thank you and Congratulations on the program.
It's great!
Offline
Just to know, have you tried if you keep having the same problem on the english version?
If this software has helped you, consider getting your pro version. :)
Offline
I have problem with that "ñ" character using Case rule. When use:
1) Case: Capitalize every word (skip extension)
Prince Royce - Las Cosas Pequeñas.mp3 ---> Prince Royce - Las Cosas PequeñAs.mp3
Same thing is in Spanish version. Didn't expect to be different.
I downloaded the version in Spanish and I have no longer the problem.
What you've done to have problem in English version, related to that character, really don't know.
P.S. See email, SafetyCar.
TRUTH, FREEDOM, JUSTICE and FATHERLAND are the highest morale values which human is born, lives and dies for!
Offline
Prince Royce - Las Cosas Pequeñas.mp3 ---> Prince Royce - Las Cosas PequeñAs.mp3
P.S. See email, SafetyCar.
I've seen the email. I added it into renamer and a strange thing happens. The ñ written on my system appear ok, but your file appears separated as "Prince Royce - Las Cosas Pequen~as.mp3". In that name I see the case rule problem but changing it to a normal "ñ" there is no problem.
Maybe Dennis has an idea of why that ñ appears in a different way?
If this software has helped you, consider getting your pro version. :)
Offline
You have just opened a can of worms!
After a bit of investigation I found out about Combining Characters - characters that are intended to modify other characters. These are special marks that are designed to be over-imposed over the preceding characters.
There are two ways to write characters with diacritical mark, such as ñ (n with a tilde):
Let's come back to the renaming issues now. In the example Pequeñas.mp3 we actually have Pequen~as.mp3 in binary (with a magic combining tilde which gets graphically imposed over preceding n but is actually a separate character). In code ReNamer sees the binary format not the graphical representation, so it detects "Pequen" and "as" as two separate words separated by the weird tilde, resulting in PequeñAs.mp3 capitalization.
It looks like the solution is for ReNamer to handle these special combining characters as part of words, not breaking the word boundaries. I will investigate this within Case rule, but are there any other places where these combining characters present a problem?
Offline
Another option is to perform Unicode Normalization possibly as an option of Cleanup rule, prior to using any other rule where those characters could cause issues. Also, worth mentioning is an interesting article describing how to Use Unicode Normalization to Represent Strings.
Offline
It looks like the solution is for ReNamer to handle these special combining characters as part of words, not breaking the word boundaries. I will investigate this within Case rule, but are there any other places where these combining characters present a problem?
I think that probably the most difficulties come from people that has not access to the "ñ" in their keyboards, I had never found this problems before, so I'm not aware of any other.
Another option is to perform Unicode Normalization possibly as an option of Cleanup rule, prior to using any other rule where those characters could cause issues. Also, worth mentioning is an interesting article describing how to Use Unicode Normalization to Represent Strings.
I think this could be the best option, since there is more characters that present the problem, not just the "ñ".
If this software has helped you, consider getting your pro version. :)
Offline
I have tested now the insert rule, the compound ñ does also alter the count of character. Being possible to insert something between both separating them.
I think there will be probably more of this problems. But I don't think ReNamer can do much about it.
I would like to have the name normalized by default, but for other users it might not be the best option. So the only thing left is the cleanup rule.
If this software has helped you, consider getting your pro version. :)
Offline