Change Markdown Syntax Page



The current page is here: [https://www.daniweb.com/welcome/syntax](/welcome/syntax)


Sorry, but not sure whether wading through DW's history of BBCode is relevant to anybody. I gave up the will to live after the 100th paragraph of why Markdown and who did what to whom. Urgh.


Can't there just be a table?


`HTML tag | Markdown | Example`


or something similar? 


Then just a simple, "No HTML tags, BBCode or any other Markdown will be parsed". 


Sorry if I'm coming across like a grumpy old fart. Maybe it's because I am. :(
I'm currently writing a Markdown powered CMS, which adheres to [Commonmark](http://commonmark.org). Their [help page](http://commonmark.org/help/) is quick, easy and to-the-point.
I suppose you could try overriding the encoding in the `HtmlWeb` object.


Try this:



```
var web = new HtmlWeb
{
    AutoDetectEncoding = false,
    OverrideEncoding = myEncoding,
};
var doc = web.Load(myUrl);

```

Note: It appears that the `OverrideEncoding` property was added to HTML agility pack in revision 76610 so it is not available in the current release v1.4 (66017). The next best thing to do would be to read the page manually with the encodings overridden. Thanks for your reply, I feared it would not be trivail, as I coudnt find any scripts. Idealy the text from the databse is place in a table witht the last column beeing the barcodes path, the images are to replace the text path and be place inside the cell, fitting within the cells width and/or height. hey [@edgar.mtz](/u/edgar.mtz),

currently [interpretation](https://support.zoom.us/hc/en-us/articles/360034919791-language-interpretation-in-meetings-and-webinars) is not available on the web sdk.

here is a list of the supported features:

[image]

[web - native sdks - zoom software development kit (zoom sdk)](https://marketplace.zoom.us/docs/sdk/native-sdks/web#browser-support)

zoom web sdk

the web sdk enables the development of video applications powered by zoom's core framewo… Yes, there is. See:  

  

<https://www.wikitree.com/wiki/Template:Delete_Category>  

  

If you tag this question with "Categorization", someone with the proper authority will soon pick it up. <p>a h1 tag is still the recommended way by w3 to headline a page:</p>
<p><a href="http://www.w3.org/qa/tips/use\_h1\_for\_title">http://www.w3.org/qa/tips/use\_h1\_for\_title</a></p>
<p><a href="http://www.w3.org/qa/tips/headings">http://www.w3.org/qa/tips/headings</a></p>
<p><a href="http://www.w3.org/tr/rec-html40/struct/global.html#h-7.5.5">http://www.w3.org/tr/rec-html40/struct/global.html#h-7.5.5</a></p>
<p>i still find that by following w3 recommendations it makes a good step in creating a well optimised page. obviously you aren't going to rank by having a h1 tag alone, but it will always never harm the page to have a well crafted one. one thing i do recommend is having a different h1 tag to the page title.</p> Basically you don't see any fields because you have the option `initial`
  




 (adsbygoogle = window.adsbygoogle || []).push({});
 
  

set to `false`
  




 (adsbygoogle = window.adsbygoogle || []).push({});
 
  

for all of them.


 `initial`
  




 (adsbygoogle = window.adsbygoogle || []).push({});
 
  

the default is used `false`
  




 (adsbygoogle = window.adsbygoogle || []).push({});
 
  

, except for the "name" field, that is, the default is an outline field `name`
  




 (adsbygoogle = window.adsbygoogle || []).push({});
 
  

or path that matches the mapping specified by Keystone for `name`
  




 (adsbygoogle = window.adsbygoogle || []).push({});
 
  

, in your case `menuTitle`
  




 (adsbygoogle = window.adsbygoogle || []).push({});
 
  

.


So normally your field `menuTitle`
  




 (adsbygoogle = window.adsbygoogle || []).push({});
 
  

will render, expect you to explicitly tell it not with customization `initial: false`
  




 (adsbygoogle = window.adsbygoogle || []).push({});
 
  

.



  




 (adsbygoogle = window.adsbygoogle || []).push({});
 
  

To display the fields, just set the ones you want `initial: true`
  




 (adsbygoogle = window.adsbygoogle || []).push({});
 
  

, for example:



```
var keystone = require('keystone'),
    Types = keystone.Field.Types;

var Page = new keystone.List('Page', {
    autokey: { path: 'slug', from: 'menuTitle', unique: true },
    map: { name: 'menuTitle' },
});

Page.add({
    keyword: { type: Types.Key, required: true, initial: true },
    type: { type: Types.Select, options: 'textpage, projects, services, contacts, homepage', default: 'textpage' },
    menuTtle: { type: String, required: true, initial: true },
    pageTitle: { type: String, initial: true },
    pageContent: { type: Types.Html, wysiwyg: true, height: 400 },
    seoTitle: { type: String },
    seoKeywords: { type: String },
    seoDescription: { type: String },
    isActive: { type: Types.Boolean }
});

Page.defaultColumns = 'keyword, slug, menuTitle, isActive';
Page.register();

        

        
        
        
 (adsbygoogle = window.adsbygoogle || []).push({});
 
        

    
```

It's also worth noting that you don't need to add a field `slug`
  




 (adsbygoogle = window.adsbygoogle || []).push({});
 
  

; it is automatically added to the schema for you due to your settings `autokey`
  




 (adsbygoogle = window.adsbygoogle || []).push({});
 
  

. ah! someone gave me the answer!

[chrome recently applied](https://www.kevel.co/blog/chrome-samesite/) a new default of " lax " to the " samesite " parameter of cookies. lax was not lax enough; i needed to set samesite=none .

added to [localsettings.php of mediawiki](https://www.mediawiki.org/wiki/manual:%24wgcookiesamesite):

$wgcookiesamesite='none';

thanks!!

​ you put the code i’ve given to layouts/\_default/\_markup/render-image.html and it executes for every image you have in your markdown. that’s what \_markup render-hooks are for. > 
> When I'm on a discussion, it shows up!
> 
> 
> 


The discussion still based on the old code.



> 
> Or do any of you guys still have it available?
> 
> 
> 


It is still possible to use:


![](http://pix.academ.info/img/2017/11/18/3d272cacfc99d5afdf92f0374cf5c406.png)


You just need to turn off the new code:


* Go to any page of the forum (this page is good).
* Write `duo.old_web_url_whitelist=["^.+"];` in the browser console and press "Enter".
* Go to home, then to the lingot store, and take the test.
* Enjoy! 1) Usage `yii`
  




 (adsbygoogle = window.adsbygoogle || []).push({});
 
  

and `php yii`
  




 (adsbygoogle = window.adsbygoogle || []).push({});
 
  

exactly the same. If you look at the file `yii`
  




 (adsbygoogle = window.adsbygoogle || []).push({});
 
  

, you'll see it in the first line `#!/usr/bin/env php`
  




 (adsbygoogle = window.adsbygoogle || []).push({});
 
  

. This is called the "shebang" syntax and instructs your shell to automatically execute the `yii`
  




 (adsbygoogle = window.adsbygoogle || []).push({});
 
  

script using binary code `php`
  




 (adsbygoogle = window.adsbygoogle || []).push({});
 
  

. See: [https://en.wikipedia.org/wiki/Shebang\_%28Unix%29](https://translate.googleusercontent.com/translate_c?depth=1&pto=aue&rurl=translate.google.com&sl=ru&sp=nmt4&tl=en&u=)


2) The difference here is flexibility. If you use the syntax `Schema::TYPE_PK`
  




 (adsbygoogle = window.adsbygoogle || []).push({});
 
  

, Yii will automatically detect the exact column type based on your database database. For example, it `Schema::TYPE_PK`
  




 (adsbygoogle = window.adsbygoogle || []).push({});
 
  

translates to `int(11) NOT NULL AUTO_INCREMENT PRIMARY KEY`
  




 (adsbygoogle = window.adsbygoogle || []).push({});
 
  

in MySQL, but if you use Postgres as your database, it will translate to `serial NOT NULL PRIMARY KEY`
  




 (adsbygoogle = window.adsbygoogle || []).push({});
 
  

. [1]



  




 (adsbygoogle = window.adsbygoogle || []).push({});
 
  

In practice, it is unlikely which method you are using because you are probably not going to switch to a different type of database halfway through your project, and therefore there is no need for your migration scripts to be database agnostic. Based on your preference, you can choose the syntax `Schema`
  




 (adsbygoogle = window.adsbygoogle || []).push({});
 
  

for added flexibility, or for a hard-coded syntax to make your hyphenation definitions more readable for future readers.


[1] See [https://github.com/yiisoft/yii2/blob/master/framework/db/pgsql/QueryBuilder.php#L21](https://translate.googleusercontent.com/translate_c?depth=1&pto=aue&rurl=translate.google.com&sl=ru&sp=nmt4&tl=en&u=) and [https://github.com/yiisoft/yii2/blob/master/framework /db/mysql/QueryBuilder.php#L24](https://translate.googleusercontent.com/translate_c?depth=1&pto=aue&rurl=translate.google.com&sl=ru&sp=nmt4&tl=en&u=)