SVG workarounds - Revision history

Fizzer at 02:35, 18 April 2026

2026-04-18T02:35:27Z

← Older revision		Revision as of 02:35, 18 April 2026
Line 1:		Line 1:
	This page lists the SVG workarounds you may need to use to get your [[map]] working in ~~Warzone~~.		This page lists the SVG workarounds you may need to use to get your [[map]] working in War.app.

	==ViewBox Fix==		==ViewBox Fix==

	~~Warzone~~ currently has a hard time understanding SVG files that have setting for an SVG's width and height from its view box. This can cause maps to appear incorrectly sized when uploaded to ~~Warzone~~, or to not appear at all if they are so much larger than the screen that all of the territories are off-screen.		War.app currently has a hard time understanding SVG files that have setting for an SVG's width and height from its view box. This can cause maps to appear incorrectly sized when uploaded to War.app, or to not appear at all if they are so much larger than the screen that all of the territories are off-screen.

	To check if this is causing an issue or to fix it, follow these steps:		To check if this is causing an issue or to fix it, follow these steps:
Line 15:		Line 15:
	## height = 400		## height = 400
	## viewBox = 0 0 900 400		## viewBox = 0 0 900 400
	# If the viewBox isn't rooted at 0,0 or if its width and height don't match the others, simply change the viewBox by selecting it, typing in the correct numbers, and clicking set. After doing this, your map will likely shift all of its territories to different locations. Now you should select all of the territories and move/resize them to fit them back within the box. After doing this, the map should work correctly in ~~Warzone~~.		# If the viewBox isn't rooted at 0,0 or if its width and height don't match the others, simply change the viewBox by selecting it, typing in the correct numbers, and clicking set. After doing this, your map will likely shift all of its territories to different locations. Now you should select all of the territories and move/resize them to fit them back within the box. After doing this, the map should work correctly in War.app.

	==Text==		==Text==

	~~Warzone~~ doesn't support the plain text you can type in in most SVG editors. They won't show. So you'll need to transfer them to paths. That can be done this way:		War.app doesn't support the plain text you can type in in most SVG editors. They won't show. So you'll need to transfer them to paths. That can be done this way:
	# Open the SVG file in Inkscape.		# Open the SVG file in Inkscape.
	# Select the text you want to transfer.		# Select the text you want to transfer.
	# Open the menu "Paths", and from there the option at the top: "Object to Path" Click it.		# Open the menu "Paths", and from there the option at the top: "Object to Path" Click it.
	Now re-upload the map to ~~Warzone~~ and you're done!		Now re-upload the map to War.app and you're done!

	[[Category:Map Making\|Workarounds]]		[[Category:Map Making\|Workarounds]]

Fizzer at 03:39, 13 November 2017

2017-11-13T03:39:39Z

← Older revision		Revision as of 03:39, 13 November 2017
Line 1:		Line 1:
	This page lists the SVG workarounds you may need to use to get your [[map]] working in ~~WarLight~~.		This page lists the SVG workarounds you may need to use to get your [[map]] working in Warzone.

	==ViewBox Fix==		==ViewBox Fix==

	~~WarLight~~ currently has a hard time understanding SVG files that have setting for an SVG's width and height from its view box. This can cause maps to appear incorrectly sized when uploaded to ~~WarLight~~, or to not appear at all if they are so much larger than the screen that all of the territories are off-screen.		Warzone currently has a hard time understanding SVG files that have setting for an SVG's width and height from its view box. This can cause maps to appear incorrectly sized when uploaded to Warzone, or to not appear at all if they are so much larger than the screen that all of the territories are off-screen.

	To check if this is causing an issue or to fix it, follow these steps:		To check if this is causing an issue or to fix it, follow these steps:
Line 15:		Line 15:
	## height = 400		## height = 400
	## viewBox = 0 0 900 400		## viewBox = 0 0 900 400
	# If the viewBox isn't rooted at 0,0 or if its width and height don't match the others, simply change the viewBox by selecting it, typing in the correct numbers, and clicking set. After doing this, your map will likely shift all of its territories to different locations. Now you should select all of the territories and move/resize them to fit them back within the box. After doing this, the map should work correctly in ~~WarLight~~.		# If the viewBox isn't rooted at 0,0 or if its width and height don't match the others, simply change the viewBox by selecting it, typing in the correct numbers, and clicking set. After doing this, your map will likely shift all of its territories to different locations. Now you should select all of the territories and move/resize them to fit them back within the box. After doing this, the map should work correctly in Warzone.

	==Text==		==Text==

	~~Warlight~~ doesn't support the plain text you can type in in most SVG editors. They won't show. So you'll need to transfer them to paths. That can be done this way:		Warzone doesn't support the plain text you can type in in most SVG editors. They won't show. So you'll need to transfer them to paths. That can be done this way:
	# Open the SVG file in Inkscape.		# Open the SVG file in Inkscape.
	# Select the text you want to transfer.		# Select the text you want to transfer.
	# Open the menu "Paths", and from there the option at the top: "Object to Path" Click it.		# Open the menu "Paths", and from there the option at the top: "Object to Path" Click it.
	Now re-upload the map to ~~Warlight~~ and you're done!		Now re-upload the map to Warzone and you're done!

	[[Category:Map Making\|Workarounds]]		[[Category:Map Making\|Workarounds]]

Moros: Added section about converting texts. I know this has already been mentioned on other pages on this wiki, but I plan to add a lot more of these tutorials to this page.

2012-09-20T21:20:14Z

Added section about converting texts. I know this has already been mentioned on other pages on this wiki, but I plan to add a lot more of these tutorials to this page.

