I have been working on this problem for a few weeks, and I am not able to get the rasterization of inline conversion of SVG into PNG to work properly with rsvg. ANy help on setup instructions for this would be appreciated.
Thanks
Jeff
Jeffrey V. Merkey wrote:
I have been working on this problem for a few weeks, and I am not able to get the rasterization of inline conversion of SVG into PNG to work properly with rsvg. ANy help on setup instructions for this would be appreciated.
Thanks
Jeff _______________________________________________ Wikitech-l mailing list Wikitech-l@wikimedia.org http://mail.wikipedia.org/mailman/listinfo/wikitech-l
And if its just plain broken, someone let me know this fact.
Jeff
Jeffrey V. Merkey wrote:
I have been working on this problem for a few weeks, and I am not able to get the rasterization of inline conversion of SVG into PNG to work properly with rsvg. ANy help on setup instructions for this would be appreciated.
Jeffrey, thank you for posting in a tech list instead of foundation-l, but since this is not the first such question you have asked, please please please read this document before continuing:
http://www.catb.org/~esr/faqs/smart-questions.html
-- brion vibber (brion @ pobox.com)
Ok Brion,
Here is a more complete question.
I have attempted to setup SVG to PNG rendering and it does not seem to work on 1.7.1. I checked the Defaults file in includes and I have verified rsvg is properly installed. I have also enabled the DebugLogFile option and attempted to run a trace the results indicate this section of code is not even activating as there are no messages being output to indicate that the RSVG section of code is even becoming active during rendering. The mine/type detection does appear to work in that SVG images are in fact detected. This would indicate an underlying problem in either te FC5 base I am using or the MediaWiki 1.7.1 code.
I have not found any other posts relative to 1.7.1 to indicate what fixes or problems exist for these cases. Is this a known problem in MediaWiki 1.7.1 and is it simply the intention of requiring SVG rendering in the browsers themselves by default?
Thanks
Jeff
Jeffrey V. Merkey wrote:
Ok Brion,
Here is a more complete question.
I have attempted to setup SVG to PNG rendering and it does not seem to work on 1.7.1. I checked the Defaults file in includes and I have verified rsvg is properly installed. I have also enabled the DebugLogFile option and attempted to run a trace the results indicate this section of code is not even activating as there are no messages being output to indicate that the RSVG section of code is even becoming active during rendering. The mine/type detection does appear to work in that SVG images are in fact detected. This would indicate an underlying problem in either te FC5 base I am using or the MediaWiki 1.7.1 code.
I have not found any other posts relative to 1.7.1 to indicate what fixes or problems exist for these cases. Is this a known problem in MediaWiki 1.7.1 and is it simply the intention of requiring SVG rendering in the browsers themselves by default?
Thanks
Jeff
Wikitech-l mailing list Wikitech-l@wikimedia.org http://mail.wikipedia.org/mailman/listinfo/wikitech-l
And Brion,
This is the most unprofessional and community hostile notice I have ever seen - if I read this right is says:
"...eat our stuff, bugs and all, and you are on your own if you need help, we don't care..."
:-)
Many project websites link to this document in their sections on how to get help. That's fine, it's the use we intended — but if you are a webmaster creating such a link for your project page, please display prominently near the link notice that /we are not a help desk for your project!/
We have learned the hard way that without such a notice, we will repeatedly be pestered by idiots who think having published this document makes it our job to solve all the world's technical problems.
If you're reading this document because you need help, and you walk away with the impression you can get it directly from the authors, /you/ are one of the idiots in question. Don't ask /us/ questions. We'll just ignore you. We are here to show you how to get help from people who actually know about the software or hardware you're dealing with, but 99% of the time that will not be us. Unless you know for /certain/ that one of the authors is an expert on what you're dealing with, leave us alone and everybody will be happier.
Jeff
This is the most unprofessional and community hostile notice I have ever seen - if I read this right is says:
"...eat our stuff, bugs and all, and you are on your own if you need help, we don't care..."
:-)
Many project websites link to this document in their sections on how to get help. That's fine, it's the use we intended — but if you are a webmaster creating such a link for your project page, please display prominently near the link notice that /we are not a help desk for your project!/
We have learned the hard way that without such a notice, we will repeatedly be pestered by idiots who think having published this document makes it our job to solve all the world's technical problems.
If you're reading this document because you need help, and you walk away with the impression you can get it directly from the authors, /you/ are one of the idiots in question. Don't ask /us/ questions. We'll just ignore you. We are here to show you how to get help from people who actually know about the software or hardware you're dealing with, but 99% of the time that will not be us. Unless you know for /certain/ that one of the authors is an expert on what you're dealing with, leave us alone and everybody will be happier.
That's from the http://www.catb.org/~esr/faqs/smart-questions.html#disclaimer page; In other words, the people who wrote how to ask better technical questions are simply saying "don't then proceed to ask us (the how-to-ask-questions-people) those technical questions; rather, ask it of the appropriate mailing list (or whatever) for the software in question". Which is what you've done ;-) I.e. It's not the MediaWiki people refusing to help you.
All the best, Nick.
Nick Jenkins wrote:
This is the most unprofessional and community hostile notice I have ever seen - if I read this right is says:
"...eat our stuff, bugs and all, and you are on your own if you need help, we don't care..."
:-)
Many project websites link to this document in their sections on how to get help. That's fine, it's the use we intended — but if you are a webmaster creating such a link for your project page, please display prominently near the link notice that /we are not a help desk for your project!/
We have learned the hard way that without such a notice, we will repeatedly be pestered by idiots who think having published this document makes it our job to solve all the world's technical problems.
If you're reading this document because you need help, and you walk away with the impression you can get it directly from the authors, /you/ are one of the idiots in question. Don't ask /us/ questions. We'll just ignore you. We are here to show you how to get help from people who actually know about the software or hardware you're dealing with, but 99% of the time that will not be us. Unless you know for /certain/ that one of the authors is an expert on what you're dealing with, leave us alone and everybody will be happier.
That's from the http://www.catb.org/~esr/faqs/smart-questions.html#disclaimer page; In other words, the people who wrote how to ask better technical questions are simply saying "don't then proceed to ask us (the how-to-ask-questions-people) those technical questions; rather, ask it of the appropriate mailing list (or whatever) for the software in question". Which is what you've done ;-) I.e. It's not the MediaWiki people refusing to help you.
All the best, Nick.
Wikitech-l mailing list Wikitech-l@wikimedia.org http://mail.wikipedia.org/mailman/listinfo/wikitech-l
OK. We should not be referring to our community members as "idiots". This is way out of line. The general tone raises some hairs on the back of my neck, but when it got to the term "idiot" I think this creates needless friction. I certainly understand why the developers would not want to deal with trivial issues and I agree with this. I also understand this was an off list posting, but Brion did refer to it as reference.
Jeff
"Jeff V. Merkey" jmerkey@wolfmountaingroup.com wrote in message news:450F34AA.3020209@wolfmountaingroup.com...
Nick Jenkins wrote:
That's from the http://www.catb.org/~esr/faqs/smart-questions.html#disclaimer page; In other words, the people who wrote how to ask better technical questions are simply saying "don't then proceed to ask us (the how-to-ask-questions-people) those technical questions; rather, ask it of the appropriate mailing list (or whatever) for the software in question". Which is what you've done ;-) I.e. It's not the MediaWiki people refusing to help you.
All the best, Nick.
OK. We should not be referring to our community members as "idiots". This is way out of line. The general tone raises some hairs on the back of my neck, but when it got to the term "idiot" I think this creates needless friction. I certainly understand why the developers would not want to deal with trivial issues and I agree with this. I also understand this was an off list posting, but Brion did refer to it as reference.
Jeff
(a) That is a message from the writers/maintainers of that article to people who have been directed to it by a third-party, as has happened here. They have no affiliation with MediaWiki and do not want to receive e-mails asking how to render inline SVG images into PNG on MediaWiki 1.7.1 from people who can't tell the difference between a mailing list and an unaffiliated web page.
(b) If you'd read to the end, you'd have seen this: http://www.catb.org/~esr/faqs/smart-questions.html#keepcool
Have a nice day!
- Mark Clements (HappyDog)
Mark Clements wrote:
"Jeff V. Merkey" jmerkey@wolfmountaingroup.com wrote in message news:450F34AA.3020209@wolfmountaingroup.com...
Nick Jenkins wrote:
That's from the http://www.catb.org/~esr/faqs/smart-questions.html#disclaimer page; In other words, the people who wrote how to ask better technical questions are simply saying "don't then proceed to ask us (the how-to-ask-questions-people) those technical questions; rather, ask it of the appropriate mailing list (or whatever) for the software in question". Which is what you've done ;-) I.e. It's not the MediaWiki people refusing to help you.
All the best, Nick.
OK. We should not be referring to our community members as "idiots". This is way out of line. The general tone raises some hairs on the back of my neck, but when it got to the term "idiot" I think this creates needless friction. I certainly understand why the developers would not want to deal with trivial issues and I agree with this. I also understand this was an off list posting, but Brion did refer to it as reference.
Jeff
(a) That is a message from the writers/maintainers of that article to people who have been directed to it by a third-party, as has happened here. They have no affiliation with MediaWiki and do not want to receive e-mails asking how to render inline SVG images into PNG on MediaWiki 1.7.1 from people who can't tell the difference between a mailing list and an unaffiliated web page.
It may be construed to be rather tacky to use that listing for third parties as a statement that reflects on the MediaWiki project.
(b) If you'd read to the end, you'd have seen this: http://www.catb.org/~esr/faqs/smart-questions.html#keepcool
I am cool. I seriously doubt that someone who invests large sums of money in MediaWiki sponsored companies likes being pointed to text that refers to them as an "idiot". I am not upset at all -- just making an observation.
:-)
Jeff
Have a nice day!
- Mark Clements (HappyDog)
Wikitech-l mailing list Wikitech-l@wikimedia.org http://mail.wikipedia.org/mailman/listinfo/wikitech-l
Hi!!!!
I am cool. I seriously doubt that someone who invests large sums of money in MediaWiki sponsored companies likes being pointed to text that refers to them as an "idiot".
If you're investing money into companies already sponsored by MediaWiki team, would you call ourselves partners? :)
Domas
Domas Mituzas wrote:
Hi!!!!
I am cool. I seriously doubt that someone who invests large sums of money in MediaWiki sponsored companies likes being pointed to text that refers to them as an "idiot".
If you're investing money into companies already sponsored by MediaWiki team, would you call ourselves partners? :)
Domas
Howdy partner. I am investing in a company that promotes the use of MediaWiki in Native American Language Preservation programs for Wikimedia content. Close enough. When my ban is lifted on the English Wikipedia, then I will start the money flow into the Foundation -- which is what I think you meant. In the meantime, I work on the Cherokee Wikipedia and Machine Translation Support for the Foundations projects -- I like the folks at Wikimedia.
:-)
Jeff
Wikitech-l mailing list Wikitech-l@wikimedia.org http://mail.wikipedia.org/mailman/listinfo/wikitech-l
Hi! Cool! Digs!
Howdy partner. I am investing in a company that promotes the use of MediaWiki in Native American Language Preservation programs for Wikimedia content. Close enough.
Good initiative. I'm working on use of mediawiki in Native European Language Preservation too!
When my ban is lifted on the English Wikipedia, then I will start the money flow into the Foundation -- which is what I think you meant. In the
Bans are set by communities. Foundation oversees operational issues, that supports many communities, including Native European Languages.
meantime, I work on the Cherokee Wikipedia and Machine Translation Support for the Foundations projects -- I like the folks at Wikimedia.
Great! I like them (Wikimedia people) too! I don't like machine translation though, because due to difficult ancient grammar constructs Native European Languages resist automatic conversions.
I actually even thought it would be great idea to have a special mailing list for native language preservation issues - your emails to foundation about new dumps etc don't get that much attention and does appear as a spam there. With a new mailing list you could send all your information about language preservation to interested folks like me!
Best regards, Domas
Domas Mituzas wrote:
Hi! Cool! Digs!
Howdy partner. I am investing in a company that promotes the use of MediaWiki in Native American Language Preservation programs for Wikimedia content. Close enough.
Good initiative. I'm working on use of mediawiki in Native European Language Preservation too!
When my ban is lifted on the English Wikipedia, then I will start the money flow into the Foundation -- which is what I think you meant. In the
Bans are set by communities. Foundation oversees operational issues, that supports many communities, including Native European Languages.
meantime, I work on the Cherokee Wikipedia and Machine Translation Support for the Foundations projects -- I like the folks at Wikimedia.
Great! I like them (Wikimedia people) too! I don't like machine translation though, because due to difficult ancient grammar constructs Native European Languages resist automatic conversions.
I actually even thought it would be great idea to have a special mailing list for native language preservation issues - your emails to foundation about new dumps etc don't get that much attention and does appear as a spam there. With a new mailing list you could send all your information about language preservation to interested folks like me!
Well, a lot of the pointless conversations on that list are spam to me -- I guess its a matter of perspective. Danny and Brad are both very interested in what I am doing and have been sending me grammar references and providing assitance, and spreading the reach of languages if the next horizon for the Foundation, not the folks who all rush to respond to Jimbo's emails with endless kiss-up all the time. David Gerard is a hard worker and several other folks, and Sabine and Dr. Benjamin were real great folks to hook up with there, so it's been helpful for all I think.
I am not interested in the Wikia competition and blasting someone as spam because they are a perceived competitor (which I am not -- Wikia is no competition at all). :-)
Jeff
Best regards, Domas
Jeffrey V. Merkey wrote:
Domas Mituzas wrote:
When my ban is lifted on the English Wikipedia, then I will start the money flow into the Foundation -- which is what I think you meant.
Regarding this comment, I cannot conribute directly to Wikimedia with a ban on the English Wikipedia in place -- it could be viewed in the wrong light by observers since folks would claim I "paid" for privileges. Better to let it run its course until Christmas when it is supposed to be lifted.
Jeff
On Tue, Sep 19, 2006 at 01:19:31AM -0600, Jeffrey V. Merkey wrote:
[ regarding ESR's Smart Questions paper ] It may be construed to be rather tacky to use that listing for third parties as a statement that reflects on the MediaWiki project.
(b) If you'd read to the end, you'd have seen this: http://www.catb.org/~esr/faqs/smart-questions.html#keepcool
I am cool. I seriously doubt that someone who invests large sums of money in MediaWiki sponsored companies likes being pointed to text that refers to them as an "idiot". I am not upset at all -- just making an observation.
I'm sure they don't.
This doesn't, however, mean that they *aren't* idiots. ESR is certainly a polarizing individual, and that as much as anything because he's blunt, and calls them like he sees them.
Whether how he sees them is reasonable is a-whole-nother argument, of course, but I personally am one of those people who answers lots of dumb questions from idiots -- idiots who *pay me* for the privilege, and that's why I don't lay ASQ on them. If they're asking me for *free*? You bet. If they think it's calling them an idiot, then maybe it is, and I might be so lucky as to have them ask someone else.
:-)
Cheers, -- jra
Jay R. Ashworth wrote:
On Tue, Sep 19, 2006 at 01:19:31AM -0600, Jeffrey V. Merkey wrote:
[ regarding ESR's Smart Questions paper ] It may be construed to be rather tacky to use that listing for third parties as a statement that reflects on the MediaWiki project.
(b) If you'd read to the end, you'd have seen this: http://www.catb.org/~esr/faqs/smart-questions.html#keepcool
I am cool. I seriously doubt that someone who invests large sums of money in MediaWiki sponsored companies likes being pointed to text that refers to them as an "idiot". I am not upset at all -- just making an observation.
I'm sure they don't.
This doesn't, however, mean that they *aren't* idiots. ESR is certainly a polarizing individual, and that as much as anything because he's blunt, and calls them like he sees them.
Whether how he sees them is reasonable is a-whole-nother argument, of course, but I personally am one of those people who answers lots of dumb questions from idiots -- idiots who *pay me* for the privilege, and that's why I don't lay ASQ on them. If they're asking me for *free*? You bet. If they think it's calling them an idiot, then maybe it is, and I might be so lucky as to have them ask someone else.
:-)
Cheers, -- jra
My first encounter with Eric Raymond was at a public conference several years ago. He got up and announced he was a "warlock" and other strange and bizzare nonsense. I note he was an author of that document. I guess that all speaks for itself.
:-)
Jeff
On Tue, Sep 19, 2006 at 12:27:38PM -0600, Jeff V. Merkey wrote:
Jay R. Ashworth wrote:
This doesn't, however, mean that they *aren't* idiots. ESR is certainly a polarizing individual, and that as much as anything because he's blunt, and calls them like he sees them.
Whether how he sees them is reasonable is a-whole-nother argument, of course, but I personally am one of those people who answers lots of dumb questions from idiots -- idiots who *pay me* for the privilege, and that's why I don't lay ASQ on them. If they're asking me for *free*? You bet. If they think it's calling them an idiot, then maybe it is, and I might be so lucky as to have them ask someone else.
My first encounter with Eric Raymond was at a public conference several years ago. He got up and announced he was a "warlock" and other strange and bizzare nonsense. I note he was an author of that document. I guess that all speaks for itself.
Sounds like it was probably Dragoncon. :-)
ESR isn't crazy, and neither is anything he wrote in that document.
And I speak as someone who's done tech support for about 15 years.
Cheers, -- jr 'though not as a psychologist :-)' a
Jeffrey V. Merkey wrote:
Here is a more complete question.
I have attempted to setup SVG to PNG rendering and it does not seem to work on 1.7.1. I checked the Defaults file in includes and I have verified rsvg is properly installed. I have also enabled the DebugLogFile option and attempted to run a trace the results indicate this section of code is not even activating as there are no messages being output to indicate that the RSVG section of code is even becoming active during rendering. The mine/type detection does appear to work in that SVG images are in fact detected.
Since you still do not provide any of your SVG-related configuration settings or the details of your investigations, I can't guess whether you've simply configured something wrong. All I can tell you is that if configured correctly, it is known to work.
-- brion vibber (brion @ pobox.com)
Brion Vibber wrote:
Jeffrey V. Merkey wrote:
Here is a more complete question.
I have attempted to setup SVG to PNG rendering and it does not seem to work on 1.7.1. I checked the Defaults file in includes and I have verified rsvg is properly installed. I have also enabled the DebugLogFile option and attempted to run a trace the results indicate this section of code is not even activating as there are no messages being output to indicate that the RSVG section of code is even becoming active during rendering. The mine/type detection does appear to work in that SVG images are in fact detected.
Since you still do not provide any of your SVG-related configuration settings or the details of your investigations, I can't guess whether you've simply configured something wrong. All I can tell you is that if configured correctly, it is known to work.
-- brion vibber (brion @ pobox.com)
Ask, and ye shall receive. Here is the LocalSettings.php (passwords removed) from MediaWiki 1.7.1. It fails with the default 1.7.1 right out of the tar.gz file. I also included the DefaultSettings.php
Jeff
Jeffrey V. Merkey wrote:
Brion Vibber wrote:
Jeffrey V. Merkey wrote:
Here is a more complete question.
I have attempted to setup SVG to PNG rendering and it does not seem to work on 1.7.1. I checked the Defaults file in includes and I have verified rsvg is properly installed. I have also enabled the DebugLogFile option and attempted to run a trace the results indicate this section of code is not even activating as there are no messages being output to indicate that the RSVG section of code is even becoming active during rendering. The mine/type detection does appear to work in that SVG images are in fact detected.
Since you still do not provide any of your SVG-related configuration settings or the details of your investigations, I can't guess whether you've simply configured something wrong. All I can tell you is that if configured correctly, it is known to work.
-- brion vibber (brion @ pobox.com)
Ask, and ye shall receive. Here is the LocalSettings.php (passwords removed) from MediaWiki 1.7.1. It fails with the default 1.7.1 right out of the tar.gz file. I also included the DefaultSettings.php
Jeff
Splicing in the text for LocalSettings.php. The mailer rejects the attachments. The only change I made to DefaultSettings.php is the addition of a "+" symbol to $wgLegalChars.
Jeff
# This file was automatically generated by the MediaWiki installer. # If you make manual changes, please keep track in case you need to # recreate them later. # # See includes/DefaultSettings.php for all configurable settings # and their default values, but don't forget to make changes in _this_ # file, not there.
# If you customize your file layout, set $IP to the directory that contains # the other MediaWiki files. It will be used as a base to locate files. if( defined( 'MW_INSTALL_PATH' ) ) { $IP = MW_INSTALL_PATH; } else { $IP = dirname( __FILE__ ); }
$path = array( $IP, "$IP/includes", "$IP/languages" ); set_include_path( implode( PATH_SEPARATOR, $path ) );
require_once( "includes/DefaultSettings.php" );
# If PHP's memory limit is very low, some operations may fail. # ini_set( 'memory_limit', '20M' );
if ( $wgCommandLineMode ) { if ( isset( $_SERVER ) && array_key_exists( 'REQUEST_METHOD', $_SERVER ) ) { die( "This script must be run from the command line\n" ); } } elseif ( empty( $wgNoOutputBuffer ) ) { ## Compress output if the browser supports it if( !ini_get( 'zlib.output_compression' ) ) @ob_start( 'ob_gzhandler' ); }
#$wgDebugLogFile = './debug.log';
$wgUseTidy = true; $wgTidyBin = 'usr/bin/tidy'; $wgTidyConf = $IP.'/extensions/tidy/tidy.conf';
$wgSitename = "WikiGadugi";
$wgScriptPath = ""; $wgScript = "$wgScriptPath/index.php"; $wgRedirectScript = "$wgScriptPath/redirect.php";
## For more information on customizing the URLs please see: ## http://meta.wikimedia.org/wiki/Eliminating_index.php_from_the_url ## If using PHP as a CGI module, the ?title= style usually must be used. $wgArticlePath = "/wiki/$1"; #$wgArticlePath = "$wgScript/$1"; # $wgArticlePath = "$wgScript?title=$1";
$wgStylePath = "$wgScriptPath/skins"; $wgStyleDirectory = "$IP/skins"; $wgLogo = "$wgStylePath/common/images/SequoyahStub.jpg";
$wgUploadPath = "$wgScriptPath/images"; $wgUploadDirectory = "$IP/images";
$wgEnableEmail = true; $wgEnableUserEmail = true;
$wgEmergencyContact = "webmaster@wikigadugi.org"; $wgPasswordSender = "webmaster@wikigadugi.org";
## For a detailed description of the following switches see ## http://meta.wikimedia.org/Enotif and http://meta.wikimedia.org/Eauthent ## There are many more options for fine tuning available see ## /includes/DefaultSettings.php ## UPO means: this is also a user preference option $wgEnotifUserTalk = true; # UPO $wgEnotifWatchlist = true; # UPO $wgEmailAuthentication = true;
$wgDBserver = "localhost"; $wgDBname = "wikidb"; $wgDBuser = "wikiuser"; $wgDBpassword = "password"; $wgDBprefix = ""; $wgDBtype = "mysql";
# Experimental charset support for MySQL 4.1/5.0. $wgDBmysql5 = false;
## Shared memory settings $wgMainCacheType = CACHE_NONE; $wgMemCachedServers = array();
## To enable image uploads, make sure the 'images' directory ## is writable, then set this to true: $wgEnableUploads = true; $wgUseImageResize = true; $wgUseImageMagick = true; $wgImageMagickConvertCommand = "/usr/bin/convert";
## If you want to use image uploads under safe mode, ## create the directories images/archive, images/thumb and ## images/temp, and make them all writable. Then uncomment ## this, if it's not already uncommented: # $wgHashedUploadDirectory = false;
## If you have the appropriate support software installed ## you can enable inline LaTeX equations: $wgUseTeX = true; $wgTexvc = './math/texvc'; $wgMathPath = "{$wgUploadPath}/math"; $wgMathDirectory = "{$wgUploadDirectory}/math"; $wgTmpDirectory = "{$wgUploadDirectory}/tmp";
$wgLocalInterwiki = $wgSitename;
$wgLanguageCode = "en";
$wgProxyKey = "1a76ed0ff0e05fadaa9c9db5344ee0a981d4348cb14f36a2209083e6a48da8e8";
## Default skin: you can change the default skin. Use the internal symbolic ## names, ie 'standard', 'nostalgia', 'cologneblue', 'monobook': $wgDefaultSkin = 'monobook';
## For attaching licensing metadata to pages, and displaying an ## appropriate copyright notice / icon. GNU Free Documentation ## License and Creative Commons licenses are supported so far. $wgEnableCreativeCommonsRdf = false; $wgRightsPage = ""; # Set to the title of a wiki page that describes your license/copyright $wgRightsUrl = "http://www.wikigadugi.org/index.php/License"; $wgRightsText = "Wikigadugi Public License"; #$wgRightsIcon = "${wgStylePath}/common/images/gnu-fdl.png"; # $wgRightsCode = "gfdl"; # Not yet used
$wgDiff3 = "/usr/bin/diff3";
# When you make changes to this configuration file, this will make # sure that cached pages are cleared. $configdate = gmdate( 'YmdHis', @filemtime( __FILE__ ) ); $wgCacheEpoch = max( $wgCacheEpoch, $configdate );
$wgUseFileCache = true; $wgFileCacheDirectory = "/wikidump/chrcache"; $wgShowIPinHeader = false; $wgUseGzip = false; $wgAntiLockFlags = ALF_NO_LINK_LOCK | ALF_NO_BLOCK_LOCK;
require_once( "$IP/extensions/Chr2Syl.php" ); require_once( "$IP/extensions/Cite.php" ); require_once( "$IP/extensions/ParserFunctions/ParserFunctions.php" );
#$wgDebugLogFile = 'debug.log';
Jeffrey V. Merkey wrote:
Jeffrey V. Merkey wrote:
Brion Vibber wrote:
Jeffrey V. Merkey wrote:
Here is a more complete question.
I have attempted to setup SVG to PNG rendering and it does not seem to work on 1.7.1. I checked the Defaults file in includes and I have verified rsvg is properly installed. I have also enabled the DebugLogFile option and attempted to run a trace the results indicate this section of code is not even activating as there are no messages being output to indicate that the RSVG section of code is even becoming active during rendering. The mine/type detection does appear to work in that SVG images are in fact detected.
Since you still do not provide any of your SVG-related configuration settings or the details of your investigations, I can't guess whether you've simply configured something wrong. All I can tell you is that if configured correctly, it is known to work.
-- brion vibber (brion @ pobox.com)
Ask, and ye shall receive. Here is the LocalSettings.php (passwords removed) from MediaWiki 1.7.1. It fails with the default 1.7.1 right out of the tar.gz file. I also included the DefaultSettings.php
Jeff
Here are the default settings for DefaultSettings.php for the SVG renderer.
Jeff
# Scalable Vector Graphics (SVG) may be uploaded as images. # Since SVG support is not yet standard in browsers, it is # necessary to rasterize SVGs to PNG as a fallback format. # # An external program is required to perform this conversion: $wgSVGConverters = array( 'ImageMagick' => '$path/convert -background white -geometry $width $input $output', 'sodipodi' => '$path/sodipodi -z -w $width -f $input -e $output', 'inkscape' => '$path/inkscape -z -w $width -f $input -e $output', 'batik' => 'java -Djava.awt.headless=true -jar $path/batik-rasterizer.jar -w $width -d $output $input', 'rsvg' => '$path/rsvg -w$width -h$height $input $output', ); /** Pick one of the above */ $wgSVGConverter = 'rsvg'; /** If not in the executable PATH, specify */ $wgSVGConverterPath = ''; /** Don't scale a SVG larger than this */ $wgSVGMaxSize = 1024;
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
- -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Moin,
On Tuesday 19 September 2006 09:31, Jeffrey V. Merkey wrote:
Jeffrey V. Merkey wrote:
Jeffrey V. Merkey wrote:
Brion Vibber wrote:
Stupid questions you might be able to answer:
* Have you tried running the commands manually? * If they succeed, check that the automated process isnt by accident running a different version (having f.i. a different path, like /usr/bin vs /usr/local/bin first) * Check that the automated process can actually find the command * Check the permissions and directories very carefully. Check them again. :D
Sorry for being so handwaiving, but without a login on that machine it's nothing more I can do from my armchair :)
Best wishes,
Tels
- - -- Signed on Tue Sep 19 10:27:30 2006 with key 0x93B84C15. Visit my photo gallery at http://bloodgate.com/photos/ PGP key on http://bloodgate.com/tels.asc or per email.
This email violates EU patent EP0394160:
[ ########## 66% #### ]
Tels wrote:
Stupid questions you might be able to answer:
- Have you tried running the commands manually?
- If they succeed, check that the automated process isnt by accident running
a different version (having f.i. a different path, like /usr/bin vs /usr/local/bin first)
I've run the command manually and it works. I am getting the debug logs for Brion he asked for now and moving the wgLegalChars changes back to LocalSettings.php and running the traces.
- Check that the automated process can actually find the command
- Check the permissions and directories very carefully. Check them again. :D
This is a VERY good idea.
Jeff
Sorry for being so handwaiving, but without a login on that machine it's nothing more I can do from my armchair :)
Best wishes,
Tels
Jeffrey V. Merkey wrote:
Splicing in the text for LocalSettings.php. The mailer rejects the attachments. The only change I made to DefaultSettings.php is the addition of a "+" symbol to $wgLegalChars.
Never ever change DefaultSettings.php
Don't do it. There's comments all over the file telling you not to do it. Please read the comments. Please read the documentation. Please follow the directions.
Change settings ONLY in LocalSettings.php.
Do not change settings in DefaultSettings.php
Your LocalSettings.php contains no SVG-related configuration; thus by default ImageMagick would be set as the SVG renderer, which will work poorly if at all.
You haven't included any of the debugging information you claim to have done.
You're also still posting to the development list instead of the support list (mediawiki-l). Slightly better than foundation-l, but it would be nice if you could pick the appropriate forum occasionally as well as including enough information for people to have a clue how to help you.
-- brion vibber (brion @ pobox.com)
wikitech-l@lists.wikimedia.org