public void showMsg(int age, string name){/*...*/}
(int age, string name) value =(20, "Jessy");
showMsg(...value); //? or something else How many mobile apps have you used or seen?
<script src="Scripts/angular.js"></script>
<script src="Scripts/angular-translate.js"></script> angular.module('app', ['pascalprecht.translate'])
.config([
'$translateProvider', function ($translateProvider) {
// Adding a translation table for the English language
$translateProvider.translations('en_US', {
"TITLE": "How to use",
"HEADER": "You can translate texts by using a filter.",
"SUBHEADER": "And if you don't like filters, you can use a directive.",
"HTML_KEYS": "If you don't like an empty elements, you can write a key for the translation as an inner HTML of the directive.",
"DATA_TO_FILTER": "Your translations might also contain any static ({{staticValue}}) or random ({{randomValue}}) values, which are taken directly from the model.",
"DATA_TO_DIRECTIVE": "And it's no matter if you use filter or directive: static is still {{staticValue}} and random is still {{randomValue}}.",
"RAW_TO_FILTER": "In case you want to pass a {{type}} data to the filter, you have only to pass it as a filter parameter.",
"RAW_TO_DIRECTIVE": "This trick also works for {{type}} with a small mods.",
"SERVICE": "Of course, you can translate your strings directly in the js code by using a $translate service.",
"SERVICE_PARAMS": "And you are still able to pass params to the texts. Static = {{staticValue}}, random = {{randomValue}}."
});
// Adding a translation table for the Russian language
$translateProvider.translations('ru_RU', {
"TITLE": "Как пользоваться",
"HEADER": "Вы можете переводить тексты при помощи фильтра.",
"SUBHEADER": "А если Вам не нравятся фильтры, Вы можете воспользоваться директивой.",
"HTML_KEYS": "Если вам не нравятся пустые элементы, Вы можете записать ключ для перевода в как внутренний HTML директивы.",
"DATA_TO_FILTER": "Ваши переводы также могут содержать любые статичные ({{staticValue}}) или случайные ({{randomValue}}) значения, которые берутся прямо из модели.",
"DATA_TO_DIRECTIVE": "И совершенно не важно используете ли Вы фильтр или директиву: статическое значение по прежнему {{staticValue}} и случайное - {{randomValue}}.",
"RAW_TO_FILTER": "Если вы хотите передать \"сырые\" ({{type}}) данные фильтру, Вам всего лишь нужно передать их фильтру в качестве параметров.",
"RAW_TO_DIRECTIVE": "Это также работает и для директив ({{type}}) с небольшими модификациями.",
"SERVICE": "Конечно, Вы можете переводить ваши строки прямо в js коде при помощи сервиса $translate.",
"SERVICE_PARAMS": "И вы все еще можете передавать параметры в тексты. Статическое значение = {{staticValue}}, случайное = {{randomValue}}."
});
// Tell the module what language to use by default
$translateProvider.preferredLanguage('en_US');
}]) .controller('ctrl', ['$scope', '$translate', function ($scope, $translate) {
$scope.tlData = {
staticValue: 42,
randomValue: Math.floor(Math.random() * 1000)
};
$scope.jsTrSimple = $translate.instant('SERVICE');
$scope.jsTrParams = $translate.instant('SERVICE_PARAMS', $scope.tlData);
$scope.setLang = function (langKey) {
// You can change the language during runtime
$translate.use(langKey);
// A data generated by the script have to be regenerated
$scope.jsTrSimple = $translate.instant('SERVICE');
$scope.jsTrParams = $translate.instant('SERVICE_PARAMS', $scope.tlData);
};
}]); <p>
<a href="#" ng-click="setLang('en_US')">English</a>
|
<a href="#" ng-click="setLang('ru_RU')">Русский</a>
</p>
<!-- Translation by a filter -->
<h1>{{'HEADER' | translate}}</h1>
<!-- Translation by a directive -->
<h2 translate="SUBHEADER">Subheader</h2>
<!-- Using inner HTML as a key for translation -->
<p translate>HTML_KEYS</p>
<hr>
<!-- Passing a data object to the translation by the filter -->
<p>{{'DATA_TO_FILTER' | translate: tlData}}</p>
<!-- Passing a data object to the translation by the directive -->
<p translate="DATA_TO_DIRECTIVE" translate-values="{{tlData}}"></p>
<hr>
<!-- Passing a raw data to the filter -->
<p>{{'RAW_TO_FILTER' | translate:'{ type: "raw" }' }}</p>
<!-- Passing a raw data to the filter -->
<p translate="RAW_TO_DIRECTIVE" translate-values="{ type: 'directives' }"></p>
<hr>
<!-- Using a $translate service -->
<p>{{jsTrSimple}}</p>
<!-- Passing a data to the $translate service -->
<p>{{jsTrParams}}</p> <script src="Scripts/angular-cookies.js"></script>
<script src="Scripts/angular-translate-storage-cookie.js"></script> // Tell the module to store the language in the cookie $translateProvider.useCookieStorage();
این مثال همانند مثال قبل رفتار می‌کند، با این تفاوت که به جای اینکه کلید زبان کنونی را درون کوکی ذخیره کند، آن را درون Local Storage با نام NG_TRANSLATE_LANG_KEY قرار می‌دهد. برای اجرا کافیست اسکریپت‌ها و تکه کد زیر را با موارد مثال قبل جایگزین کنید.
<script src="Scripts/angular-translate-storage-local.js"></script> // Tell the module to store the language in the local storage $translateProvider.useLocalStorage();
مثال های ex4_set_a_storage_key و ex5_set_a_storage_prefix نام کلیدی که برای ذخیره سازی زبان کنونی در کوکی یا Local Storage قرار می‌گیرد را تغییر می‌دهد که به دلیل سادگی از شرح آن می‌گذریم.
translate table در angular-translate قابلیت مفید namespacing را نیز داراست. این قابلیت به ما کمک می‌کند که جهت کپسوله کردن بخش‌های مختلف، ترجمه آنها را با namespaceهای خاص خود نمایش دهیم. به مثال زیر توجه کنید:
$translateProvider.translations('en_US', {
"TITLE": "How to use namespaces",
"ns1": {
"HEADER": "A translations table supports namespaces.",
"SUBHEADER": "So you can to structurize your translation table well."
},
"ns2": {
"HEADER": "Do you want to have a structured translations table?",
"SUBHEADER": "You can to use namespaces now."
}
}); همانطور که توجه می‌کنید بخش ns1 خود شامل زیر مجموعه‌هایی است و ns2 نیز به همین صورت. هر کدام دارای کلید HEADER و SUBHEADER می‌باشند. فرض کنید هر کدام از این بخش‌ها می‌خواهند اطلاعات درون یک section را نمایش دهند. حال به نحوه‌ی فراخوانی این translate tableها دقت کنید:
<!-- section 1: Translate Table Called by ns1 namespace --> <h1 translate>ns1.HEADER</h1> <h2 translate>ns1.SUBHEADER</h2> <!-- section 2: Translate Table Called by ns2 namespace --> <h1 translate>ns2.HEADER</h1> <h2 translate>ns2.SUBHEADER</h2>
به همین سادگی می‌توان تمامی بخش‌ها را با namespaceهای مختلف در translate table قرار داد.
در بخش بعدی (پایانی) شش قابلیت دیگر angular translate که شامل فراخوانی translate table از یک فایل JSON، فراخوانی فایل‌های translate table به صورت lazy load و تغییر زبان بخشی از صفحه به صورت پویا هستند، بررسی خواهند شد.
فایل پروژه: AngularJs-Translate-BestPractices.zip
At The Bit, we understand how overwhelming it can be to navigate through all the different tutorials online and try to teach yourself programming skills alone.
That’s why we’ve created The Bit — we’ll match you to a peer with similar skills and interests to take the tutorial of your choosing.
Find a tutorial you want to take below? Upload it to our platform to get the support and accountability you need to start building cool shit.
DECLARE @data XML SET @data = '<people> <person> <name> <givenName>name1</givenName> <familyName>lname1</familyName> </name> <age>33</age> <height>short</height> </person> <person> <name> <givenName>name2</givenName> <familyName>lname2</familyName> </name> <age>40</age> <height>short</height> </person> <person> <name> <givenName>name3</givenName> <familyName>lname3</familyName> </name> <age>30</age> <height>medium</height> </person> </people>'
declare @data xml set @data = (select * from openrowset(bulk 'c:\path\data.xml', single_blob) as x)
for $p in doc("data.xml")/people/person
where $p/age > 30
return $p/name/givenName/text() SELECT @data.query('
for $p in /people/person
where $p/age > 30
return $p/name/givenName/text()
') SELECT @data.value('/people/person/age', 'int') XQuery [value()]: 'value()' requires a singleton (or empty sequence), found operand of type 'xdt:untypedAtomic *'
SELECT @data.value('(/people/person/age)[1]', 'int') Infer.exe people.xml -o schema.xsd
<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="people">
<xs:complexType>
<xs:sequence>
<xs:element maxOccurs="unbounded" name="person">
<xs:complexType>
<xs:sequence>
<xs:element name="name">
<xs:complexType>
<xs:sequence>
<xs:element name="givenName" type="xs:string" />
<xs:element name="familyName" type="xs:string" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="age" type="xs:unsignedByte" />
<xs:element name="height" type="xs:string" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema> declare @schema xml set @schema = (select * from openrowset(bulk 'c:\path\schema_1.xsd', single_blob) as x)
CREATE XML SCHEMA COLLECTION poeple_xsd AS @schema
DECLARE @data XML(poeple_xsd) SET @data = 'مانند قبل با همان محتوایی که در ابتدای بحث عنوان شد'
SELECT @data.value('/people/person[1]/age', 'int') XQuery [value()]: 'value()' requires a singleton (or empty sequence), found operand of type 'xs:unsignedByte *'
DECLARE @data XML(document poeple_xsd)
DECLARE @x XML SET @x='' SELECT @x.query( ' 1,2 (: 1,2 :) ')
DECLARE @x XML SET @x='' SELECT @x.query( ' for $x in (1,2,3) for $y in (4,5) return ($x,$y) ')
DECLARE @x XML SET @x='' SELECT @x.query( ' 1, <node/> ')
XQuery [query()]: Heterogeneous sequences are not allowed: found 'xs:integer' and 'element(node,xdt:untyped)'
If you’re dealing with Unicode strings in your application, you need to take into account that characters could be represented in multiple ways.
The creator of C++, Bjarne Stroustrup, shares some valuable life advice that, let’s face it, all developers, no matter their years of experience could use. According to Bjarne, ‘You can’t just do code’, you need to develop more skills if you want to be a well-rounded successful developer. Watch this unreleased interview if you want some inspiration and guidance on your developer journey from one of the OGs.
how WebAssembly is evolving to be more than something that is run on web browsers. With WASI, you can run any app that is compiled into a .wasm binary on any host.
once the non LTS is installed you end up with 16.10 which has installed some newer versions of required libraries, namely something called libicu which is now on 57 instead of a required 55.
