Among Us Impo
Shinyoung Gedris
I'm aware of the typical import statement conventions specified in the PEP 8 style guide and for blank lines as well. However, I became curious if there is a convention or unwritten rule for blank lines among import statements.
For example, I usually like to put a blank line in between the three categories that are specified in PEP 8 (i.e. standard library imports, related third party imports, local application/library specific imports) but I've also noticed that many people tend not to do so. My PyLint application even throws a warning whenever I put a blank line.
Importing MS Word files into InDesign has always been twiddly. Both for myself and for others in my organization, I need to import files and update them regularly. One big challenge over the years has been dealing with italic and superscripted text. I have figured out how to have similarly-named styles in Word (yes, I know that my MS Word paragraph styles should be "based on: none") and in InDesign to allow automatic mapping to occur without having to have a customized import mapping. And after exporting a .rtf file from InDesign, I have even figured out how to apply MS Word paragraph styles to outline-numbered paragraph styles so the exported RTF has the same numbering as in InDesign.
But for my teaching handouts (I'm a med school professor), I have to use Word to create the text file, and then Place it, as I need to use EndNote to create and format bibliographic references. Here is the first section of one of my handouts in MS Word:
I thought about the recommendations to not use Word's builtin italic and superscript and the like, and create MS Word Character Styles for italic and superscript and the like, but it looks like MS Word has already created some character styles, which may be the source of the problem:
I can't address why this is happening, but I have the same issue on a regular basis. In my case, the paragraphs have the correct style assigned (Body), but they have overrides. My approach is three-fold:
Ah, I thought you were mapping your Word character styles to InDesign character styles. For this to work, everything has to have a style assigned. If you are losing the inline formatting, take 5 minutes to create character styles for the inline formatting, and then build the required find/change queries to find the inline formatting and assign the style (and save them so that they are available for future docs):
I also tried doing a search-and-change for superscript, but I can't find a superscript to search for. Perhaps that's because there is some really weird stuff going on in those superscripted numbers from EndNote. See the screenshot below with MS Word field codes shown:
But, the standard medical/biosciences format is for references to be superscripted numbers in the order of appearance. The style I chose in EndNote is the New England Journal of Medicine format. That's the most common format; other major medical formats exist, but as fars as I can tell, they all have changes in the format of the bibiliography at the end still have the superscripted numbers which seem universal.
Thank you, Barb, but I dread the complications that a GREP might cause with other numbers in parentheses. I finally decided to use the Vancouver style that has citation references in parentheses without superscripts. As you can see, it certainly cut down on the amount of manual clean-up required.
However, it's now more clear that whatever EndNote is doing in those citation references (hidden from our view in Word and InDesign) is still messing up the italics, though not as badly. I'm starting to think I should address this with the EndNote folks.
A properly defined (and tested) GREP find/change query is reliable, just like any properly defined (and tested) Text, Glyph or Object find/change query. But that said, I'm glad you settled on a formatting approach that will work for you.
By all means take this up with EndNote, but do note that as per my first response, I have the same issue with footnotes on a quarterly layout job and that's why I developed the solution I presented in the same post. It has worked for me for years.
OK, so I did that. As a note, I did one better than saving a backup copy: Save the MS Word .docx file that I usually Place in InDesign, named Diarrhea-Text.docx, to Diarrhea-Stripped.docx, so that I'm less likely to destroy my many hours of work, and then use Diarrhea-Stripped.dox to Select All and then remove all the field codes.
Above, I put a series of numbers in parenthesis and created a character style called Superscript. The position is set to superscript and I added the magenta to help the numbers stand out in the demo, but of course you would leave the color black.) Then:
Barb, thank you very much. I used the Vancouver EndNote style, which uses non-superscripted numbers in parentheses, and than ran the GREP find-and-change that you posted. This eliminated all of the run-on superscripts.
I did try the PerfectPrepText_Do script (with the dependency PrepText script at the same level) and ended up still with runon italics and bold, unchanged from before running the script and still requiring manual corrections:
This is clearly, absolutely, 100% a bug in InDesign's Word importer. And in fact it's a trivial bug; during import, attributes get set when the importer sees those attributes in the Word file but don't get cleared when the attribute is reset in the Word file. This is the sort of bug in a C/C++ app that a first-year college intern with no formal experience should be able to fix. The fact that it still exists four years after this thread began is disappointing.
And the thing is, I've been using InDesign since version 1.0, and this bug didn't always exist. It was introduced sometime between InDesign CS6 and InDesign CC, and never fixed. When Adobe moved to a subscription model, one of the advantages they touted to users was faster updates and faster bug fixes. Guess that didn't happen.
When I do this on a Macbook Pro M1, I get this result, which I am quite comfortable calling an InDesign bug that Adobe is responsible for.
I bet there's probably a DoS or other security problem here, that can be exploited with maliciously crafted Word files. I'd do a proof of concept but I'm on deadline laying out a novel and don't have time.
Section 314(b) of the USA PATRIOT Act is an important tool for combatting financial crime. It provides financial institutions with the ability to share information with one another, under a safe harbor provision that offers protections from civil liability, in order to better identify and report potential money laundering or terrorist financing. After carefully considering feedback from the financial industry, FinCEN is providing three main clarifications:
Financial institutions subject to an anti-money laundering program requirement under FinCEN regulations, and any qualifying association of such financial institutions, are eligible to share information under Section 314(b). Although sharing information pursuant to Section 314(b) is voluntary, FinCEN strongly encourages financial institutions to participate to enhance their compliance with anti-money laundering/counter-financing of terrorism requirements. For additional questions related to 314(b) information sharing, contact FinCEN at 866-326-8314 or sys...@fincen.gov.
The mission of the Financial Crimes Enforcement Network is to safeguard the financial system from illicit use, combat money laundering and its related crimes including terrorism, and promote national security through the strategic use of financial authorities and the collection, analysis, and dissemination of financial intelligence.
The site is secure.
The ensures that you are connecting to the official website and that any information you provide is encrypted and transmitted securely.
When most people think of ethics (or morals), they think of rules for distinguishing between right and wrong, such as the Golden Rule ("Do unto others as you would have them do unto you"), a code of professional conduct like the Hippocratic Oath ("First of all, do no harm"), a religious creed like the Ten Commandments ("Thou Shalt not kill..."), or a wise aphorisms like the sayings of Confucius. This is the most common way of defining "ethics": norms for conduct that distinguish between acceptable and unacceptable behavior.
Most people learn ethical norms at home, at school, in church, or in other social settings. Although most people acquire their sense of right and wrong during childhood, moral development occurs throughout life and human beings pass through different stages of growth as they mature. Ethical norms are so ubiquitous that one might be tempted to regard them as simple commonsense. On the other hand, if morality were nothing more than commonsense, then why are there so many ethical disputes and issues in our society?
One plausible explanation of these disagreements is that all people recognize some common ethical norms but interpret, apply, and balance them in different ways in light of their own values and life experiences. For example, two people could agree that murder is wrong but disagree about the morality of abortion because they have different understandings of what it means to be a human being.
Most societies also have legal rules that govern behavior, but ethical norms tend to be broader and more informal than laws. Although most societies use laws to enforce widely accepted moral standards and ethical and legal rules use similar concepts, ethics and law are not the same. An action may be legal but unethical or illegal but ethical. We can also use ethical concepts and principles to criticize, evaluate, propose, or interpret laws. Indeed, in the last century, many social reformers have urged citizens to disobey laws they regarded as immoral or unjust laws. Peaceful civil disobedience is an ethical way of protesting laws or expressing political viewpoints.
c80f0f1006