I use aspose cells.copyRow function but cannot copy the "Merge and center" format, as shown in the diagram, why?
my aspose versoin is 21.10
Related
I have a situation where the source file is an EXCEL with a sheet in it. I am looking to use the same excel file as a destination file where by creating a new sheet in the same excel file. In an attempt, to achieve this, I took excel destination, in its editor, I tried to use the NEW feature that is right beside the feature "Name of the Excel Sheet" and VS is throwing the following error, would anyone please help me understand the scenario. Thank you for giving me your valuable.
Hi You cannot read and write to same excel file simultaneously. Create an intermediate step (.CSV file or .xlsx file etc) and use that file as a source file to write to the preferred excel sheet.
I am trying to migrate a load of documentation which was written in markdown into a Google Doc so it can be used by our marketing department.
Is there a mechanism using appscript/ Google Docs Api that I can import a file and convert it to a Google Doc using a predefined template?
Eg H1s will map to Title, etc
One suggestion: use Pandoc to convert Markdown to docx, then import to Google Docs using the Google Drive API.
You can also accomplish this using the Google Drive web interface:
Convert markdown to ODT (or some other intermediate) using pandoc: pandoc MyFile.md -f markdown -t odt -s -o MyFile.odt
Move the ODT file into your Google Drive folder.
Right-click the ODT file (in the web version of Drive) and press "Open With -> Google Docs".
Google Drive will now create a new Google Doc, with contents matching the ODT file, and open it for you.
No add-ons needed
I just stumbled upon a really simple approach that may suit your needs.
In github, I opened a ReadMe.md file, rendered in the browser as rich text. I copied it from the browser and pasted it into a new Google Doc.
Voila: Google Docs preserved the headings, bullets, etc. I can't vouch for what it does with links and other fancier markdown ops, but it was a quick way to get started.
Easiest way that most likely requires no new tooling for many developers (if you're willing to do some manual pasting):
Just use Visual Studio Code.
Paste text into the editor.
At bottom right, select markdown as language.
Top right, click the preview button.
This will split the screen and show the rendered markdown you can paste into google docs.
It's pretty quick at this point to just keep paste markdown/copy result/repeat as long as you don't have hundreds of docs.
Of course, if it's a ton of docs, you'll want something more automated than this.
One variation of the suggestion to use pandoc: try using the docx format instead of odt. Google Docs handles MS Office files natively so I found formatting was preserved somewhat better using this approach.
Revised steps:
Convert markdown to DOCX using pandoc: pandoc MyFile.md -f markdown -t docx -s -o MyFile.docx
Upload MyFile.docx into your Google Drive folder
Double-click MyFile.docx in the web version of Drive
Google Drive will open MyFile.docx in a new tab
I don't know of a tool or library that allows for a direct conversion from markdown to a google doc.
Maybe you can convert your markdown to an intermediary format compatible with Google Docs (viable formats include .docx, .docm .dot, .dotx, .dotm, .html, plain text (.txt), .rtf and .odt) and then go from there.
You just need to find a tool that can convert markdown to one of those formats and also process your files in bulk (maybe some command-line utility could help with that).
There is the Google Docs Addon Markdown to Docs ... which converts Markdown to Google Docs.
It has its limitations due to the Gdoc format but works otherwise very well.
#!/bin/bash
# Create the "converted" directory if it doesn't already exist
if [ ! -d "converted" ]; then
mkdir "converted"
fi
# Find all markdown files in the current directory and its subdirectories
find . -name "*.md" | while read filename; do
# Use pandoc to convert the file to a .docx file
pandoc "$filename" -o "${filename%.*}.docx"
# Create the same directory structure under "converted" as the original file
dir=$(dirname "$filename")
mkdir -p "converted/$dir"
# Move the converted file to the "converted" directory
mv "${filename%.*}.docx" "converted/$dir"
done
Within Jupyter, there's two options to export notebooks to other formats, using nbconvert either on the command-line or as a library. Both require you to pass the original notebook as input (either as a file name or JSON data).
What I would like to do is essentially automatic, self-contained report generation, i.e. use the nbconvert library within a notebook, to export that same notebook to HTML/PDF on execution. I envisage the export code in the final cell of the document, with instructions to ignore that last cell on export.
My problem is in getting the data. Within the notebook I can access the code cells through In[1], Out[2] etc, but AFAIK there is no such functionality for markdown cells. There's also no (official) method to grab the name of the notebook (no __file__ attribute) to pass information that way.
There's plenty of examples to grab all the cell data from other notebooks - but is there a way to access all the cell data from the current notebook?
You can do this with the notebook filename and nbconvert, as you surmise. Doing some stuff client side might require extensions, one I can envision is a server extension to do the convert, and a bit of JS you write in the last code cell which renders a button, for example, and posts the notebook back to the convert server extension. Hiding certain cells (say, the Js cell) you can do in the convert extension, or with cell metadata and nbconvert templates. Given the flexibility of the architecture, there are quite a few ways to do this
From one source file I made a copy using hg copy.
Now I'm going to Change some stuff in the second file (the copy) and I want to be able to merge the future changes of the original file into the second file.
Can this be done using hg merge? Right now when I try to do something like
hg merge NewFile.html -r 130:f24199b5b945
using the most current changeset of the original file, I get an error: abort: please specify just one revision.
No, the two files are separate after that, and except for one file originating from the other, they do not share any history after that.
You will either have to duplicate your modifications in the other file, or you need to find another way to do this.
I use Mercurial in my project and we just switched to "force text" in the Asset Serialization option.
My files are text now, but when I try to merge, I get this "tool opendiff can't handle binary" message. I tried to force FileMerge to merge and it marks the whole file as different.
I tried to switch to DiffMerge and force it to merge, and it tells an important info: "File has a NUL byte at offset 0; this is not valid for encoding..."
The file bash command tells me that those asset files are "text/plain; charset=us-ascii".
hg diff between the two revisions results in a YAML text file, so both files are in text mode.
Isn't that a bug? I mean, Unity should convert to text files that merge tools are able to merge...
By the way, we are using Mac OSX.
Don't try to convert the project in more than one repository and after merge them.
Somehow it worked when I converted the project on one repo and distributed it to others, that is, no problem in future merges.
The downside is that everybody has to get to the same revision, stop to work and wait for the conversion.