Results for my phone is not good that translation from Tajik to English

the name is not known
add folder

pgp signature is not verified
the signature has been verified successfully:

'% 1' is not a valid qlayout.
'%1' is not a valid qlayout.

% 1 is not a function and cannot be called.
%1 is not a function and cannot be called.

% 1 бит, бо истифодаи% 2 бити рамзи блокӣthe certificate is not trusted
%1, using %2 bits of a %3 bit key

% 1% (пур шуд) shown when a time estimate is not available
%1% (charged)

either the hardware/ software the module configures is not available or the module has been disabled by the administrator.
either the hardware/software the module configures is not available or the module has been disabled by the administrator.

somehow user has gotten a voice type that is not valid, i. e. not male1, male2, etc.
girl

Шумо метавонед ин алоқа нобуд кардан? opening is not allowed in "data view/ design view/ text view" mode
do you want to save changes?

no subtree check this option disables subtree checking, which has mild security implications, but can improve reliability is some circumstances. if a subdirectory of a filesystem is exported, but the whole filesystem is not, then whenever a nfs request arrives, the server must check not only that the accessed file is in the appropriate filesystem (which is easy) but also that it is in the exported tree (which is harder). this check is called the subtree_ check. in order to perform this check, the server must include some information about the location of the file in the "filehandle" that is given to the client. this can cause problems with accessing files that are renamed while a client has them open (though in many simple cases it will still work). subtree checking is also used to make sure that files inside directories to which only root has access can only be accessed if the filesystem is exported with no_ root_ squash (see below), even the file itself allows more general access. as a general guide, a home directory filesystem, which is normally exported at the root and may see lots of file renames, should be exported with subtree checking disabled. a filesystem which is mostly read- only, and at least does not see many file renames (e. g. / usr or / var) and for which subdirectories may be exported, should probably be exported with subtree checks enabled.
no subtree check this option disables subtree checking, which has mild security implications, but can improve reliability is some circumstances. if a subdirectory of a filesystem is exported, but the whole filesystem is not, then whenever a nfs request arrives, the server must check not only that the accessed file is in the appropriate filesystem (which is easy) but also that it is in the exported tree (which is harder). this check is called the subtree_check. in order to perform this check, the server must include some information about the location of the file in the "filehandle" that is given to the client. this can cause problems with accessing files that are renamed while a client has them open (though in many simple cases it will still work). subtree checking is also used to make sure that files inside directories to which only root has access can only be accessed if the filesystem is exported with no_root_squash (see below), even the file itself allows more general access. as a general guide, a home directory filesystem, which is normally exported at the root and may see lots of file renames, should be exported with subtree checking disabled. a filesystem which is mostly read-only, and at least does not see many file renames (e. g. / usr or / var) and for which subdirectories may be exported, should probably be exported with subtree checks enabled.