\documentclass[a4paper, 11pt]{article}
\renewcommand{\familydefault}{\sfdefault}
\usepackage{a4wide}
\usepackage[utf8]{inputenc}
\usepackage[ngerman]{babel}
\usepackage{color}
\usepackage{graphicx}
\usepackage{setspace}
\usepackage{ulem}
\usepackage{listings}
\usepackage{float}
\usepackage[rflt]{floatflt}
\usepackage{tabularx}
\setlength{\parindent}{0pt}
\title{browscap.ini issues}
\usepackage[
pdftitle={browscap.ini issues}
pdfsubject={Problems in the analysis of user agent strings based on the browscap.ini}
pdfauthor={Udo Schmal}
pdfkeywords={Analyse, ISAPI-Filter, browscap.ini, browscap, Free Pascal, ISAPI CMS}
]{hyperref}
\definecolor{darkblue}{rgb}{0,0,.5}
\hypersetup{pdftex=true, colorlinks=true, breaklinks=true, linkcolor=darkblue, menucolor=darkblue, pagecolor=darkblue, urlcolor=darkblue}
\begin{document}browscap.ini issues
\singlespacing
{\LARGE \textbf{\label{sec:title}Problems in the analysis of user agent strings based on the browscap.ini}}

The list of user agents strings that can not be identified with the current Browscap.ini.

Currently, the list of unrecognized browsers and bots is getting longer and longer, as the browscap.ini file grows steadily.

It is to be considered whether browscap.ini is still the right method for the identification of a browser or bot with ever-increasing number of useragend strings. In my opinion, a method should be chosen to read the data of the User-Agend string that identifies the client by means of certain rules and a defined vocabulary. My idea, method and implementation I presented on the site \href{http://www.gocher.me/User-Agent-String}{User-Agent-String}.\newline
\newline

\label{sec:browscap_issues}\end{document}