Does anyone know why the right hand side of the text is cut off? The first image is in the editor, the 2nd is through a browser. The .web file is attached.
Printable View
Does anyone know why the right hand side of the text is cut off? The first image is in the editor, the 2nd is through a browser. The .web file is attached.
Looks to me as if you have squished the font (ARIAL) horizontally in WD.
The browser can't squish fonts.
(Also, Hobo Std isn't a web safe font)
Looks like you have changed the aspect ratio on the text which is causing the problem to occur.
The reasons we dropped the side handles on objects such as groups, photos, text was to make it difficult to squash or stretch text, because brwosers will make a mess of it (as slegder said browsers can't do this). So the idea was that it should not be easy to mess up text like this (admittedly not looked at the .web file though).
The text attributes say that it's Arial 11pt. If, however, you duplicate the first line of text directly above the already existing paragraph (specifying that it be Arial 11pt), you'll see that share the same height, but the new line is quite a bit more extended.
Might it be helpful in the text properties to indicate some compression/expansion factor? The current dialog doesn't offer that.
I am having a bit of trouble with test boxes. I move the box and the test does squash instead of staying put. May be a tutorial vid would explain this better.
Use the Text tool to resize the text area rather than the select tool.
It will be bounded by a red dashed border.
I do and the same thing seems to happen.
Edit: Doh, of course now it proves me wrong. May be I resized it using different tools without realising which tool i was using and that's where the problem was. Thanks
It might be an idea for the software to switch behaviours when dealing with text so that text is treated appropriately regardless of which method of selection is made.
Not a bad idea. But what it you wanted to distort the font type (squash vertically or horizontally) for a bitmap header etc?
Just making sure you select the text tool to resize the text box works perfectly. It's just getting used to it. :)
'Convert to editable shapes' comes to mind, though I have yet to install WD!Quote:
Originally Posted by sledger
That's true, but a TON of people are going to mess up their layouts and ask for help because of this behaviour.Quote:
Originally Posted by nickydude
I'm missing something here - like how you squashed the text. Neither the Selector Too nor the Text Tool will squash text. So how exactly did you do this?
Paul there is no 'convert to editable shapes' in Web Designer.
Using the select tool resizes the text as well as the text box whereas using just the text tool to resize resizes the text box only.
OK now I'm confused, I actually never noticed this before either, so yes Paul - the text area acts just as the way you asked for :o
Nickydude:
Was this something you started in Xara Xtreme? Because you can squash the text in Xtreme, copy it to the clipboard and paste into WD as squashed but editable text.
Maybe you are editing a .xar which you started in Xtreme?
.web file attached to demonstrate
I just installed WD and was unable to squish text out of proportion and it all behaved nicely. Good job Charles. very impressive (who stole all my tools though?!).
I've never used Xtreme (which is why I keep asking questions about the tools you guys are probably used to :)) Here's a grab of what I meant. Resizing the text box using the select tool also resizes the text, which I didn't want. But now all is well. :)
Nickydude.
Yes that's correct for point resizing, but I cannot cannot squash the text (deform) like you have in your original file at the start of the thread. How did you deform Arial like this in Web Designer?
I have been trying but cannot squash it.... :confused:
Ahh, bear in mind that I originally asked about the cutting of text, not squashing. This reason is that I've actually squashed the entire screen shot down so it wasn't a large image to show on the forum. So the 'squashing' is just a resized screen shot.
http://img52.exs.cx/img52/271/l9iblush.gif
Nicky the screen shot is not what we have been talking about. It is the text in your .web file. It exhibits traits of being squashed which is what would cause it to be cut off. Squashed text will not properly wrap within the text area when exported so it becomes cutoff.
Steve (sledger) and I have been trying to duplicate the problem but cannot with out resorting to squashing the text deliberately within Xtreme then placing it within Web Designer.
Theroretically it is impossible to squash the text within Web Designer...but somehow it has been done or a reasonable facsimile. :)
Right, I see what you mean. I've just tried to duplicate it and it's a combination of resizing with both the text tool and the select tool. First I resized it small using the select tool, then used the text tool to enlage the text box, then shrunk it smaller using the select tool... It's a combination of using one then the other to shrink / enlarge.
It should not do that :D
I think you have found a bug in the soup so to speak.
When John (Covoxer) is online again I'm sure he will make note of it. He works on a lot of the Web Designer code I believe.
The selector tool can not (should not) change proportions of the text object.
However, it is possible to change them in WD the other way. If you turn off proportions lock in the property bar of the selector tool (the small lock button to the right of the percentage scales), and then manually change the width in the width box on the property bar, it will resize only in one dimension.
Right John :)
OK - back to Post #1 and #2.
nickydude, you squished the text, browsers don't render squished (resized in the horizontal dimension only) text. :rolleyes:
Perhaps WD should always lock the proportions when dealing with text - regardless of the users general setting.
Maybe,
For just the purpose of using squashed text,
Have (auto)convert to shapes as you implemented for the rotating text issue
Hans
Turning off the proportional lock, then changing the height:width of text is a valid operation (depending on graphic intent). While not accurately representable as text in a browser, a graphic conversion (to jpg or png) of the text can ensure proper display. Removing the option to disproportionately squish/squash text in xWD should not be seriously considered.
Well, if the user is expecting text to be rendered as html text, then a proportional lock would stop the user being disappointed with the end result when the html is generated. As you suggest, text that has been made into a graphic can be squished as the end user sees fit.Quote:
Originally Posted by cursor
The challenge for Xara is making these two situations clear to the user.
I don't think dismissing locking the proportions of text that is being generated as html needs to be dismissed out of hand.
Yes, it's a screw-up on our part that it's so easy to mess up text by un-ticking that aspect-lock control. We would have been better to remove the feature (the aspect lock / unlock button) and so we are indeed very seriously considering removing the feature in future releases.
And while you could argue that producing squashed text for use in graphics is valid, and it will work and be WYSIWYG, you can equally argue that all squashed text is ugly (it is) it's not something a professional designer would do, and so this is in fact not a useful operation.
We always have to balance whether providing a given feature makes the product more complex and more likely to give poor / ugly results. In this case it gives bad results, and also gives us a real support headache (as you can tell from the length of this thread). When customers cannot work out why things have gone wrong, that is a sign of poor software design on our (my) part.
Charles,
Why not make the same procedure to squashed text as you did to the rotated text.
Another wysiwyg program I use has the same feature to text that needs shadow or reflection.
It converts the text used to an gif when these effects are applied.
Hans
Yes it would be an option to automatically convert squashed text to graphics, and probably quite easy to do that in fact. But while that will solve the WYSIWYG problem, I suspect that most users who accidentally squash text probably don't realise, and would rather not have all their text as one large graphic. We are really better off trying to make it really difficult to squash text.