openlp-core team mailing list archive

[robsmith <773036@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

While attempting to open a powerpoint presentation I got the following
error message:

"Unsupported file
This type of presentation is not supported"

Which was rather strange as I'd just used powerpoint to generate the
presentation (MS office 2000 sp 3), and powerpoint would re-open
correctly.

Investigation points to the name having more than one "." in it (the
name being dictated by a corporate policy which requires the use of "."
as certain places...)

Renaming the file to the same name, but without the additional "."
allows the file to be loaded.

This is reproducible with even the simplest single slide presentation
with a name like "test.1.ppt" failing to load.

This behaviour is contrary to the windows file naming rules which state
that "." are allowed within the name, the final one being used to
identify the file extension.

** Affects: openlp
     Importance: Undecided
     Assignee: Jonathan Corwin (j-corwin)
         Status: New

-- 
You received this bug notification because you are a member of OpenLP
Core, which is subscribed to OpenLP.
https://bugs.launchpad.net/bugs/773036

Title:
  Invalid type when opening a powerpoint presentation

Status in OpenLP - Worship Presentation Software:
  New

Bug description:
  While attempting to open a powerpoint presentation I got the following
  error message:

  "Unsupported file
  This type of presentation is not supported"

  Which was rather strange as I'd just used powerpoint to generate the
  presentation (MS office 2000 sp 3), and powerpoint would re-open
  correctly.

  Investigation points to the name having more than one "." in it (the
  name being dictated by a corporate policy which requires the use of
  "." as certain places...)

  Renaming the file to the same name, but without the additional "."
  allows the file to be loaded.

  This is reproducible with even the simplest single slide presentation
  with a name like "test.1.ppt" failing to load.

  This behaviour is contrary to the windows file naming rules which
  state that "." are allowed within the name, the final one being used
  to identify the file extension.