Thanks for the answer Hussein, That's perfectly clear. It would maybe require an entry in the FAQ or somewhere else since this behaviour has changed quite recently ?
Best regards, Vincent Hussein Shafie a ?crit : > Vincent Vandenschrick wrote: > >> I've migrated this morning to the latest 4.1.0 release and found out >> that most of the JPEG images were not drawn anymore. After a bit of >> investigations, it seems like the problem comes from images with >> filenames containing "dots" in addition to the final one before the >> extension. >> For instance "test.image.jpg" is not displayed correctly whereas >> "test-image.jpg" works. So I replaced all "dots" by "dash" and >> everything worked fine again. >> > > The file extension of "test.image.jpg" is considered to be "image.jpg" > and not "jpg". And, of course, "image.jpg" is an unsupported format. > > This seems stupid because, in your case, the file extension is obviously > "jpg". But in the general case, this is not always true. Example: > xxe-perso-4_1_0.tar.gz (the file extension is "tar.gz" and not "gz") > > Therefore, we are currently not 100% sure that this problem needs to fixed. > > > > >> To be complete, it seems that the XML parsing gets rid of the filename >> part before the first "dot" (xmleditor shows this "reworked" filename in >> bold blue) >> >> > > Not really. When XMLmind XML Editor needs to display an image for which > the format is not supported, it uses the image placeholder icon and > superimpose to this icon the file extension written in bold blue letters > (in your case, the file extension is "image.jpg"). > > > -- Vincent Vandenschrick Jspresso Project Leader http://www.jspresso.org
