INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: Special characters  (Read 987 times)

aliciaviola

  • Galactic Citizen
  • ****
  • Posts: 393
Special characters
« on: March 10, 2020, 07:22:26 am »

Once again, because the problem still has not be solved, the urgent prayer to solve the "special character problem".
Any word, containing a special character (Ä, ö, ü, é, è, î....) copied from a MAC program (with the exception of Google Crome!) appears broken when pasted into a MC tag field.
In the example you can see in the appended pictures I wrote the tags in Metadatics and then imported them in MC. As you can see some of the tag fields show the name "Mäkelä" in the correct way, some not.

Frank
Logged

bob

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 13488
Re: Special characters
« Reply #1 on: March 13, 2020, 11:38:20 am »

I just tried this from Safari and Notes without any trouble.

Pasted this into a conductor field
Vänskä

Looks fine.
Logged

HaWi

  • Citizen of the Universe
  • *****
  • Posts: 905
Re: Special characters
« Reply #2 on: March 13, 2020, 03:01:39 pm »

I just tried this from Safari and Notes without any trouble.

Pasted this into a conductor field
Vänskä

Looks fine.
I see the same, however, in the case of my spaces and hyphens that I have investigate a bit more, while they copy and paste fine and look the same, they are still different when you try to "find" them with an expression. In other words, if I copy and paste a hyphen from some source it behaves differently in a find command executed in MC versus when I type it on the keyboard; the typed hyphen/space is found while the pasted hyphen/space is not. Have you tried to compare the typed version of Västä or, say, Dvořak, with the copy/pasted version in a find/replace scenario? I'm just just curious.
Best regards,
Hans
Logged
rPi5/8GB, Debian 12 Bookworm on SSD | JRMark (32.0.36 64 bit): 2699
MacBookPro (2013), 2.6 GHz Quad-Core Intel Core i7, MacOS 11.7.17 | JRMark (32.0.38 64 bit): 3764
Mac Studio M2 Max, 64GB, 1TB SSD, macOS Sonoma 14.4.1 | JRMark (32.0.38 64 bit): 9235
Docker Container (shiomax) DS1819+ | JRMark (32.0.36 64 bit): 1430
JRemote 3.43
MO 4Media 1.5.7 | Marantz SR7007 (RSL 5.1) HDMI to MacBookPro

bob

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 13488
Re: Special characters
« Reply #3 on: March 13, 2020, 03:14:27 pm »

I see the same, however, in the case of my spaces and hyphens that I have investigate a bit more, while they copy and paste fine and look the same, they are still different when you try to "find" them with an expression. In other words, if I copy and paste a hyphen from some source it behaves differently in a find command executed in MC versus when I type it on the keyboard; the typed hyphen/space is found while the pasted hyphen/space is not. Have you tried to compare the typed version of Västä or, say, Dvořak, with the copy/pasted version in a find/replace scenario? I'm just just curious.
Best regards,
Hans
The hypen for example probably needs to be a UTF-8 character when it's in a tag, it probably isn't always when it's being copied from a web or other resource.
Logged

Gretschguy

  • Recent member
  • *
  • Posts: 8
Re: Special characters
« Reply #4 on: March 14, 2020, 01:00:22 am »

Is this related to the same problem whereby handheld devices do a full resync and re-load of all files if the file names contain certain characters (dashes might be the problem in my case)?  So frustrating.
Logged

HaWi

  • Citizen of the Universe
  • *****
  • Posts: 905
Re: Special characters
« Reply #5 on: March 14, 2020, 11:34:16 am »

The hypen for example probably needs to be a UTF-8 character when it's in a tag, it probably isn't always when it's being copied from a web or other resource.
That could definitely be the issue. I find it a bit sad that in the 21st century such differences still exist. I don't know much about character encoding but kind of assumed we have a universal standard by now. Is there a way to find out, in MacOS, whether a certain character is UTF-8 or not? Or is there a way to automatically force a conversion when it isn't UTF-8?
cheers,
Hans
Logged
rPi5/8GB, Debian 12 Bookworm on SSD | JRMark (32.0.36 64 bit): 2699
MacBookPro (2013), 2.6 GHz Quad-Core Intel Core i7, MacOS 11.7.17 | JRMark (32.0.38 64 bit): 3764
Mac Studio M2 Max, 64GB, 1TB SSD, macOS Sonoma 14.4.1 | JRMark (32.0.38 64 bit): 9235
Docker Container (shiomax) DS1819+ | JRMark (32.0.36 64 bit): 1430
JRemote 3.43
MO 4Media 1.5.7 | Marantz SR7007 (RSL 5.1) HDMI to MacBookPro

bob

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 13488
Re: Special characters
« Reply #6 on: March 14, 2020, 12:41:17 pm »

That could definitely be the issue. I find it a bit sad that in the 21st century such differences still exist. I don't know much about character encoding but kind of assumed we have a universal standard by now. Is there a way to find out, in MacOS, whether a certain character is UTF-8 or not? Or is there a way to automatically force a conversion when it isn't UTF-8?
cheers,
Hans
Is there any consistency in the types of files that the issue shows up in?
Logged

HaWi

  • Citizen of the Universe
  • *****
  • Posts: 905
Re: Special characters
« Reply #7 on: March 14, 2020, 07:07:14 pm »

I am not sure but it might have been files I ripped from CDs
Cheers
Hans
Logged
rPi5/8GB, Debian 12 Bookworm on SSD | JRMark (32.0.36 64 bit): 2699
MacBookPro (2013), 2.6 GHz Quad-Core Intel Core i7, MacOS 11.7.17 | JRMark (32.0.38 64 bit): 3764
Mac Studio M2 Max, 64GB, 1TB SSD, macOS Sonoma 14.4.1 | JRMark (32.0.38 64 bit): 9235
Docker Container (shiomax) DS1819+ | JRMark (32.0.36 64 bit): 1430
JRemote 3.43
MO 4Media 1.5.7 | Marantz SR7007 (RSL 5.1) HDMI to MacBookPro

aliciaviola

  • Galactic Citizen
  • ****
  • Posts: 393
Re: Special characters
« Reply #8 on: March 17, 2020, 10:45:52 am »

It doesn't happen if there is already the identical name - as in the conductor's or artist/artist-album - but with all new copy and paste things (save from Google Chrome).
Logged
Pages: [1]   Go Up