From: Maxwell, A. R <ada...@pn...> - 2005-05-31 18:24:37
|
On May 31, 2005, at 11:10, Christiaan Hofman wrote: > > On May 31, 2005, at 19:52, Maxwell, Adam R wrote: > > >> >> On May 31, 2005, at 09:37, Geoffrey Simms wrote: >> >> >>> On a related note, I have had a couple of articles with slashes >>> "/" within the title, and using the title as part of the autofile >>> filename, they got filed in a subdirectory even though I didn't >>> want this. I just tested this again with 1.0RC2 and it still >>> behaves that way. >>> >>> Perhaps string fields embedded in autofile names should be >>> escaped to prevent inadvertent subdirectory filing, but directory >>> separators should be allowed in the overall autofile naming >>> template. >>> >> >> This should not happen. Please file a bug report at <http:// >> sourceforge.net/tracker/?group_id=61487&atid=497423> so we can >> track this issue and fix it. >> >> thanks, >> Adam >> >> > > Hmm, I actually have sort of the opposite: I use a field containing > the slashes, which I _want_ to use to build a subdirectory > structure. I am not sure how we should handle this in general. > Replace "/" for certain fields (such asTitle), or perhaps all > fields but based on a preference option? Yes, I realized the same thing shortly after I sent that message, since I do the same thing that you mention. Maybe we could have a checkbox for "replace slashes in standard fields", which would only operate on btxdoc-defined fields? I'm not sure if there is a clean way to do this, though. Adam |