This question already has answers here:
Can I make a phone call from HTML on Android?
(3 answers)
Closed 9 years ago.
I am making an html link for a phone.
This is what I have:
1-888-888-8888
Will phones recognize this, or do I need to change it to:
1-888-888-8888
Visual separators (except for spaces) are allowed in the uri.
From RFC 3966 "The tel URI for Telephone Numbers":
5.1.1. Separators in Phone Numbers
Phone numbers MAY contain visual separators. Visual separators
('visual-separator') merely aid readability and are not used for URI
comparison or placing a call ... "tel" URIs MUST NOT use spaces in visual separators ...
Related
This question already has answers here:
Using explicitly numbered repetition instead of question mark, star and plus
(4 answers)
Closed 2 years ago.
I have a pattern that I am using and it does everything I need it to except for it does not allow for an 10 digit phone number and not all UK numbers are 11 digits, for example, 01932 783433 is allowed and valid but 01932 78383 is also valid but not allowed;
Pattern:
^\s*\(?(020[7,8]{1}\)?[ ]?[1-9]{1}[0-9{2}[ ]?[0-9]{4})|(0[1-8]{1}[0-9]{3}\)?[ ]?[1-9]{1}[0-9]{2}[ ]?[0-9]{3})\s*$
I've tried without success to edit the pattern but each time I make a change and think I'm there the pattern starts allowing non numeric characters like 'ext 456' (extension numbers) at the end which is what I am trying to stop.
Is anyone able to help with a solution to make the 11th digit optional without changing anything else?
The comments of changing {3} to {2,3} resolve the issue I was having and the pointer to regex101.com were very useful in understanding my issue.
This question already has answers here:
HTML entities and charset in IE
(7 answers)
Closed 9 years ago.
I use ✓ ! ✗ for show ✓ ! ✗ symbols and it is works for major browser Firefox, chrome and others. But they is not working for internet explore. Can't i use these any more? What are the alternatives for these symbol?
Those references are undefined in any HTML specification, but proposed in the HTML5 Candidate Recommendation. Around 2011, some browsers started supporting them, and IE 10 has joined the gang, but e.g. IE 9 renders them literally, like any pre-2011 browser.
So these references should not be used yet, if ever. They add nothing to the expressive power of the language, but they cause serious incompatibilities, for a long time. As #Quentin recommends, use the characters themselves or (if you do not know how to enter them, or if you are forced to use an encoding other than UTF-8) numeric character references like ✓ and ✗. (There is not reason to use a reference for the “!” character – ! denotes just the common exclamation mark we have in our keyboards. You can find the Unicode numbers (needed for the numeric references) from the same source in which the named references are listed in HTML5 CR.
As a completely different problem with some of these characters, the font being used may well lack them, and this may force browsers to pick them up from other fonts (possibly creating a stylistic mismatch) or, in rather old systems, fail to render them at all. You should thus make sure that some of the fonts in the font-family list you use for the text containing them, in an acceptable shape.
Those entities are not defined in the HTML 4 specification.
Use literal characters (with a suitable encoding such as UTF-8) or numeric character references.
This question already has answers here:
Closed 10 years ago.
Possible Duplicate:
Why does Chrome incorrectly determine page is in a different language and offer to translate?
My entire page is written in English and not in Malay. However, chrome shows that the page is in Malay. What changes should I do in my code? Is it some HTML standard that I didn't adhere to?
It depends on what editor you used to save the file. Assuming you used Dreamweaver, there is a thing called BOM (byte order mark), when you look at the page properties in Dreamweaver, there should be encoding setting and the check box for BOM. It's possible that either the page was saved with Malay encoding. BOM signals that the text stream (file) is Unicode when set.
This question already has answers here:
Tick symbol in HTML/XHTML
(14 answers)
Closed 1 year ago.
Is there an HTML entity for a check mark?
I've searched for it in various html entities cheat sheets but didn't find it
Something like this?
✔
if so, type the HTML ✔
And ✓ gives a lighter one:
✓
Here are a couple: http://www.amp-what.com/unicode/search/check%20mark
✓
✔
HTML and XML entities are just a way of referencing a Unicode code-point in a way that reliably works regardless of the encoding of the actual page, making them useful for using esoteric Unicode characters in a page using 7-bit ASCII or some other encoding scheme, ideally on a one-off basis. They're also used to escape the <, >, " and & characters as these are reserved in SGML.
Anyway, Unicode has a number of tick/check characters, as per Wikipedia ( http://en.wikipedia.org/wiki/Tick_(check_mark) ).
Ideally you should save/store your HTML in a Unicode format like UTF-8 or 16, thus obviating the need to use HTML entities to represent a Unicode character. Nonetheless use: ✔ ✔.
✔
✔
Is using hex notation and is the same as
$#10004;
(as 2714 in base 16 is the same as 10004 in base 10)
There is HTML entity ✓ but it doesn't work in some older browsers.
This question already has answers here:
URI starting with two slashes ... how do they behave?
(4 answers)
Closed 9 years ago.
More and more, began to notice that the links in the source code on Web sites begin with two slashes. For example:
Image
Why do it?
It's a protocol-relative URL (typically HTTP or HTTPS). So if I'm on http://example.org and I link (or include an image, script, etc.) to //example.com/1.png, it goes to http://example.com/1.png. If I'm on https://example.org, it goes to https://example.com/1.png.
This lets you easily avoid mixed content security errors.