对于每个用户，这个文件仅包含一条记录。
所以，用户不得不分别地展开每个方法.
每个用户条目必须具有单独的规则行。
正如我们所见，这些属性对每个用户而言是不同的。
As we will see, these attributes are different for each individual user.
显然，要使这个模型生效，每个用户都必须经过认证。
Obviously, for this model to work each user must be authenticated.
每个客户端都可以编写消息，然后广播给所有其他用户。
Each client can write messages that are then broadcast to all other users.
每个应用程序首先是一个应用程序用户。
Every application program is first and foremost an application user.
每个用户都可以轻松地处理自己的任务。
不过，它们可以记录每个用户的目的地。
每个用户请求期间所做的数据变更都要被保存。
Data changes made during every user request would need to be saved.
每个数据地图保存单个表单实例的用户输入。
Each data map maintains the user input of a single form instance.
可以看到，每个进程都有一个相关的所有者(用户名)。
As you can see, each process is associated with an owner (user name).
一个线程被创建来处理每个新用户连接。
因此，此数据地图ID对每个用户和页面的组合而言也是惟一的。
Therefore, the data map ID is unique for each user and page combination.
在以前，用户可以访问的每个页面的页面数据都是在登录时预加载的。
Previously, page data for every page a user could access was pre-loaded at login.
第一，每个状态基本上都与不同的系统用户相关。
First, each state tends to be relevant to different system users.
几乎每个网站都涉及到用户账户、注册、身份等概念。
Nearly every site has a concept of a user account, registration, and identity.
每个故事都跟一个用户活动相关联，而且都有个优先级。
Each story is associated with a user activity, and has a priority.
用户现在可以实际查看地图上每个球场的边界！
Users actually are able to view the boundaries of each course on the map!
每个联系人列表特定于一个门户用户。
根用户应该运行每个配置。
每个用户可以创建多个业务空间。
需要在每个页面上显示用户的购物车吗？
Do you need to display the user's shopping cart on every page?
该信息储存在用户定义的、应用到每个文档的属性表中。
This information is stored in a user-defined property sheet that is applied to each document.
确定每个用例都支持用户目标。
请确保每个用户都具有惟一id和惟一名称。
接下来，需要判断每个地理区域的目标用户社区。
Next, you need to determine the target user community per geography.
然而，每个客户外观存储都以指定的用户为对象。
However, each customer facing store can be targeted at the specific audience.
假设每个部门的子节点表示一组用户。
This is assuming that the children of each department represent a group of users.
每个用户每天事务的平均事务数为 5,407 个。
The average number of daily transactions per user was 5,407.
应用推荐