-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Fred, Am 28.08.2016 um 06:48 schrieb Frederic Muller - DFF:
Thank you for the answer. We actually discuss with the topic at length with Alexandro and maybe others 3 years ago. There was a small bug in the display of the SVG between Inkscape and the rendering engine making the text slightly off.
- - Rendering engine? You mean the browser?
That's about as much as I remember. I can't even remember how to edit the file now if it's not using a text editor.
- - That I can do ;-)
So back to what we want is actually replacing the current PNG files for our countdown with SVG file(s). We believe this would help us better manage translations and re-editing the file year after year. So it should be able to display the SFD countdown image (we have the SVG source so that should be ok) and deduct 1 day everyday as we get closer to SFD. Also the current availability of the files make it possible for people to chose the SFD date based on their timezone. So it is pretty simple to just copy & paste the code and insert it in a blog or website.
- - You want the thing to work client-side, right? Not via a script that serves the image-of-the-day from the sfd website? That's what I gather from the unfinished SVG file in the Wiki. That's actually the hard part for including in a blog. You need to use iframe, embed or object tags, or paste the source of the image directly into the html to get the counter js to work, if it's included in the SVG image, as far as I know. img tags will *not* work. So would the iframe thing be desirable? I'm not sure if everyone can include one on their blog, that's why I'm asking. Or would it be more practical to create those 60 svg (or even better, png) files automatically and have them work like the pngs currently? That's easy to do with Inkscape and either some own scripting or a preexisting Inkscape extension. That's a solution which would work for everyone, but would still require that a script be run on your server (which requires a gui if one uses Inkscape for it... :/) or on the translators' local machines to create the single svg/png files. We should also make sure to either use a font that is readily available for everyone, to convert the text to paths in the process (using Inkscape), or to include/link to the font file when using an SVG, or just to use a png. Do you have any preferences? Or would you just like to have it work easily? What I would do is: - - modify the SVG image - - add instructions for translators into the svg file, ask them to install the necessary fonts, so they can adapt the size of their texts correctly - - only have them translate those few strings, then ask them to upload the changed SVG file - - provide instructions how to generate the pngs automatically, using Inkscape (with gui) and a csv file for the dates on a computer where the required fonts are installed - - have you continue serving the png images using the working script you have It's less sophisticated, and less automatical, than the js version, but makes work easy for translators and works for all kinds of blogs. Even when you visit them using IE ;-) What do you think? (If you prefer the other option, I would also prepare the file for the iframe/embed/object option, only my javascript foo is weak - I can tell you the steps that need to be performed / the ids that would need to be adapted, but can't write it myself). Regards, Maren -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJXwxA4AAoJELavtZto4hQPTssP/2lpvPYnBl/fQSmVBeBr+W0R LTOBSRnzPjcAYQK0lGSwUsi2NehiTPHA0K80dE2kKsERIBd9EAZE2CKPJmdj1N+Q NmUqV0x0JZbNBvHjEkupL/V9PZUaocj6Gs4/gj5Gzs6Y4f7Oi/8J+0j8t/FQhah3 /1XftWppe9kugO/Qjkc2QslTsE1z2L1xfoUPQ2pf35MDzlsdzHxLLUO2KQyBcdoz eZ5KVTro8+65vBbHO48mFvKBbVWm9DKTAIflkIOt67CDqcd/ApW1Km28v8VIEhuc 8BSpZ/1DH7rjmscfYn+M4iNOIWyo1fNBC49bAiXNKhlvS3BRDkd5LG/c4gshLabo Q79ltKATl4ioYcIPX+iy9EBkdIq/lQH1YUybYEEbuBO13dV3shtQUMuOHOCjA2cv RME5hs7T9KPwk5fCmXCNHqT4UHDTUtOxxbW9F/SdQh3kQwRR9PtdxEthdWdHnId2 bpyMx7pOWWJSYVdCjU0VBZ/bBe5uSTJEYnDQqNsBTzMfKw/9GGkVJBySlw8ooxFl Sbv1l9TTtASFyHLG8QJlnCaQa/DC0uonNYvF32UYc9HSt0ee6JFmiC9fddh1CY/U fWJDQuEChk8g+oz8a53ansPqgj3tObV3doGmqi4vj4lSi4sE8CFrzTwHWIxhGk+6 bwLFg8TEB/05eD12yB7E =3vAo -----END PGP SIGNATURE-----