Translate to Kazakh

Pages

Source text		Translations
#	What type of data the field will store Show related projects	(not translated)
#	Each field can store one type of data (text, number, file, etc.). When you define a field, you choose a particular <em>field type</em>, which corresponds to the type of data you want to store. The field type cannot be changed after you have created the field. Show related projects	(not translated)
#	How the data will be input and displayed Show related projects	(not translated)
#	How many values the field will store Show related projects	(not translated)
#	You can store one value, a specific maximum number of values, or an unlimited number of values in each field. For example, an employee identification number field might store a single number, whereas a phone number field might store multiple phone numbers. This setting can be changed after you have created the field, but if you reduce the maximum number of values, you may lose information. Show related projects	(not translated)
#	Reusing fields Show related projects	(not translated)
#	Once you have defined a field, you can reuse it. For example, if you define a custom image field for one content type, and you need to have an image field with the same parameters on another content type, you can add the same field to the second content type, in the <em>Add existing field</em> area of the user interface. You could also add this field to a taxonomy vocabulary, comments, user accounts, etc. Show related projects	(not translated)
#	Some settings of a reused field are unique to each use of the field; others are shared across all places you use the field. For example, the label of a text field is unique to each use, while the setting for the number of values is shared. Show related projects	(not translated)
#	There are two main reasons for reusing fields. First, reusing fields can save you time over defining new fields. Second, reusing fields also allows you to display, filter, group, and sort content together by field across content types. For example, the contributed Views module allows you to create lists and tables of content. So if you use the same field on multiple content types, you can create a View containing all of those content types together displaying that field, sorted by that field, and/or filtered by that field. Show related projects	(not translated)
#	Fields on content items Show related projects	(not translated)

Pages

Leave this field blank