Bug 3012 - Unicode characters and CLI
: Unicode characters and CLI
Status: RESOLVED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: CLI
: 6.5b1
: PC Windows XP
: P2 major (vote)
: ---
Assigned To: Dan Sully
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-02-16 04:55 UTC by steliosb
Modified: 2006-02-22 23:33 UTC (History)
3 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description steliosb 2006-02-16 04:55:41 UTC
When using CLI 
for example
title $player ?

and the title has unicode characters then slim.exe reports the following error and closes

Can't escape \x{039C}, try uri_escape_utf8() instead at
/PerlApp/Slim/Control/CLI.pm line 618

When title has latin characters then it returns the title correct 

PS. title is just an example, it happens when CLI returns anything with unicode characters
Comment 1 KDF 2006-02-16 08:48:07 UTC
same response as your other report.  please try nightly builds, and please leave target milestone unset.  As it is, 6.2.1 can no longer be a practical target at this point. thanks.

for CLI, there has been a large restructuring as part of 6.5 builds.
Comment 2 Fred 2006-02-16 10:12:43 UTC
Duplicate of 2788, fixed eons ago on 6.2.x and 6.5. Yes 6.2.1 has a bug there.
Comment 3 KDF 2006-02-16 10:19:58 UTC
Thanks Fred.  Steliosb, please download the nightly builds and create new reports if you still have issues there, and a search does not show a duplicate report.

*** This bug has been marked as a duplicate of 2788 ***
Comment 4 Fred 2006-02-16 11:58:37 UTC
In all fairness, kdf, a standard search does not return "RESOLVED" issues. You have to go and select "RESOLVED" in the advanced search tab... Not sure how to fix that, maybe we should have an intermediate stage like "FIXED in SVN" or something, or leave everything open until the SW is released?
Comment 5 steliosb 2006-02-17 01:04:55 UTC
I tried the latest nightly build
This issue still exists even in 6.5b

for example :
TRY TO SEND SOME UNICODE CHARACTERS (GREEK HERE) TO BE DISPLAYED TO SQUEZEBOX WITH THE FOLLOWING COMMAND 

display �������� �������� 30

THEN THEN UNICODE CHARACTERS ARE NOT DISPLYED CORRECT AT THE SQUEEZEBOX DISPLAY
Comment 6 KDF 2006-02-17 09:05:21 UTC
please do not use all caps.  This is a developer tool, and not for screwing around.

The instructions on the main page say to search for "open OR resolved" issues.

In all fairness, I simply asked for the search to be done in future, as I have asked repeatedly.
Those who wish to keep banging at bugzilla as a support forum should be learning to use it properly.
Fred, you should be encouraging proper use.

My guess is stelios will keep screaming until you make him happy.
Comment 7 KDF 2006-02-17 10:23:37 UTC
I also wonder if there is something of a hint as to why there is a problem, in that the above example shows as a unicode replacement character (FFFD) instead of any sort of greek character.  I think all windows settings issues need to be eliminated here.  I'm running win2k, and I am seeing proper international characters in other bug reports.  Could the input settings be causing the problems?  It would explain at least two of steliosb's unicode bugs. 

steliob, what input locale settings are you using?
Comment 8 Fred 2006-02-18 04:31:13 UTC
I get the characters correctly here. Accented capitals.

If this is what you try to enter using telnet, it won't work. The strings have to be url-encoded, as indicated in the CLI documentation. �� for example is C3%86%C3%87.

display C3%86%C3%87 C3%86%C3%87 30 should show �� on both player lines.
Comment 9 steliosb 2006-02-20 02:02:53 UTC
(In reply to comment #8)
> I get the characters correctly here. Accented capitals.
> If this is what you try to enter using telnet, it won't work. The strings have
> to be url-encoded, as indicated in the CLI documentation. �� for example is
> C3%86%C3%87.
> display C3%86%C3%87 C3%86%C3%87 30 should show �� on both player lines.


SlimServer Version: 6.5b1 - 6273 - Windows XP - EN - cp1253 

i tried urlencoding using ( php's rawurlencode()) but no chance

your test
display C3%86%C3%87 C3%86%C3%87 30 
does not display ZH
Comment 10 Fred 2006-02-20 03:51:15 UTC
Now that I am able to test (was travelling last week), I agree it does not work. Will investigate.
Comment 11 Fred 2006-02-20 14:37:42 UTC
Fixed in 6318. Please try it again in the next nightly.
Comment 12 malcolmwotton 2006-02-22 06:11:39 UTC
Everyone,

This fix breaks lots of other things - just noticed the connection, I've raised a bug 3045 with the other problem.

Malcolm
Comment 13 steliosb 2006-02-22 23:12:23 UTC
(In reply to comment #11)
> Fixed in 6318. Please try it again in the next nightly.

Yes it fixes it but I have now, new  problems regarding playlist saving when playlist names are written in characters other than latin.

Please tell me because I am new here.

can I just replace an updated *.pm file to my current slimserver installation or the hole slimserver must be recompiled?

the fixes regard only to 6.5x versions or at the same time to 6.2x series ?
Comment 14 KDF 2006-02-22 23:33:43 UTC
If you have installed the Windows EXE version, then you have to install a new nightly build in order to get updates.

If you install ActivePerl (http://www.activestate.com) then you can update or edit a *.pm file and use slimserver.pl to run the server, instead of slim.exe.  The slimTray app would no longer work for this, but you can use firedaemon to make slimserver.pl into a service.

Fixes to 6.5 affect 6.5, fixes to 6.2.2 affect 6.2.2.  Since this bug was reported against 6.5, only 6.5 is fixed.  The CLI is heavily changed for 6.5, so some fixes cannot be back-ported to 6.2.2 if this same problem exists there (not mentioned previously).  New features are kept in 6.5, and critical fixes are ported to 6.2.2 where possible.

the playlist saving problem is noted in bug 3026, so please keep those issues with that report.  likely that one is related to another problem with entering unicode chars into form inputs.

Since this one is fixed, marking as such.  Users can re-open if there are remaining issues.