Results for it's just a song but it's not a jus... translation from English to Tajik

he knows what is in land and sea; not a leaf falls, but he knows it. not a grain in the earth's shadows, not a thing, fresh or withered, but it is in a book manifest.
Ҳар чиро, ки дар хушкиву дарёст, медонад. Ҳеҷ барге аз дарахте намеафтад, магар он ки аз он огоҳ аст, Ва ҳеҷ донае дар торикиҳои замин ва ҳеҷ тареву хушке нест, ҷуз он ки дар китоби мубин Лавҳул маҳфуз омада аст.

not a leaf falleth but he knoweth it, not a grain amid the darkness of the earth, naught of wet or dry but (it is noted) in a clear record.
Ҳеҷ барге аз дарахте намеафтад, магар он ки аз он огоҳ аст, Ва ҳеҷ донае дар торикиҳои замин ва ҳеҷ тареву хушке нест, ҷуз он ки дар китоби мубин Лавҳул маҳфуз омада аст.

is it that you will inform him of something he knows not in the earth or is it (just) a show of false words."
Шояд мехоҳед Ӯро аз чизе дар рӯи замин огоҳ кунед, ки намедонад, ё суханони беҳуда мегӯянд?»

no hide this option is based on the option of the same name provided in irix nfs. normally, if a server exports two filesystems one of which is mounted on the other, then the client will have to mount both filesystems explicitly to get access to them. if it just mounts the parent, it will see an empty directory at the place where the other filesystem is mounted. that filesystem is "hidden". setting the nohide option on a filesystem causes it not to be hidden, and an appropriately authorized client will be able to move from the parent to that filesystem without noticing the change. however, some nfs clients do not cope well with this situation as, for instance, it is then possible for two files in the one apparent filesystem to have the same inode number. the nohide option is currently only effective on single host exports. it does not work reliably with netgroup, subnet, or wildcard exports. this option can be very useful in some situations, but it should be used with due care, and only after confirming that the client system copes with the situation effectively.
no hide this option is based on the option of the same name provided in irix nfs. normally, if a server exports two filesystems one of which is mounted on the other, then the client will have to mount both filesystems explicitly to get access to them. if it just mounts the parent, it will see an empty directory at the place where the other filesystem is mounted. that filesystem is "hidden". setting the nohide option on a filesystem causes it not to be hidden, and an appropriately authorized client will be able to move from the parent to that filesystem without noticing the change. however, some nfs clients do not cope well with this situation as, for instance, it is then possible for two files in the one apparent filesystem to have the same inode number. the nohide option is currently only effective on single host exports. it does not work reliably with netgroup, subnet, or wildcard exports. this option can be very useful in some situations, but it should be used with due care, and only after confirming that the client system copes with the situation effectively.