Opened 9 years ago

Closed 2 years ago

#1980 closed Enhancement (invalid)

add support for title metainfo

Reported by: castorinop Owned by:
Priority: Normal Milestone: None Set
Component: Transmission Version: 1.52
Severity: Normal Keywords:
Cc:

Description

this patch provide title metainfo support for cli, daemon/remote and gtk.

Attachments (1)

transmission-1.51-metainfo_title.001.patch (10.2 KB) - added by castorinop 9 years ago.

Download all attachments as: .zip

Change History (13)

Changed 9 years ago by castorinop

comment:1 Changed 9 years ago by charles

  • Milestone changed from 1.52 to None Set

Thank you for the patch, but... where is the 'title' tag coming from? What other clients support this tag?

comment:2 Changed 9 years ago by livings124

I've never heard of this "title" tag. Is there documentation of this somewhere?

comment:3 Changed 9 years ago by castorinop

bittorrent 5.2.0 support that.

comment:4 Changed 9 years ago by livings124

The client supports the field? What is the field for? Where is the documentation for it?

comment:5 Changed 9 years ago by castorinop

in mi case set a title or someone more descriptive that name field and is very usefull when 2 resources share same parent dir.

for example: torrent a content: commondir/resource-a/ torrent b content: commondir/resource-b/ for both torrents the name field is commondir (very common on transmision-daemon/remote) but the content is different. If create torrent with title field, you can set (example) "commondir - resource-a" or "commondir - resource-b" can be view the diference between them in the torrent's list.

comment:6 Changed 9 years ago by livings124

Is there a specification of this anywhere? I would feel more comfortable considering this if there was documentation of this field.

comment:7 Changed 9 years ago by charles

castorinop: ping

comment:8 Changed 9 years ago by castorinop

i contact a Greg Hazel for ask about this topic and answer:

Hi.

The 'title' field is simply a key/value pair on the root level of the metafile. However, it is not really used in practice, so there is no official spec.

Hope this helps,

-Greg

comment:9 Changed 9 years ago by charles

  • Resolution set to invalid
  • Status changed from new to closed

If this isn't really used in practice, I don't see the benefit in adding this feature.

Thanks for the patch though. It was pretty well-written.

comment:10 Changed 9 years ago by castorinop

so bad...

comment:11 Changed 2 years ago by koisama

  • Resolution invalid deleted
  • Status changed from closed to reopened
  • Version changed from 1.51 to 2.92

I would like to reopen this ticket.

It's possible to have folder structure where data is stored in subfolders with the same names. In this case it will be impossible to tell different torrents apart without examining the path.

In this example you will have 3 "format 2" torrents:

./root
  /Title 1
    /format 1
    /format 2
  /Other Title
    /format 2
  /Yet another Title
    /format 2
    /format 3

comment:12 Changed 2 years ago by mike.dld

  • Resolution set to invalid
  • Status changed from reopened to closed
  • Version changed from 2.92 to 1.52

Titles could be duplicated as well, I don't see how it would help. On the contrary, it could bring confusion as part of torrents will be displayed using file/directory names and another part using titles. And is there still no documentation on this?..

Note: See TracTickets for help on using tickets.