My print preview from MS Access shows everything perfectly fine. Here's the actual PDF file snapshot which shows some letters are cut in half. It happens inconsistently with this report and not always for the same data.
In this report only 5 out of 40 questions had their first letter cut in half.
Please advise.
I've tried adjusting where the data field must start, i.e. I've moved the start of the question a bit more right, but no difference.
Here's the design view I've highlighted in yellow where the question starts. I've moved it more right, makes no difference.
Here's where the user captures questions]
Your problem text lines have a stray Tab character (ASCII 9) at or near the beginning of the line, which is being interpreted as a lateral positioning move for the string. Your correct lines do not have a stray Tab. If you use Acrobat's text editor to delete the Tab, the rest of the line jumps properly into view.
Below, I've extracted the text of each line in your sample, and replaced the unexpected Tab character with an "X." If you use Acrobat text editing to navigate carefully to the spot in the line where the Tab is located (you won't see it directly, but it's there), Shift-cursor sideways to highlight the Tab alone, and delete it, you'll see the text revert to its normal appearance.
Note that the Tab is usually not the first character in the line, in lines where it appears:
SXources of polyunsaturated fats include
LXack of calcium is one of the major causes of osteoporosis
XDisaccharides are the simplest form of carbohydrate
Excessive long term protein intake may lead to kidney problems
Water soluble vitamins taken in excess have toxic effects in the body
LXack of calcium is one of the major causes of osteoporosis
SXources of polyunsaturated fats include
VXitamin B12 is involved in
I'm going to hazard a guess here that the problem was introduced in the text before it was uploaded to your final document, so that the unwanted Tabs somehow snuck in as body text. I hope that helps.
That is one weird effect. It is a bit suspicious that it only occurs towards the end of the document, but I have no idea what causes it.
Two workarounds worked for me:
1) Use
=" " & [Question]
as control source of the text box, and rename it to txtQuestion to avoid a circular reference. That's two spaces, one wasn't enough.
Move it a bit to the left, to make up for the increased indentation.
2) Don't use the Access-integrated PDF creator, use a PDF printer instead.
I used the Windows 10 integrated "Microsoft Print to PDF", but there are many free ones, e.g. https://en.pdf24.org/ (just google "pdf printer driver").
This created a larger .pdf file for me, but it doesn't show the error.
Edit: Interestingly, while Adobe Acrobat Reader shows the error, Foxit Reader or the Firefox integrated PDF viewer doesn't. Here is a single page example if anyone else wants to check.
Related
When you copy then paste the string “word”, macOS sometimes inserts “word” (unchanged), “ word”, “word ”, or “ word ”, depending on what you’re pasting it next to, whether it thinks you copied it as a word or as a range, and whether you’re pasting into a writing input (like a note in the Notes app) or a string input (like Safari’s URL bar). Click-and-dragging to select results in a range copy, double clicking results in a word copy.
On macOS, Safari and Chrome perform automatic space insertion in all inputs, while Firefox performs it in none. Firefox also does not follow the native behavior for double clicking a word, right clicking a word, or copying a word.
You can play with the behavior with the following demo. Try double clicking a word then pasting it multiple times, then try selecting a word by dragging then pasting it multiple times.
<div>one two three</div>
<input>
Automatic space insertion is probably fine and intuitive for macOS users, but is sometimes inappropriate for the same reason it’s inappropriate in Safari’s URL bar: some contexts are not in English or any other written language. In these contexts, automatic space insertion leads to surprising results. For example, I ran into this issue when entering input in a micro-language of the form [field.{id}], then pasting an ID, which was copied as a word, then getting [field. {id}] and the error that it caused.
Ideally, I want to instruct the browser not treat an input’s value as writing. Minimally, I want to turn off automatic space insertion an inputs. How can I do this?
Things I’ve tried that didn’t work:
Setting lang="" or lang="none" on both the input and the copied text
Setting lang="zh" on both the input and the copied text (Chinese languages do not use spaces between words)
Setting spellcheck="false" on the input
Setting autocorrect="off" on the input (non-standard, Safari only)
One solution is to cancel then mimic the paste event in JS.
<input id="example">
document.querySelector('#example').addEventListener('paste', e => {
e.preventDefault();
const pastedText = e.clipboardData.getData('text/plain');
document.execCommand('insertText', false, pastedText);
});
This solution has the following limitations:
Requires JS
Does not also disable other writing-specific niceties, if any exist
Uses the deprecated document.execCommand API
I'm currently working on a web app that part of which is to display a description per location taken from an API. I have it so it displays the whole description no matter how long it is. when I run the app in developer mode and even when I deploy it to firebase it works just fine, it shows me the description no matter how long it is. tested it on my phone (android) and works just as well, but a co-worker tried it out on his iPhone and after a few lines it shows applies text-overflow: ellipsis;, thus not showing me the rest of the string and in turn replacing it with an ellipsis. I wasn't able to find much info on this problem so I wanted to ask if there are any relevant info sites out there for this sort of issue, and if anyone knows how do I disable this CSS property on IOS devices.
for additional context, the app is developed on Ionic-Angular
Sorry this is a few months late but the only solution I found was going into settings>general>keyboard>text replacement and then doing the following:
In a text, or notes, or anywhere you can type (even copy these if you want: ... ) type two periods, put a space, then type another.
Now go back and delete that space between the two and all 3 will still be periods, not merged into an ellipsis. Select and copy those 3 (or the 3 I gave above) and now create new text shortcuts. I made 4 just to be safe and here they are:
1] the phrase is the pasted 3 periods, and the shortcut is an actual ellipsis (you can also type it by long pressing on the period on your iPhone)
2] the phrase is the pasted 3 periods and then the shortcut is the same pasted 3 periods (sometimes this makes the phone recognize something differently)
3] the phrase is the pasted 3 periods and the shortcut is two periods (so: .. ) and this way if I type 2 periods and hit space, it’ll turn it into 3 periods, not an ellipsis
4] the phrase is the pasted 3 periods and the shortcut is four periods (so: .... ) and this way if I type 4 periods and hit space it’ll turn it into 3 periods, not an ellipsis with a dot after it.
It’s not a perfect work around but if you almost always use 3 dots and don’t need 2 or 4 that often then this stopped the ellipsis from showing up for me (luckily!)
Edit: after playing around with it I found that the iPhone’s input of an ellipsis depends on where you are typing. For instance if I’m in a green text message chat (someone on android) it does not input it... so then when I type 3 periods, it replaces it to 4 since it sees the first by itself and the next 2 as being a shortcut to 3... grrrr...
So with that said, my solution above works for iMessages when texting people who have iPhones. This is primarily where I use 3 periods so I’ll probably keep mine this way. However, you can delete 3 of the 4 shortcuts I recommended and simply keep the 4 period shortcut one. Then every time you need 3 periods instead of an ellipsis, simply type 4 periods and move on..
I'd like my data to at least extend horizontally to the edge of the environment pane, but it gets truncated even if there is plenty of room left in the pane. Columns of class "chr" appear to be restricted to showing only the first 4 entries (yellow arrows in the first picture), and columns of class "num" and "int" tend to show either 5 or 10 values (green arrow in the first picture).
Right-clicking on one of the rows and selecting "Inspect element" brings up RStudio DevTools; using that, I can at least enable a scroll bar by changing "overflow-x" from 'hidden' to 'scroll'. However, the scroll bar only scrolls to the original 4, 5, or 10 values that were shown, and then you still see the ellipsis. Changing "text-overflow" from 'ellipsis' to any of the other options seems to have no effect, nor does changing any of the other properties (padding-left/right, border, white-space).
I'd just like to see more data in that pane or enable a scroll bar at the bottom of the pane instead of for each individual row, but I can't find any settings to change to enable this. The theme I'm using is Tomorrow Night Bright if that matters.
You definitely can't do it using RStudio DevTools. RStudio implements their display using Chrome, so RStudio DevTools is just Chrome DevTools: the truncation of values has already happened before Chrome sees it.
There's probably a variable somewhere in the RStudio sources that controls how the truncation takes place, but I don't know where. You can look through the sources here if you want: https://github.com/rstudio/rstudio . I kind of doubt that it will be something you can control from R, but you never know.
So I can't offer a general solution, but I can offer a small hack. Normally I use this when I want to look at an expression: many debuggers let you watch expressions, but RStudio just shows you existing variables. However, if you want to see x+y in the environment pane, you can just calculate it in the console:
`x+y` <- x+y
and it will be displayed. (You've also created a new variable, and possibly stomped on an existing one.) This doesn't change like a live expression, so it's not that great, but it's better than nothing.
For your purpose, the thing to calculate would be something to display the missing bits of your display. If you want to see more manufacturer values, then do something like
mfr <- paste(mpg$manufacturer, collapse = " ")
This creates one long string, and will show as much of it as will fit.
I added a package to the Atom code editor that closes HTML tags for me. This feature is included in many code-editors, so it isn't Atom-specific.
For example, I type
<h1>
and it conveniently changes the line to
<h1></h1>
and places my cursor between the two tags.
This is where the dilemma occurs: My cursor is placed between the words and the closing tag, and I wish to go to the next line. Moving my hand to the mouse and clicking to the end of the line and then pressing enter is out of the question, especially with long documents where this phenomenon occurs hundreds, if not thousands of times.
Is there any way, perhaps a keyboard shortcut that skips to the end of the line, to solve this?
In Atom, CmdEnter (Mac) or CtrlEnter (Windows/Linux) will make a new line and go there, skipping past whatever is presently on the line.
You can just push the end button. Mine is located above my backspace key, but it might be with the number pad if you have a separate number pad.
If you add the same element over and over again, you could copy & paste it. And for the sake of an empty element you could copy & paste something like <br /> (you can even leave out the space, I just like to add them to make self-closing tags easier to identify).
PS: empty headlines? shame on you!
When I do a simple search/replace, without any regex, ST2 adds a newline to each replacement. What am I doing wrong?
Below, I want to change spaces to commas. It does so, but also throws in a newline.
If the text you would like to replace is somewhat limited in size, here is a workaround. It doesn't even incorporate the builtin replace feature, and it can be somewhat slow for large text files.
Hit CMD + F (or CTRL + F) to bring up the Find dialog on the bottom of the window. Enter whatever string you'd like into the text field. Click the "Find All" button, and you'll get multiple write positions into the file. You can write in two places at once! If you've done it correctly, you'll see not just one blinking vertical line (which usually indicates the position in the file that the read/write pointer is at), but multiple. You can then type as usual into the file, and it should add text in multiple places.