← Older revision		Revision as of 21:20, 20 September 2012
Line 16:		Line 16:
	## viewBox = 0 0 900 400		## viewBox = 0 0 900 400
	# If the viewBox isn't rooted at 0,0 or if its width and height don't match the others, simply change the viewBox by selecting it, typing in the correct numbers, and clicking set. After doing this, your map will likely shift all of its territories to different locations. Now you should select all of the territories and move/resize them to fit them back within the box. After doing this, the map should work correctly in WarLight.		# If the viewBox isn't rooted at 0,0 or if its width and height don't match the others, simply change the viewBox by selecting it, typing in the correct numbers, and clicking set. After doing this, your map will likely shift all of its territories to different locations. Now you should select all of the territories and move/resize them to fit them back within the box. After doing this, the map should work correctly in WarLight.

			==Text==

			Warlight doesn't support the plain text you can type in in most SVG editors. They won't show. So you'll need to transfer them to paths. That can be done this way:
			# Open the SVG file in Inkscape.
			# Select the text you want to transfer.
			# Open the menu "Paths", and from there the option at the top: "Object to Path" Click it.
			Now re-upload the map to Warlight and you're done!

	[[Category:Map Making\|Workarounds]]		[[Category:Map Making\|Workarounds]]

Grzechooo at 11:01, 6 November 2011

2011-11-06T11:01:50Z

← Older revision		Revision as of 11:01, 6 November 2011
Line 1:		Line 1:
			This page lists the SVG workarounds you may need to use to get your [[map]] working in WarLight.

	==ViewBox Fix==		==ViewBox Fix==

Fizzer at 14:38, 30 October 2011

2011-10-30T14:38:57Z

@@ Line 14: / Line 14: @@
 ## viewBox = 0 0 900 400
 # If the viewBox isn't rooted at 0,0 or if its width and height don't match the others, simply change the viewBox by selecting it, typing in the correct numbers, and clicking set.  After doing this, your map will likely shift all of its territories to different locations.  Now you should  select all of the territories and move/resize them to fit them back within the box.  After doing this, the map should work correctly in WarLight.
 [[Category:Map Making|Workarounds]]

Grzechooo at 12:52, 23 October 2011

2011-10-23T12:52:12Z

← Older revision		Revision as of 12:52, 23 October 2011
Line 26:		Line 26:
	This bug will be fixed in the next WarLight release, 1.08.		This bug will be fixed in the next WarLight release, 1.08.

	[[Category:Map Making]]		[[Category:Map Making\|Workarounds]]

Grzechooo at 12:46, 23 October 2011

2011-10-23T12:46:02Z

← Older revision		Revision as of 12:46, 23 October 2011
Line 25:		Line 25:

	This bug will be fixed in the next WarLight release, 1.08.		This bug will be fixed in the next WarLight release, 1.08.

			[[Category:Map Making]]

Fizzer at 12:33, 23 October 2011

2011-10-23T12:33:54Z

← Older revision		Revision as of 12:33, 23 October 2011
Line 1:		Line 1:
	==Fix ~~viewports~~==		==ViewBox Fix==

	WarLight currently has a hard time understanding SVG files that have setting for an SVG's width and height from its view box. This can cause maps to appear incorrectly sized when uploaded to WarLight, or to not appear at all if they are so much larger than the screen that all of the territories are off-screen.		WarLight currently has a hard time understanding SVG files that have setting for an SVG's width and height from its view box. This can cause maps to appear incorrectly sized when uploaded to WarLight, or to not appear at all if they are so much larger than the screen that all of the territories are off-screen.
Line 16:		Line 16:


	==Fix ~~transforms~~==		==Transform Fix==

	Unfortunately there are a few kinds of transformations that SVG supports that WarLight does not. These can cause objects to appear at a different location within WarLight than they should.		Unfortunately there are a few kinds of transformations that SVG supports that WarLight does not. These can cause objects to appear at a different location within WarLight than they should.

Fizzer: Created page with "==Fix viewports== WarLight currently has a hard time understanding SVG files that have setting for an SVG's width and height from its view box. This can cause maps to appear in..."

2011-10-23T12:32:31Z

Created page with "==Fix viewports== WarLight currently has a hard time understanding SVG files that have setting for an SVG's width and height from its view box. This can cause maps to appear in..."

New page

==Fix viewports==

WarLight currently has a hard time understanding SVG files that have setting for an SVG's width and height from its view box. This can cause maps to appear incorrectly sized when uploaded to WarLight, or to not appear at all if they are so much larger than the screen that all of the territories are off-screen.

To check if this is causing an issue or to fix it, follow these steps:

# Open the SVG file in Inkscape
# Open the XML Editor (4th button from the top right)
# Click on the top-most node (it should start with svg:svg)
# Inspect the "width", "height" and "viewBox" attributes. ViewBox should have 4 numbers, which represent (in order): x, y, width, height
# The viewBox should be set to 0 and 0 for x and y, and to the same values as width and height. For example, these settings are correct:
## width = 900
## height = 400
## viewBox = 0 0 900 400
# If the viewBox isn't rooted at 0,0 or if its width and height don't match the others, simply change the viewBox by selecting it, typing in the correct numbers, and clicking set. After doing this, your map will likely shift all of its territories to different locations. Now you should select all of the territories and move/resize them to fit them back within the box. After doing this, the map should work correctly in WarLight.

==Fix transforms==

Unfortunately there are a few kinds of transformations that SVG supports that WarLight does not. These can cause objects to appear at a different location within WarLight than they should.

Fortunately, these are easy to fix. In Inkscape, open the XML Editor (on the top toolbar, it's the 4th button from the right).

Select the offending object. The XML Editor will show you the attributes on it. If you see an attribute named ''transform'' with a value that starts with ''matrix'', delete it. This will cause the object to move in Inkscape - now just drag it back to its correct position and your map should work normally.

This bug will be fixed in the next WarLight release, 1.08.