Lens: What is the advantage of not using names, but only descriptions as unique identifiers for lenses?

Am I correct in noting that the lenses do not have names …?

No.Lenses have names, multiple names, such as model numbers and FCC IDs. Manufacturers need a way to track what they do and sell. Some manufacturers also give brand names to their lenses.

Since model numbers often do not convey information that consumers need to determine whether to purchase a lens, the specs themselves also serve as a (common) name. Most manufacturers have only one Current lens model with a given set of specifications. Consumers may refer to lenses with abbreviated names, such as "Nikon 18-55mm", and there will generally only be one current match model. More information is needed when looking at used lenses, but it's not that difficult. If you don't remember if you want the v1 or v2 lens, it probably doesn't matter. If it's important, write it down, bookmark the review, or ask Google.

… when I am looking for a new lens, I can never find a model number.

Whether you can find the model number is a different question than whether it exists. Model numbers for some manufacturers may be for internal use only (not well publicized).

A little search on the Nikon website reveals that the model number of a lens from the aforementioned Nikon kit is: AFS18-55_3.5-5.6GVRII_NT (7C_DL). Note that it is similar to the common name, with no spaces or units of measure. By learning the common name, you are effectively using the model number.

… there must be some advantage to using descriptions for lenses.

Common names (referred to as descriptions) are easier to remember than arbitrary model numbers. People are also often more interested in the specifications, which govern how the product will be used. Suppose a company presented Elijah and Elisha lenses. Are you going to buy them according to their names? Wouldn't you be interested in the specs? Someone looking for a 35mm lens can safely skip the 85mm lens reviews.

I heard that lenses used to have names, but it got confusing.

Marketing names are confusing. For example, what are the differences between Pancolar, Planar, Sonnar, Biotar, Biometar, Minitar, Lomogon, Xenon, Xenar, Hexanon, Hexar, Rokkor, Celtic, …? What if I tell you that these names, more or less, see 50mm lenses for different camera systems? If you have a single camera system, just knowing you want 50 / 1.8 is enough to get the right one.

Wow, two of those lenses are 32mm … That's the craziness of trusting these kinds of names. You remember the name, but you get the wrong lens anyway.

You still need to know the mounting or opening to distinguish them.

It is not too much to expect people to know which mount they need for their camera. Most people at least know what camera they are using. Most sellers can use that information to determine mounting.

Can anyone explain to me what is the difference between lenses and other consumer electronic products?

Marketing names say nothing to people about how the product will be used. For products such as cars, televisions, and cameras, usage is determined by product type. But the use of lenses is governed by certain specifications. If you need a specific FOV, you need to find lenses with particular focal lengths. If you want to shoot at 1: 1 ratios, you need a macro lens. Elegant names do not convey that information.

attachments: document file names automatically change during Share

I am using a Huawei Y7 Android 8.1.0. Every time I select share for a PDF or DOCX file and select whatsapp or viber, the file is renamed to a longer name. On Whatsapp it shows & # 39; NULL & # 39; in the thread. When opened within Whatsapp, it shows a long file name. Anyone know how to stop this. It happens for file names of less than 8 characters. My problem is that I want to share the file with the name that I have given it, but not with a long and meaningless code. All software, including Android and apps, is updated. Clear app caches. Can anyone help?

Websites with unintended funny names

Sort of like MorristownScrap, which could read Morristown & # 39; sCrap. :RE


This could be a problem when choosing a domain name. Who thought of it?

Spring Boot addResourceHandler does not redact until file names are changed

I work on intellij ultimate 2019.3 and added Tomcat 9.0.33 as my server for my SpringBoot app. Fedora 31.
I am following the plural tutorial "Spring Framework: Spring MVC Fundamentals" and I am in Chapter 6 "Solving Static Files".

