WINDOWS PHONE风格PPT模板
浅褐色iOS苹果风PPT模板
你的标题
修改您的内容修改您的内容修改您的内容修改您的内容 修改您的内容修改您的内容 修改您的内容修改您的内容修改您的内容修改您的内容
请输入你的标题
请输入你的标题
修改您的内容修改您的内容修改您的内容修改您的内容修改您的内容修改您的内容 修改您的内容修改您的内容修改您的内容修改您的内容修改您的内容修改您的内容 修改您的内容修改您的内容修改您的内容修改您的内容修改您的内容修改您的内容
• 修改您的内容修改您的内容修改您的内容修改您的内容修改您的内 容修改您的内容
• 修改您的内容修改您的内容修改您的内容修改 您的内容修改您的内容修改您的内容
• 修改您的内容修改您的内容修改您的内容修改 您的内容修改您的内容修改您的内容
04
请输入你的标题
这里输入简单的文字概述这里输入简单字概述这里输入简单简单的文字概述这里输 入简单的文字概述简单的文字概述这里输入简单的文字概述这里输的文字概述这里
你的标题
修改您的内容修改您的内容修改 您的内容修改您的内容修改您的 内容修改您的内容
请输入你的标题
修改您的内容修改您的内容修改 您的内容修改您的内容修改您的
内容修改您的内容
01
修改您的内容修改您的内容修改您的内容修改 您的内容修改您的内容修改您的内容
02
05
修改您的内容修改您的内容修改您的内容修改 您的内容修改您的内容修改您的内容
输入简单的文字概述简单的文字概述这里输入简单的文字概
请输入你的标题
请输入你的副标题
修改您的内容修改您的内容修改您的内容修改您的 内容修改您的内容修改您的内容 修改您的内容修改您的内容修改您的内容修改您的 内容修改您的内容修改您的内容 修改您的内容修改您的内容修改您的内容修改您的 内容修改您的内容修改您的内容 修改您的内容修改您的内容修改您的内容修改您的 内容修改您的内容修改您的内容
第7章 Windows Phone设计元素和应用实战
Windows Phone 设计原则
第 7 章 Windows Phone 设计元素和应用实战
Windows Phone 界面框架
页面标题
尽管页面标题不是一个交互性的控件，但仍然有特定的 设计规范。页面标题的主要功能是用来清晰地显示页面内容 的信息，如果选择显示标题，那么应该在程序的每个页面中 都保留相同的标题位置， 这可以保持用户体验的一致性。
第 7 章 Windows Phone 设计元素和应用实战
Windows Phone 界面框架
进度指示器
进度指示器显示了程序内正在进行的与某一动作或事件 相关的执行情况，例如下载。进度指示器被整合进了状态栏， 可以在程序的任何页面显示。Windows 应用包括不确定进 度栏、进度环以及确定进度栏。
第 7 章 Windows Phone 设计元素和应用实战
Windows Phone 标准控件
搜索
搜索是用户可以在应用中查找内容的最常用方法之一， 本文中的指南介绍搜索体验、搜索范围和实现的要素，以及 在上下文中搜索的示例。 1.输入：文本是最常见的搜索输入模式，其他常见的输入 模式包括语音和相机。 2.零输入：在用户已激活输入字段之后却未输入文本之前， 可以显示所谓的“零输入画布”。零输入画布通常显示在应 用画布中，以便自动建议在用户开始输入查询时替换此内容。 3.查询规范化/ 自动建议：只要用户开始输入，查询规范 化便开始替换零输入内容。当用户输入查询字符串时，系统 将为他们提供一组不断更新的查询建议或消除歧义选项。
第 7 章 Windows Phone 设计元素和应用实战
Windows Phone 系统特点
通用Windows 应用史
通用 Windows 应用是一种基于通用 Windows 平台 (UWP) 构建的 Windows 体验，它首次作为 Windows 运行 时在 Windows 8 中引入。用户希望其体验在所有设备上均 为移动版，并且希望使用现有的最方便或最高效的设备完成 任务，此理念是通用 Windows 应用的核心。 通过 Windows 10，可以更加轻松地为UWP 开发应用， 并且只需一个API 集、一个应用包和一个应用商店，即可访 问所有 Windows 10 设备，包括PC、平板电脑和手机等。 对许多屏幕大小以及各种交互模型的支持也更加轻松。
PPT模板-win8风格-ISO-清新简约-30页
此处添加详细文本描述，建议与标题相 关并符合整体语言风格，语言描述尽量 简洁生动。
此处添加详细文本描述，建议与标题相 关并符合整体语言风格，语言描述尽量 简洁生动。
此处添加详细文本描述，建议与标题相 关并符合整体语言风格，语言描述尽量 简洁生动。
添加标题
此处添加详细文本描述，建议与标题 相关并符合整体语言风格，语言描述 尽量简洁生动。
添加标题
此处添加详细文本描述，建议与标题 相关并符合整体语言风格，语言描述 尽量简洁生动。
添加标题
此处添加详细文本描述，建议与标题 相关并符合整体语言风格，语言描述 尽量简洁生动。
添加标题
此处添加详细文本描述，建议与标题相关 并符合整体语言风格，语言描述尽量简洁 生动。尽量将每页幻灯片的字数控制在200 字以内，据统计每页幻灯片的最好控制在5 分钟之内。
此处添加详细文本描述，建议与标题相关 并符合整体语言风格，语言描述尽量简洁 生动。尽量将每页幻灯片的字数控制在200
字以内。
添加标题
此处添加详细文本描述，建议与标题相关 并符合整体语言风格，语言描述尽量简洁 生动。尽量将每页幻灯片的字数控制在200
字以内。
添加标题
此处添加详细文本描述，建议与标题相 关并符合整体语言风格，语言描述尽量 简洁生动。
此处添加详细文本描述，建议与标题相关 并符合整体语言风格，语言描述尽量简洁 生动。尽量将每页幻灯片的字数控制在200 字以内。
此处添加详细文本描述，建议与标题相关 并符合整体语言风格，语言描述尽量简洁 生动。尽量将每页幻灯片的字数控制在200 字以内。
添加标题
此处添加详细文本描述，建议与标题 相关并符合整体语言风格，语言描述 尽量简洁生动。
Windows Phone 7设计模板
Windows Phone 7设计模板Contents应用程序面板和应用程序菜单(application bar ＆ application menu) (2)按钮(buttons) (3)复选框(check box) (6)上下文菜单(context menu) (7)日期选择按钮(date picker) (8)对话框(dialog boxes) (9)编辑框控件(editor control) (11)硬件(hardware) (11)图标(icons) (12)键盘和输入(keyboard & input) (13)列表选择框(list picker) (15)列表控件(list view) (15)全景控件(panorama) (17)全景背景(panorama backgrounds) (17)选择框(picker box) (18)枢轴控件(pivot control) (19)进度指示器(progress indicators) (19)快速跳转网格(quick jump grid) (21)单选按钮(radio button) (22)提示器(reminders) (23)滑动条(slider) (23)开始界面和应用列表(start & app list) (24)启动瓷砖(start tiles) (25)状态栏(status bar) (26)主题(theme) (27)时间选择控件(time picker) (28)土司通知(toast notifications) (29)开关(toggle switch) (30)应用程序面板和应用程序菜单(application bar ＆ application menu)应用程序面板为改进大多数普通任务和应用程序视图提供了一个地方。
至少对于普通任务，应用程序可以包含一个单独的菜单，该菜单可以用于启动该应用。
应用程序菜单不是必须的，但如果你的应用使用了一个菜单，该菜单就必须和应用程序面板结合使用。
朦胧IOS风格商务办公通用PPT模板
单击此处添加标题单 击此处添加标题单
单击此处添加标题单击此处添加标题单击此 单击此处添加标题单击此处添加标题单击此 单击此处添加标题单击此处添加标题单击此 单击此处添加标题单击此处添加标题单击此 单击此处添加标题单击此处添加标题单击此 单击此处添加标题单击此处添加标题单击此 单击此处添加标题单击此处添加标题单击此
单击此处添加标题
第一
单击此处可编辑内容，根据您的需要自由拉伸文本框大小单 击此处可编辑内容，根据您的需要自由拉伸文本框大小单击 此处可编辑内容
第二
第三
单击此处添加标题
taxt
taxt
taxt
taxt
单击此处添加标题单击此处添加标题单击此单击此处添 加标题单击此处添加标题单击此单击此处添加标题单击
关键词
单击此处添加标题单击此处添加 标题单击此处添加
单击此处添加标题
单击此处添加
单击此处添加标题单击此处添加标题单击 此处添加单击此处添加标题单击此处添加 标题单击此处添加单击此处添加标题单击 此处添加标题单击此处添加单击此处添加 标题单击此处添加标题单击此
单击此处添加标题单击此处添加标题单击此 单击此处添加标题单击此处添加标题单击此 单击此处添加标题单击此处添加标题单击此 单击此处添加标题单击此处添加标题单击此
单击此处添加标题
单击此处可编辑内容，根据您的需要自 由拉伸文本框大小单击此处可编辑内容， 根据您的需要自由拉伸文本框大小单击 此处可编辑内容
ADD YOUR TEXT
单击此处可编辑内容， 根据您的需
单击此处可编辑内容，根 据您的需要自由拉伸文本 框大小单击此处
单击此处添加标题
单击此处可编辑内 容，根据您的
小清新唯美碎花ios风个人简历ppt模板
在此YTRYSDGVFSDG描述说明， YTRYSDGVFSDG描述说明上述图表的 描述
添加标题
输入文字标题
添加标题
在此YTRYSDGVFSDG描述说明， YTRYSDGVFSDG描述说明上述图表的 描述
添加标题
在此YTRYSDGVFSDG描述说明， YTRYSDGVFSDG描述说明上述图表的 描述
简约清新时尚个人简历
||述职报告||个人简历||工作总结||岗位竞聘||
CONTRACTED WIND POWERPOINT TEMPLATE DESIGNS CONTRACTED WIND ERPOINT TE DESIGNS CONTRACTED WIND POWERPOINT TEMPLATE DESIGNS CONTRACTED WIN
远见力 决策力
个人素质
感召力 创新力
在持续长期发展过程中，继承优良传统，适应 时代要求，由企业家积极倡导，全体员工自觉 实践，从而形成的代表企业信念、激发企业活 力、推动企业生产经营的团体精神和行为规范。 按照不同层次划分为精神文化型和组织制度型 两类。划分为精神文化型和组织制度型两类。
执行力
胜任能力
POWERPOINT TEMPLATE DESIGNS
目
summer
录
01、 02、 03、 04、
自我介绍 岗位认知 胜任能力 目标规划
01
自我介绍
基本信息 个人履历 荣誉与奖项
自我介绍
姓名: 小小 年龄: 28岁 体重: 48kg 政治面貌: 党员
性别: 女
民族: 汉 身高: 162cm 学历: 本科
在此YTRYSDGVFSDG综合描述说明，在此YTRYSDGVFSDG上述图表的综合描述说明入。在此 YTRYSDGVFSDG综合描述说明，在此YTRYSDGVFSDG上述图表的综合描述说明入。在此 YTRYSDGVFSDG综合描述说明，在此YTRYSDGVFSDG上述图表的综合描述说明入。
ppt模板素材 微软win8瓷片风格ppt图表
SSL VPN
Down-level Windows clients and mobile devices.
Access Strategy
Access to data depends on user, device and location
WHO
User Profile Compliance
WHERE
Proxi LOB applications Public Collaboration Mobility
Account Manager
Business value Collaboration needs LOB Applications Engagement with technology Mobility
Choose Your Own
White-listing devices Loose policies
Here is Your Own
Predefined Device Strict policies
Freedom Consumer of devices UN- MANAGED MANAGED Limited Loose policies Control
Many Types of Devices for IWs
Windows 8
Heterogeneous Devices
How do I meet my IT policies?
Access Strategy
CORPORATE NETWORK Windows 7/8
RRAS VPN
Myriad mobile devices
Compliancy Enterprise enablement
Embrace Bring Your Own Device
设计原汁原味的Windows Phone应用
USA Today中对于全景视图的使用全景视图设计上类似于Windows系统中的多窗口事件，每个窗口中打开的可以是不同的软件。
所以全景视图中可以放置文字、图片、瓦片等等所有可以承载的内容，每个页面中的内容、布局、甚至操作都可以有所不同，每个页面右侧露出的边沿恰恰构成了切换标签的最佳隐喻（见下图）。
这样的特性正好对应于iOS或者Android系统应用最为常见的一级导航，所以我们在设计Windows Phone应用时完全可以大胆的将这两个平台应用的一级架构直接移植过来。
Windows Phone的设计不太推荐一个页面中出现二级标签（也是可以支持的，但是那样就不够原生，不在本文讨论范围），这就需要设计时将内容尽量扁平化，在尽量少的层级内完成相关的操作，这一般是我们设计应用时比较花心思的地方。
全景视图中每个界面中放置的内容也可以有两种展示方式，纵向展示多用于内容较多或信息流类内容，纵向理论上可以“无限长”；横向展示多用于内容量及布局固定，希望一次性展示完毕的内容，其纵向不可操作，横向可做多屏拼接。
如下图，Xbox LIVE栏目使用的即为横向展示方式（覆盖区域为栏目范围，框选区域为一屏显示范围），其他栏目使用的是纵向展示方式。
全景视图中可以模拟主屏幕中的瓦片及动作效果，不过微软没有把1*2的长方形瓦片使用权限开放给开发者，对此我们可以使用自己绘制的方式进行效果模拟。
全景视图中不同界面内容及操作不同，则其对应的功能菜单肯定也有一些区别，解决这个问题可以在界面之间切换时设置一个操作菜单收起的动作，到下一界面再次展开时显示该界面对应的操作即可。
枢轴视图（Pivot）的正确使用枢轴视图设计上类似于Windows系统中的多任务事件，在一个软件中开启多个并列任务，每个任务。
Windowsphone风格ppt初稿
有 社 会 责
活 动
参 加 文 体
健 康 ，
生 活 积 极
团委 学生会 研究生会 家电义务维修小组 SPS美国大学生物理学生会 Torchwood物理学社 中山大学航空俱乐部
完成三步阶梯目标的 组织保证:
完整的组织架构
格物致知， 经世致用
学术
名家讲座
四大学术社团 分享会
学术竞赛指导讲座 （MCM，MATLAB等）
中山大学
2019 -
2019
共青团
年度 评优
物理科学Байду номын сангаас
&
工程技术 委员会
4
Monday
Calendar
People Weather
24°C
Guangzhou PRC Rainy
Call & Messaging WeChat
Music
Photo Chrome
Call & Messaging
物理科学与工程技术学院 在
欧洲核子中心 夏令营 交流会
“芙兰”物理节 海峡两岸科技文化
交流活动
创建学术性社 团
格物致知， 经世致用
公益
家电义务 维修小组
走进社工站 成立物理科学小组
社区 募捐书籍
“理工益” 班级特色公益活动
格物致知， 经世致用
文体
THANK YOU
共青团委员会
线
我们的理念
你好，我在做一份关于学生发展的 调查，想问你们一些问题？
嗯嗯，我们一直致力于帮助学生发 展为“格物致知，经世致用”的人。
让我给您简单介绍一下吧。
格
物
经 世
致 知
2023最新精品IOS风格PPT模板 (35)
在此处添加详细描述文本，尽量与标题文本语言风格相符合，语言描述尽量简洁生动，尽可能概括出段落内容。
单击添加标题
在此添加标题文字Add up your title
content
单击添加标题
单击此处添加标题
单击此处添加标题
单击此处添加标题
单击此处添加标题
单击此处添加标题
单击此处添加标题
单击此处添加标题
单击此处添加标题
单击添加标题
%
%
%
单击添加标题
单击添加标题
单击添加标题
单击添加标题
%
单击添加标题
单击添加标题
单击添加文本单击添加文本单击添加ห้องสมุดไป่ตู้本单击添加文本单击添加文本单击添加文本单击添加文本
单击添加标题
单击添加文本单击添加文本单击添加文本单击添加文本单击添加文本单击添加文本单击添加文本
X年工作总结模版
清小风
清风素材sc.taobao
目录
单击此处添加您的标题
单击此处添加您的标题
单击此处添加您的标题
单击此处添加您的标题
在此添加标题文字Add up your title
content
单击添加标题
.单击输入您的标题文字
.单击输入您的标题文字
.单击输入您的标题文字
单击输入标题文字
单击添加标题
%
其它费用
%
单击添加标题
在此添加标题文字Add up your title
content
单击添加标题
诚信铸就品质
创新引领未来
点击输入简要文字内容，文字内容需概括精炼，不用多余的文字修饰，言简意赅的说明分项内容。点击输入简要文字内容，文字内容需概括精炼，不用多余的文字修饰，言简意赅的说明分项内容…… 点击输入简要文字内容，文字内容需概括精炼，不用多余的文字修饰，言简意赅的说明分项内容……
微软Windows Phone风格指南（墨西哥语）说明书
WINDOWS PHONES TYLE GUIDE FOR H UNGARIANContents1.Goals of This Guide (3)2.The Windows Phone Voice (3)nguage-Specific Guidelines (4)3.1.General Tone & Voice—Share the Message (4)3.2.Style—Help Deliver the Voice (5)3.2.1.Product Names (5)age—Sound Natural (6)3.4.Terminology—Be Consistent (7)3.4.1.Naming Guidelines and Trademark Requirements (9)3.5.Handling Fictitious Content (9)3.6.Measurements (9)4.Windows Phone UI Localization Guidelines (10)4.1.How to Translate UI Elements (10)4.1.1.App Bar Icon (10)4.1.2.App List Item (11)4.1.3.Buttons (11)4.1.4.Check Box Label (13)4.1.5.Edit Box Label (13)4.1.6.Group Label (14)4.1.7.Hub Title (15)4.1.8.List Item in Settings (15)4.1.9.Menu Items (16)4.1.10.Message Box (17)4.1.11.Notification Toast (18)4.1.12.Page Title (19)4.1.13.Pane Section Title (19)4.1.14.Phone Control Label (20)4.1.15.Pivot Item (20)4.1.16.Progress Indicator Text (21)4.1.17.Text Box (21)4.1.18.Tile Label (22)4.1.19.Toggle Switch (22)4.2.How to Translate References to UI Elements (23)4.3.Text Overflow (24)4.4.Capitalization—Mind the Case (25)4.5.Words—Show as well as Tell (27)4.6.Punctuation—Divide and Conquer (28)4.7.Editing/Screen Review—Fine-Tune the Translation (28)4.8.Handling Input from External Stakeholders (29) (30)5.1.General (30)5.2.Terminology (30)5.3.Elements Specific to (31)5.3.1.Image Captions (31)5.3.2.Topic Titles (31)5.3.3.References to UI Elements (32)5.4.Sample Translations of Texts (33)5.4.1.Marketing Text (33)5.4.2.How-to Text (34)5.5.Fine-Tuning during Editing/Screen Review (35)1.Goals of This GuideThis document describes the tone, style and some specific translation instructions which should be used as reference during the Hungarian localization of Windows Phone and its documentation. Windows Phone is a unique project as regards tone, style and terminology usage. The main goal of this guide is to help the translator understand and learn how to deal with all its linguistic and stylistic nuances during localization.There are 4 main focus areas in this guide:1.Windows Phone Voicenguage-specific guidelines on tone, style and terminology3.UI-specific Localization Guidelines—e.g. capitalization, text overflow,punctuation4.UA-specific stylePlease note this style guide is intended to be the main stylistic reference for Windows Phone projects. It is also a live document— it may be updated at certain stages to make sure the examples reflect all the latest information and guidelines.2.The Windows Phone VoiceThe language related to Windows Phone should make consumers (users) feel that they are empowered and supported. Windows Phone should be perceived as genuine, spirited, balanced, and supportive:Genuine•Speak with confidence.•Be an experienced guide.•Be friendly, focusing on the customer’s needs.Spirited•Genuinely express your own enthusiasm.•Express the achievable and talk about the difference it makes.•Reveal the unexpected, the sparkle, the delight.•Express a pleasant, engaging rhythm.Balanced•Be an experienced concierge: personal, friendly, enthusiastic, attentive.•Know when to keep things light, when to get down to facts.•Keep the moment, the audience, and the message in mind.•Don’t overpromise—be quick, clear, concise.Supportive•Lend help where it's needed, when it's needed.•Convey your knowledge like a trusted friend.•Strive to put others at ease.•Frame things positively, with a friendly demeanor.nguage-Specific Guidelines3.1.General Tone & Voice—Share the MessageThe Windows Phone device targets a group of modern, career-oriented people who expect their mobile phone to meet their needs in both their professional and private lives.In order to appeal to this audience, use contemporary, up-to-date style and terminology, close to what people actually say in everyday settings rather than theformal, technical language that is often used for technical and commercial content. Avoid using overly colloquial language, and keep a professional tone instead.3.2.Style—Help Deliver the VoiceThe style is direct and personal.Address the user w ith the formal second person (“önözés”). The language used should sound natural.∙Use short sentences that are easier to read.∙Context comes first: screen design can influence word choice, sentence length, punctuation, etc.Structures in first person plural are mostly rendered impersonally in Hungarian. Avoid using the first person plural.Example:Avoid colloquialisms and slang expressions. The register should be neutral.“&” and “+”Strings containing the characters “&” or “+” appear frequently in the source text. The ampersand (“&”) should be translated with the conjunction “és” unless it is part of a company name or trademark (for example “AT&T”). The plus symbol (“+”) is part of the design language of the phone and also saves space, so it should be preserved in the translation. The plus sign should not be surrounded with spaces.3.2.1.Product NamesThe overall style used in Windows Phone can sound too academic and unnatural in Hungarian without applying suffixes to product names. Everyday language usage tends to suffix. Watchful product name suffixation makes the text more fluent, keeps it brief but to the point and avoids unnecessary paraphrasing. Do not, however, overuse it and make every product name suffixed—this will have an opposite effect; use a descriptor instead (see Microsoft Office Professional in the below table). Product name suffixes should also not be applied to explicit trademarks indicated by the ® and TM trademark signs. In such a case, apply a workaround and/or a descriptor.age—Sound NaturalDuring the localization of any Windows Phone components, keep the following general points in mind:∙Be direct—be straightforward and concise. Windows Phone should not be chatty or wordy and redundancy should be avoided.∙Be accurate but not over-exhaustive, as it might harm legibility.∙Be calm, professional, friendly, and honest.∙Avoid slang and be careful with colloquialisms.∙Make sure explanations are pleasant to read.∙Make the complicated uncomplicated without oversimplifying: focus on essentials.3.4.Terminology—Be ConsistentUse terminological options which are easy to understand, up-to-date and in line with the terminology used by competitors. The focus should not be on following Microsoft standard terminology, but rather on researching and identifying those terms most widely used within the mobile industry of your target country.Always refer to the Windows Phone terminology as priority no. 1. Please note that approved translations for Windows Phone key terms are to be found in the Windows Phone MultiTerm database.When translating Windows Phone for Office applications such as presentations, e-mails, spreadsheets, etc., aim for consistency with current Office applications in order to give the user a consistent experience. Please pay special attention to Excelformulas and functions—verify their translation in the latest localized version of Excel and/or in TRES.Microsoft standard terminology should be used in conjunction with other Microsoft products (Xbox, Internet Explorer, etc.) as secondary source of reference. As part of your terminology research, always check what is used in other products in TRES and TermStudio.If needed, please provide feedback on Windows Phone terminology you feel is incorrect (but please do not attempt to change approved terminology before receiving confirmation from the project team).Also contact the project team if you come across a new app, product or feature name that is not included as part of the Windows Phone terminology. Product names are normally not translated (e.g. Windows Phone). Feature names can usually be translated (e.g. Kid’s Corne r, voicemail)—even though there may be some exceptions of features that need to stay in English. In any case, it is extremely important to always confirm localizability of any such items with the project team.3.4.1.Naming Guidelines and Trademark RequirementsPlease follow Windows Phone Naming Guideline and Trademark Requirements provided separately.3.5.Handling Fictitious ContentFictitious content is legally sensitive material and as such cannot be handled as a pure localization issue. When dealing with fictitious company and people names in Windows Phone, please use the list of legally approved names provided by the Microsoft Legal department (LCA). The Windows Phone product team representative will be able to provide you with the list of legally approved names managed by LCA.*******************The domain name should be left unlocalized, as it is a globally recognized domain created by the IANA (Internet Corporation for Assigned Names and Numbers) for sample purposes. “Someone” can be replaced with a first name from the Approved People Name list or any common name in the country. For Hungarian, please replace ******************* with ******************.3.6.MeasurementsThe EN US source contains measurements in strings such as:Regardless of the spacing in source, please add a blank space between the value (a placeholder like “%s” in the examples above) and the unit of measurement in the translation. Please note that while the source is inconsistent in this regard, thetranslation should always have a space between a number and a unit of measurement.The unit “KB” (kilobyte) should be translated as “KB”, keeping the letter “K” in uppercase.4.Windows Phone UI Localization Guidelines4.1.How to Translate UI Elements4.1.3.Buttons4.1.3.2.Push ButtonRadio Button4.1.3.3.4.1.5.Edit Box Label4.1.6.Group Label4.1.7.Hub Title4.1.8.List Item in Settings4.1.9.Menu Items4.1.9.1. Application Menu Item4.1.9.2.Context Menu Item4.1.10. Message Box4.1.10.1. Message Box Body4.1.10.2. Message Box Header4.1.11. Notification Toast4.1.13. Pane Section Title4.1.14. Phone Control Label4.1.15. Pivot Item4.1.16. Progress Indicator Text4.1.17. Text Box4.1.18. Tile Label4.1.19.1. Toggle Switch Label4.1.19.2.Toggle Switch TitleNote: Target capitalization follows source capitalization style. For more information on Windows Phone capitalization style, see Capitalization—Mind the Case.4.2.How to Translate References to UI ElementsReferences to UI elements within the UI can be found in error messages, task messages, etc. It is important to have a consistent approach towards the localization of such references. References to UI elements can appear in examples such as the below.Example:SourceTry another ID, or tap Show Available IDs to see some suggestions.DescriptionThe string above makes a reference to the “Show available IDs“ UI option. In the EN US source, UI options are usually in all lowercase when appearing on their own; however, when there is a direct reference to these elements in UI messages, English does not use lowercase, but title casing instead, i.e. the first letter of each word is capitalized. This is why in the source example above “Show Available IDs“ appears in title casing.Translation StrategyFor Hungarian, references to UI elements within UI strings should be translated using Sentence case. As a result, the translation of the source string in the example above would be as follows.TranslationAdjon meg egy másikat, vagy a Választható azonosítók megjelenítése elemre koppintva tekintse meg a javaslatokat.4.3.Text OverflowIn some screens, the text flows out of the screen. This is part of the UI design. Whether text is allowed to flow out of the screen or not depends on where it appears and what type of control it is.For example, some text that is not part of the user interface (generated by a user or coming from an external server) can overflow out of the screen.Titles that come from a previous screen (like the ones from the Settings page) and run out of the screen can be truncated—even if the text is not understandable. That is the behavior in the source UI.Example:Control—Label with Title1Style4.4.Capitalization—Mind the CaseWindows Phone showcases a very specific capitalization style—Hungarian follows the source in this respect. What follows is a summary of this Windows Phone-specific capitalization style.Lowercase:Lowercase notation is preserved in the translation in order to follow the original marketing design.Lowercase is used in the following user interface (UI) elements:∙link controls (also called inline links; links that are within a set of content)∙phone control labelsExceptions:∙If you have a branded name, use the appropriate capitalization.∙Proper nouns are excluded from this rule and should follow the appropriate capitalization.Sentence case:Please always follow source capitalization when sentence case is applied.Title Case:The following UI elements appear in Title Case in source:∙Photo Album Titles∙Tiles, Hubs, Cards (Live Tiles, People Hub, Me Card)In Hungarian, only the first word in the album titles is capitalized, the following words are capitalized only if they are proper nouns or would normally be capitalized when appearing on their own in other contexts.∙Live Tiles = Live Tile csempék∙People Hub = Kapcsolatok központ∙Me Card = Én kártyaALL CAPS:ALL CAPS is used in source for the following UI elements:∙PAGE/APPLICATION TITLE∙DIALPAD LABELExample:To sum up, all the above product specific capitalization guidelines should be followed during translation into Hungarian.4.5.Words—Show as well as Tell∙To show simple and easy, use simple sentences and phrases, minimal text, and everyday words. Use the simplest and most specific words possible.∙Avoid the use of excessively long words as they can lead to truncations.∙Use language that customers use.∙Translate colloquial and conversational phrases in a friendly tone and style.∙Do not use jargon and/or slangy interjections, as they might sound inappropriate to the audience.∙Do not use too complicated and long compound words.∙Use one term for one concept, and use terms consistently.∙Avoid creating words or applying new meanings to common words.Be careful with:∙Overuse/redundancy∙“Ön”∙Using “Kérjük,...”∙Apologizing∙Overpromising4.6.Punctuation—Divide and ConquerThe Hungarian rules of punctuation considerably differ from those of English. The rules are described in A magyar helyesírás szabályai, Tizenegyedik kiadás, Akadémiai Kiadó, Budapest, 1985 and Helyesírás, Osiris Kiadó, Budapest, 2006 in detail.∙Do not use abbreviations with the exception of units of measurement.∙Do not use semicolons. Two shorter sentences are better and easier to read.∙Do not overuse exclamation points. Choose stronger words.4.7.Editing/Screen Review—Fine-Tune the TranslationScreen editing is a key step to detect any style, terminology or other linguistic inconsistencies or errors introduced during translation. Here are some important issues to look out for during your review:∙Strings that include redundant words. Unnecessary repetitions should be avoided.∙Too literal translations. The text needs to be naturally-sounding and appealing in the target language.∙Concordance. Translators are sometimes presented with standalone strings for translation. Often, some words are used in conjunction (concatenated) withdifferent words. Translating these standalone terms may easily lead toconcordance and accuracy issues (singular/plural and complex concatenatedstructures).∙Truncation. In some instances it will be necessary to shorten strings due to length restrictions in the graphical interface. Do not ever abbreviate words; it is preferable to reformulate the strings to shorten them. In some cases, it might be possible to leave out part of the string without losing the meaning. If this is not possible, contact the Product Team to discuss a possible solution.4.8.Handling Input from External StakeholdersAnalyze the feedback provided by mobile operators, Microsoft subsidiary contacts, and other relevant parties. If any changes are needed to be implemented in the product resulting from external stakeholder feedback (such as a terminology change or any other linguistic change), please discuss the changes with the Microsoft Project Manager first. After getting the approval, the reference material should be updated with the latest approved changes.Please explore the already published pages for Hungarian at the following location: /hu-HU.5.1.GeneralThe language used in is intended to make the user feel that this is a system they can depend on. The overall style should be perceived as sincere, enthusiastic, balanced and supportive. The text is intended to be casual and full of energy, with simple, easy-to-understand explanations.The rules concerning the general style and tone of the user interface also apply to the Windows Phone website. This contributes to a consistent look and feel perceived by any user working with the device and browsing the website.Please refer to The Windows Phone Voice section for more information about the individual rules.5.2.TerminologyThe same terminology used for translating the Windows Phone user interface must be applied in the Windows Phone website. UI options must be referenced precisely, as any mismatched terminology might confuse the user and make the website less coherent.To reiterate, please take into account the guidelines already provided in this section as regards vocabulary choices on this project.Also, please note that there is some key terminology specific to the component. Translations for these terms can be found in the Windows Phone MultiTerm database.Other aspects to take into account:Rigid term-to-term approach: Rework for fluency/adherence to basic guidelines of tone and voice. For high-visibility terms, always do a reality check—“Can that sound awkward or incorrect in Hungarian? Do people speak like that?” If needed, provide feedback on terminology that you consider incorrect.“Layers” of localization:The style tends to change when localization occurs in phases. Please refer to legacy or earlier translations for specific solutions or guidelines. Correct past mistakes and continue with good solutions. If the legacy translation is not up to the standard, disregard it. However, do not ever change approved terminology. Any inappropriate terminology should be flagged.5.3.Elements Specific to 5.3.1.Image CaptionsImage captions can be found in the text in the following structure:<hhtInlineImage href="/global/windowsphone/en-ww/PublishingImages/howto/wp7/inline/basic-icon-favorites.png" altText="Favorites icon"/>. Only the highlighted text is translatable:<hhtInlineImage href="/global/windowsphone/en-ww/PublishingImages/howto/wp7/inline/basic-icon-favorites.png" altText="Kedvencek ikon"/>.5.3.2.Topic TitlesIn English topic titles usually begin with "How to…" or with phrases such as "Working with…" or "Using…". In the Hungarian version, such flexibility is not possible. English tends to use different moods in titles (e.g. interrogative and imperative mood, infinitives, gerunds etc.). Please use a uniform, possibly non-verbal structure in most cases:5.3.3.References to UI ElementsIn , EN US Source uses sentence casing to indicate references to UI elements. For Hungarian, references to UI options should be localized using Sentence case.Examples:5.4.Sample Translations of TextsThe two sample translations included in this section illustrate the approach adopted for the localization of UA sites.5.4.1.Marketing TextTap+SendMegosztás összeérintéssel5.4.2.How-to TextPress the SearchWith the music playing, hold your phone where you can clearly hear the music, and then tap MusicNyomja meg telefonján a Keresés5.5.Fine-Tuning during Editing/Screen ReviewThe review stage—either on the file or the screen—is key to verify that the translation is accurate and adheres to the Windows Phone voice and style as well as the approved key terminology. When reviewing, please take particular care on the following linguistic aspects:∙All the main references have been followed, particularly as regards localization of Windows Phone and other related products UI options.∙Image captions and topic titles have been translated consistently.∙The text flows, is straight-forward and appealing to the reader.∙The style follows the agreed Windows Phone tone and voice staples into your language.∙The text is translated consistently. All Windows Phone and key terms have been localized as per approved glossary.。
windowsphone进入市场分析.ppt
2、Ios没有涉及中端市场，而且随着4S的发布证明它也没 有廉价IPHONE的计划，WP可以运用这个机会明确自己的 定位，做好系统优化，做在相同价位下的用户体验优于 android。
3、随着ios的普及，它在消费者心中的地位会下降，随着 地位下降，它低性价比得缺陷就会显现，最终用户会发 现，ios其实不比android windows phone好多少，最终消 费会趋于理性。
2、微软在电脑操作系统上的成功，使得微软有庞大的 用户基础，把电脑上优秀的软件，服务转移到移动设备上， 会形成一大特色。
Microsoft Office
1.拥有雄厚的软件开发实力，优秀的人才，先进的理念。
Internet Explorer
必应搜索（bing)
3、作为进入市场最早的手机操作系统开发者之一，拥有 大量专利，在自己的windows phone上运用这些专利的 同时，可以在适当时机用专利打击别的操作系统。
5 0 %+2 6% = 7 6%
20Байду номын сангаас1/1/11
2、应用软件上的劣势，WP7现有的手机应用软件有3万 多个，iOS应用为42.5万个，Android应用有25万个。
3、微软是一个庞大的公司，产品服务众多，除了电脑操 作系统，其他产品都给人一种不上不下的感觉，能否真 正把重心放在手机操作系统将决定WP的成败。
4、微软没有自己的硬件设备厂商，容易被硬件 合作商牵制。，
2021/1/11
1、android硬件大战，windows phone没有必要加入 。
2021/1/11
iphone 4s 双核 1 GHz 512MB 1430mAh 960*640 800万
8000