Quote from: Marc at Apr 13, 2006, 02:17 PMIt must be what mike is saying, charset support has been added to php htmlentities function at PHP 4.1.0. I could do an option that the charset from modx will be used if enabled.. and possibility to define the charset in the snippet call also. I’ll look into this.
Another point: In the description of an image, the Utf-8 encoding is not recognized. An accentuated character as the ’ é’ (in French) is translated into ’é’
I tested the special characters (frequently used in France) with version 3. The characters éè’àçöü’ù"ô€"&² are posted correctly.
Quote from: doze at Apr 14, 2006, 12:03 PM
Quote from: Marc at Apr 13, 2006, 02:17 PMIt must be what mike is saying, charset support has been added to php htmlentities function at PHP 4.1.0. I could do an option that the charset from modx will be used if enabled.. and possibility to define the charset in the snippet call also. I’ll look into this.
Another point: In the description of an image, the Utf-8 encoding is not recognized. An accentuated character as the ’ é’ (in French) is translated into ’é’
The user who reported this problem with etogal removed the htmlentities call from the display of the component he was using. This might be an option for Marc if he knows PHP code. Its not an ideal solution, as the call is there to stop you inadvertently mangling the HTML for the page by a ’special’ character in the text, but it may be a useful stopgap.
The code what Marc used is not the version 0.3. I sent him some new code to try last night, I still want to do bit more testing with it before I release it (can’t test it myself). But it will be in the next release.
I tested the special characters (frequently used in France) with version 3. The characters éè’àçöü’ù"ô€"&² are posted correctly.
Thanks for your works
Sorry. I thought of having the version v0.3.
Quote from: Marc at Apr 14, 2006, 05:30 PMThe code what Marc used is not the version 0.3. I sent him some new code to try last night, I still want to do bit more testing with it before I release it (can’t test it myself). But it will be in the next release.
I tested the special characters (frequently used in France) with version 3. The characters éè’àçöü’ù"ô€"&² are posted correctly.
Thanks for your works
The idea is to protect the images from a copy. The solution to put a watermark does not function. For my part, this point is not very significant
Quote from: Marc at Apr 13, 2006, 02:17 PMI tested the solution: it generates an image increased and not protected by the copy.Sorry, but I don’t understand what you are saying..Could you post your snippet call and a site where I could see the results, if you are having problems?
The idea is to give, for the user, the posibility to sail between the great images. Currently, it must return at the lower level to see or the page of index to make this navigation. That remains an idea but I think that it is complex to implement. It is easier to give ideas than to carry them out.
Quote from: Marc at Apr 13, 2006, 02:17 PMThat option is to show an original/bigger version of some picture in a gallery and it’s not supposed to have the next/prev links. It could be built to have them, but I didn’t think that it would be needed. What you guys think about it, is it needed?
I have one question: Why in the presentation of the gallery in ’ dropshadow and imagemasking ’, once the image increased, one does not find the links ’ Next’ and ’ Previous’ as in embedded gallery?
The v0.3 has the ability to disable rightclick, just use &disable_rightclick=`1` in the snippet call. But as said many times, visitors can still get the pics if they want quite easily from cache/source. It’s not really possible to protect pictures on the net, other than using watermark that overlays the image.
The idea is to protect the images from a copy. The solution to put a watermark does not function. For my part, this point is not very significant
Yes, you must return back to the lower level. Also the picture descriptions will not be visible in the large pics view. When I get the time to update the slidebox, it would be easy to do the next/prev links to the larger images too. But if user then navigates in the slidebox to next/prev images, the "lover level" in the background would still stay on the current image. I may do this in some point, but not likely to happen soon (unless there will be alot more people wanting this)
The idea is to give, for the user, the posibility to sail between the great images. Currently, it must return at the lower level to see or the page of index to make this navigation. That remains an idea but I think that it is complex to implement. It is easier to give ideas than to carry them out.
Thanks, Included to the next version.
I modifed a file for the futur version lang_fr.zip
Marc, watermarking is not intended to prevent people from copying an image. It is only intended to modify the image so that nobody would want to copy it or so that it would be easily identified if someone did copy it and try to use it elsewhere.
Quote from: Marc at Apr 15, 2006, 08:41 AMThe v0.3 has the ability to disable rightclick, just use &disable_rightclick=`1` in the snippet call. But as said many times, visitors can still get the pics if they want quite easily from cache/source. It’s not really possible to protect pictures on the net, other than using watermark that overlays the image._fr.zip[/url]
The idea is to protect the images from a copy. The solution to put a watermark does not function. For my part, this point is not very significant
@dave : Thank you for the explanations. I am not an expert on the image processing and I discover with this snippet the jargon and the tools used in this field.
Quote from: doze at Apr 15, 2006, 02:29 PMMarc, watermarking is not intended to prevent people from copying an image. It is only intended to modify the image so that nobody would want to copy it or so that it would be easily identified if someone did copy it and try to use it elsewhere.
Quote from: Marc at Apr 15, 2006, 08:41 AMThe v0.3 has the ability to disable rightclick, just use &disable_rightclick=`1` in the snippet call. But as said many times, visitors can still get the pics if they want quite easily from cache/source. It’s not really possible to protect pictures on the net, other than using watermark that overlays the image._fr.zip[/url]
The idea is to protect the images from a copy. The solution to put a watermark does not function. For my part, this point is not very significant
[!MaxiGallery? &pics_in_a_row=`4` &max_thumb_size=`110` &max_pic_size=`400` &keep_bigimg=`1` &thumb_use_dropshadow=`1` &thumb_use_watermark=`1` &thumb_watermark_txt=`Copyright MAC` &pic_use_mask=`1` &pic_use_imagemask=`1` &pics_per_page=`12` &pic_mask_img=`assets/snippets/maxigallery/imagemask/mask-copyright.png` &big_use_watermark=`1` &big_img_linkstyle=`slidebox` &big_use_mask=`1` &big_use_imagemask=`1` &titles_in_overview=`1` &big_mask_img=`assets/snippets/maxigallery/imagemask/mask-logo.png`!]
<script type="text/javascript">var xml_url = 'assets/galleries/[*id*]/gallery.xml';</script> <script type="text/javascript" src="[(site_url)]assets/snippets/maxigallery/slidebox/slidebox_lang_fr.js"></script> <script type="text/javascript" src="[(site_url)]assets/snippets/maxigallery/slidebox/slidebox.js"></script> <script type="text/javascript" src="[(site_url)]assets/snippets/maxigallery/slidebox/prototype.js"></script> <link rel="stylesheet" href="[(site_url)]assets/snippets/maxigallery/slidebox/style.css" type="text/css" media="screen" />
<script type="text/javascript" src="[(site_url)]assets/snippets/maxigallery/js/external.js"></script> <script type="text/javascript" src="[(site_url)]assets/snippets/maxigallery/js/popup.js"></script> <script type="text/javascript" src="[(site_url)]assets/snippets/maxigallery/lightboxv2/js/effects.js"></script> <script type="text/javascript" src="[(site_url)]assets/snippets/maxigallery/lightboxv2/js/lightbox.js"></script> <script type="text/javascript" src="[(site_url)]assets/snippets/maxigallery/lightboxv2/js/prototype.js"></script> <script type="text/javascript" src="[(site_url)]assets/snippets/maxigallery/lightboxv2/js/scriptaculous.js"></script> <link rel="stylesheet" href="[(site_url)]assets/snippets/maxigallery/slidebox/style.css" type="text/css" media="screen" /> <link rel="stylesheet" href="[(site_url)]assets/snippets/maxigallery/lightboxv2/css/lightbox.css" type="text/css" media="screen" />
This discussion is closed to further replies. Keep calm and carry on.