So the problem is that I added those lines

    public void addResourceHandlers(ResourceHandlerRegistry registry) {

and drag and drop a pdf file into my / WEB-INF / pdf / directory.
When I started my app and tried to open it at http: // localhost: 8080 / pluralsightmvc / files / pdf / mypdf.pdf
it gave me a 404 page error

HTTP Status 404 – Not Found
Type Status Report

Message /pluralsightmvc/WEB-INF/jsp/error.jsp

Description The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.

Apache Tomcat/9.0.33

If I change the name of the pdf (within intellij or in my file browser) and restart the application, it will work without problems.
http: // localhost: 8080 / pluralsightmvc / files / pdf / myRenamedPdf.pdf

Am I doing something wrong?

nginx: https with two sni certs but server names but the same configuration. Can I use a server block?

I often run into the following problem.

I have an nginx server that serves two host names through https on the same IP and the same port. Each hostname has its own certificate.

What I'm doing so far is having two settings:

server {
    listen              443 ssl;
    server_name         www.example1.com;
    ssl_certificate     www.example1.com.crt;
    ssl_certificate_key www.example1.com.key;
    ssl_protocols       ...;
    ssl_ciphers         ...;


server {
    listen              443 ssl;
    server_name         www.example2.com;
    ssl_certificate     www.example2.com.crt;
    ssl_certificate_key www.example2.com.key;
    ssl_protocols       ...;
    ssl_ciphers         ...;

Is there a trick to do this on a single server block?

The reason I am asking is that both servers share, apart from the name and the certificate, exactly the same configuration.

What I do so far is:

server {
    listen              443 ssl;
    server_name         www.example1.com;
    ssl_certificate     www.example1.com.crt;
    ssl_certificate_key www.example1.com.key;
    include /etc/nginx/common_config/example1_and_2/*;

server {
    listen              443 ssl;
    server_name         www.example2.com;
    ssl_certificate     www.example2.com.crt;
    ssl_certificate_key www.example2.com.key;
    include /etc/nginx/common_config/example1_and_2/*;

It can improve? Are there any standard recommendations?
If this is good, is there at least a recommendation for the path to such common configuration files?

Website design – Language of language names in the language selector?

Anyway, although what others have answered is good, it does not reach the big picture. I will give you what I think is the IDEAL answer.

Basically this answer provides Multiple tracks (instead of a single track) for language selection.

First It is the name of the language (according to the previous answers), as it provides a basic interface for anyone literate in English.

Second is the name of the language in your own native script, for a person literate in the basic native language. e.g.
enter the image description here

Third It is a flag for the country. For languages ​​spoken in dialects and common countries, the country of origin or the country of speech can be used. E.g. ENGLISH (must have the flag of the United Kingdom), ENGLISH OF THE UNITED KINGDOM, ENGLISH OF THE USA USA (Must have the flag of their respective countries). A visual clue that overlooks the thinking part of the brain.

Below is a poor screenshot from this example, from the website http://blog.myheritage.com/2009/06/small-changes-big-differences-new-header-and-footer/
enter the image description here

Many apps I've seen have implemented this correctly, and I urge the rest to follow this.

Some other required features are fast filtering of keyboard-displayed languages, such as listing for lists, to narrow down results. I like it if you are specifically looking for English (Singapore).

Also, the location of the language selector is very important. Must be ideally located above the fold (that is, on the first page) somewhere. General practice is the upper right corner, below any profile information you may have. IT IS A MUST for first-time visitors, can be hidden from regular visitors (i.e. the site is already in your preferred language) and can be accessed through the second location.
The second common location is at the bottom of the page, centered or left aligned. Although I think it should always be available at first glance. The same is true for applications.

Ahhh, this is one of my hobbies!
For example, see Chrome! (I know it is an app, but please be patient with me) It has the most horrible user experience to change the language to English from a language unknown to the user. It requires an excessive amount of clicks and absolute confusion!

  1. Menu icon
  2. Configuration menu item (no icon! For clear / easy identification when using an unknown language)
  3. Click Show advanced settings text.
  4. Click Language (absolutely no way to find it in an unknown language)
  5. Click Add
  6. Choose your language
  7. Move it to the top of the screen.
  8. Click the button on the right to make it Chrome's default language. (Some languages ​​can't be done this way either, and can only be used for spelling! You should separate these dialogs and not combine spelling and language selection dialog! As the most common case is probably selecting language, and a very distant one is the spell checker selection).
  9. Restart Chrome!

Some interesting links I found with contrary opinions and other useful resources.

Best practice for presenting languages


Sale of many domain names

[*]Hello guys,

I am selling these domains:

[LIST] [*] muskbank.com [*] royalcarinsurance.com [*] teslainsurer.com [*] applecheckout.com
… | Read the rest of https://www.webhostingtalk.com/showthread.php?t=1803151&goto=newpost