Apostrophe's in metadata now have two trailing spaces?

[peternm22]

Fairly new to BMT, but really liking it so far. Ran into an odd formatting issue today. See attached image.

I'm fairly certain this is a BMT problem, as there are no extra spaces on the TVDB page for this episode: http://thetvdb.com/?tab=episode&seri...=5353324&lid=7

Any ideas? Any button/knob/pulley for me to push/twist/pull?

Thanks.

[Skirge01]

I've seen this pretty regularly in the description, but I don't recall ever seeing it in the title. I'd tend to agree that it's a BMT issue, but I'm not sure it will be fixed [any time soon?]. I think stuckless is focused pretty exclusively on the OSS version of Sage for the time being.

There are several other longstanding issues with BMT (most are fairly minor), as well.

[Fuzzy]

Originally Posted by Skirge01

I've seen this pretty regularly in the description, but I don't recall ever seeing it in the title. I'd tend to agree that it's a BMT issue, but I'm not sure it will be fixed [any time soon?]. I think stuckless is focused pretty exclusively on the OSS version of Sage for the time being.

There are several other longstanding issues with BMT (most are fairly minor), as well.

Well, anyone can work on finding bugs and fixes if they choose:
https://github.com/stuckless/sagetv-phoenix-core

[stuckless]

Not saying this is NOT a BMT issue, but, I'm wondering if it's a Unicode issue. (TVDB is riddled with Apostrophe issues).

The title in question looks innocent enough...

You’re Not Yelping

But that apostrophe is not a standard ' it's a ’ (see the difference)

It shouldn't matter, but, depending on the font, and/or how sagetv (or bmt) deals with the unicode character it could be causing the issue here.

When I URL encode the title, just to test if it has Unicode characters... I confirm my suspicions...

You%u2019re%20Not%20Yelping

u2019 is the Unicode character for the right single quote
http://www.fileformat.info/info/unic...2019/index.htm

If this were a standard single quote I would have expected to see %27 and not %u2019

I have unit tests in BMT/Phoenix typically will just pass that data, as is, along to the SageTV core where it gets stored in the Database. In my tests in Phoenix, when I get the data, it's good. If I get time, I'll try to test this specific title and see what Phoenix gets, etc.

[Skirge01]

Originally Posted by Fuzzy

Well, anyone with coding skills can work on finding bugs and fixes if they choose:
https://github.com/stuckless/sagetv-phoenix-core

Fixed that for you.

[Fuzzy]

Originally Posted by Skirge01

Fixed that for you.

I didn't say you had to be any good at it, or even succeed...

[Skirge01]

Originally Posted by Fuzzy

I didn't say you had to be any good at it, or even succeed...

[stuckless]

Keep in mind that while BMT (ie, the Web UI portion of Phoenix) is not being worked on, much of these types of problems are not Web UI related, but instead either problems in phoenix-core or sagetv. Phoenix Core is still being supported. I'm hoping to do some house cleaning on it, to remove parts that are no longer relevant, but for the most part, it'll be in use for the foreseeable future.

As for BMT, I'm hoping that either myself, or someone, will get the chance to actually do a full replacement for Mobile Web, Nielm's Web, and BMT, into a single web app using something more modern than GWT and JSP.

[Skirge01]

Originally Posted by stuckless

Keep in mind that while BMT (ie, the Web UI portion of Phoenix) is not being worked on, much of these types of problems are not Web UI related, but instead either problems in phoenix-core or sagetv. Phoenix Core is still being supported. I'm hoping to do some house cleaning on it, to remove parts that are no longer relevant, but for the most part, it'll be in use for the foreseeable future.

As for BMT, I'm hoping that either myself, or someone, will get the chance to actually do a full replacement for Mobile Web, Nielm's Web, and BMT, into a single web app using something more modern than GWT and JSP.

Thanks for pointing that out as it's often forgotten, if known at all. I think most of us non-coders think of BMT & the Phoenix API as the same thing. While I'm actually aware that the API is used for a ton of different things, I really don't know which part of what I (the user) see is from BMT, Phoenix, or a host of other plugin dependencies which just magically make things work for me. Because of that, we post in the thread which applies to the parts we do see.

Regardless, thanks for everything you do for Sage!