Why does Google show the rating percent symbol as HTML entity code?
In the base search results the percent symbol shows correct, but in rich snippets it is encoded.
This bug available in Google testing tool also.
For example, JSON-LD for Google Structured Data Testing Tool: https://gist.github.com/ZhandosKz/996308ef58fbd8382203f6843a81231e
In preview we will see:
Related
I have PDF documents, that has lots of screenshots and very less text. How can I show the PDF itself directly, when a user asks for a particular question.
Based on your description of the document in question it sounds like QnA Maker is the wrong tool for the job.
The following is from the official documentation:
QnA Maker imports your content into a knowledge base of question and answer pairs.
QnA Maker does not perform OCR on the ingested documents. You could use the Read API which is part of the Computer Vision offering to OCR the document and extract text from the images, then input into QnA Maker.
Alternatively, you could manually update the QnA pair in question to include the link to the PDF using the markdown syntax outlined here.
e.g. For more information, see product PDF which is available [here](https://<your-url-here>).
Well, I got the solution to this. There is a Link icon on the answers section in qnamaker.ai, where we can provide a link to the pdf, where pdf could be stored on a blob storage or any public location.
I have a 300+ page PDF document which needs to have internal page links added to it to reference other pages in the document. The document is created in Visio, which does not support consistent hyperlink generation in PDF export, so the link generation needs to be done on the PDF itself, not up the chain. This is an annual need, and regularly takes over a week due to the amount of manual labor, time, and checking needed.
The text which is hyperlinked has the same format in every case (e.g., "See Section 8.18 - How to Hyperlink"), and I'm certain this can be automated, as there are commercial plugins which can do this, but they cost hundreds of dollars, and are not able to be used in this case due to restrictions imposed by my employer. Example: https://www.evermap.com/ABAddingHyperlinks.asp
I've been looking through the Acrobat Plugin SDK and it seems doable, but I know there is also a higher level scripting language available for Acrobat. Does anyone have experience working with PDFs or with the Acrobat scripting / SDK tools? Are there open source methods for doing this? I've looked everywhere! Willing to learn. I've looked at Ghostscript (Adding internal hyperlink to a pdf) but what I need is way more than just a Table of Contents, and links can appear in many places on the page with line breaks, so consistency is a challenge.
EDIT: I found a solution! Bluebeam software's Revu Extreme works pretty darn well, and can be used as a 30 day free trial of all features. Only limitation is that links which extend across a line break (multiple lines of text) do not properly work in Edge or Chrome's PDF viewer, as they don't properly support hyperlinks with multiple click regions. I've submitted a ticket requesting a feature be added to Revu that fixes this, but for now those links need to be manually fixed following the batch link. The process is described here: https://support.bluebeam.com/online-help/revu2018/Content/RevuHelp/Menus/Batch/Link/Batch-Link--T.htm
EDIT: I found a solution! Bluebeam software's Revu Extreme works pretty darn well, and can be used as a 30 day free trial of all features. Only limitation is that links which extend across a line break (multiple lines of text) do not properly work in Edge or Chrome's PDF viewer, as they don't properly support hyperlinks with multiple click regions. I've submitted a ticket requesting a feature be added to Revu that fixes this, but for now those links need to be manually fixed following the batch link. The process is described here: https://support.bluebeam.com/online-help/revu2018/Content/RevuHelp/Menus/Batch/Link/Batch-Link--T.htm
You can add hyperlinks to a document with Ghostscript, but you would need to know the location of the text to hyperlink and the destination in advance, you cannot automate it or in fact write any reasonably simple code to automate the task using Ghostscript. You'd need to modify chunks of the PDF interpreter, which is written in PostScript and is not a task for anyone not a PostScript expert.
You could probably do it with MuPDF, and probably using MuJS to script it, but I don't know enough to be certain. It would still require some coding effort, but it would probably be easier to use JavaScript at least.
I have been trying for a while to get Phonetic or Phoneme pronunciation working with google's text to speech but have not managed to get it performing consistently.
I have managed to get limited results from using https://tophonetics.com/
It translated "The cow went mad." to "ðə kaʊ wɛnt mæd." but the 'the' 'ðə'
was not audible. And when I tried "ðɪs ɪz səm fəˈnɛtɪk tɛkst ˈɪnˌpʊt".
Are there any SSML codes to define phonetic blocks of text,
that can be this format "D,Is Iz sVm f#n'EtIk t'Ekst 'InpUt"
can be used instead of "ðɪs ɪz səm fəˈnɛtɪk tɛkst ˈɪnˌpʊt"
"
Google Text-to-Speech supports the <phoneme> tag since at least spring 2021.
However, there are a lot of potential gotchas to overcome:
The demo page filters out <phoneme> tags on the client side before they even reach the API. (It does the same with the <voice> tag as pointed out here)
As with Microsoft Azure Text-to-speech (see the other answer for details), each language only supports a limited set of phonemes ("letters") that can be used.
If you use an unsupported one, the phoneme tag is completely ignored without any warning. So the official example <phoneme alphabet="ipa" ph="ˌmænɪˈtoʊbə">manitoba</phoneme> does not work with any English variant but en-US, since all others lack the "o" or "oʊ" phoneme.
It's unclear if you need to use the v1beta1 API (which I can confirm is working) or if version v1 is also ok.
There is the SSML tag <phoneme> that serves your purpose.
Unfortunately, it's currently not supported in Google Cloud Text-to-speech. The available subset of SSML tags for Google Cloud is listed in the documentation. The <phoneme> tag is not in this list. An experiment using Google Cloud's text-to-speech-demo confirms that the phonemes are ignored. The content of the tag is being read as ordinary text, as has already been remarked by #Trevor in the comments.
The <phoneme> tag is, however, being supported by Microsoft Azure Text-to-Speech and Amazon Polly. In both cases, the available phonemes are limited to those available in the language being used (see here for Azure and here for Polly). The Azure documentation isn't 100% clear about the exclusion of out-of-language phonemes, but practical experiments with the Azure Text-to-Speech demo confirm that they're not working properly. In some cases, they at least seem to be replaced by the nearest available equivalent in the language used.
Being restricted to the phonemes of one language severely limits the usefulness of the phonemes tag. E.g., you can't used the feature to embed correctly pronounced content in a second language, as the second language will usually have some phonemes that are not available in the first language. Concrete language pairs in which each language has some phonemes that are not available in the other one are English/German, Spanish/German, English/Spanish.
I am looking for a JavaScript library like Google prettify (doesn't support MDX) to display MDX expressions in HTML so they can be displayed with color, indentation and line numbers.
Does anybody know such a library?
Thanks
You can make a store procedure with the MDX script and then with web services and jscript you can add colors...etc.
Take a look at this example
Can someone please explain what a "Tagged PDF" is, and how it differs from regular, non-tagged PDF?
Will tagged PDFs contain special content, such as XML, Rich Media, Javascript, or the like?
Which TeX-toolchains generate Tagged PDFs?
Tagged PDF is a PDF file that contains meta-information around certain groups of PDF instructions inside a page content. This meta-information has many use cases: Text-extraction, content-reflow, document accessibility, geographic information in PDF containing maps, etc.
If you need to know more details about this topic I would recommend reading Chapter 10 - Document Interchange of Adobe PDF Reference version 1.7.
The main reason it is used is for accessibility. With the correct tags, a screen reader (for a blind person) can understand where headings fall, what is a table/footnote/graphic and so on. Also there is a feature called PDF Article Threading which is useful for magazine or newspaper layouts where an article is split across boxes/pages.