Android:多语言对应

我们建好一个android 的项目后,默认的res下面 有layout、values、drawable等目录

这些都是程序默认的资源文件目录,如果要实现多语言版本的话,我们就要添加要实现语言的对应的资源文件。

首先我们点击添加Android Xml File按钮,会出现下面的界面:

image

输入文件名:string.xml,选中Values单选框,并把下面左列表中的Region添加到左边的列表里面,并在Region输入框里输入cn,如下图

image

这时,上面的消息提示:如果用Region的话,需要使用语言项,和Region一样,我们把Language也添加到右面的列表里面,填入zh,如下图

image

点击Finish按钮,资源文件就会建好了,目录:res\values-zh-rCN(其实上面一大堆操作,就是为生成这个目录

image

默认生成的string.xml的代码:

修改刚刚生成的res\values-zh-rCN目录下的string.xml:

运行结果:

en-us:英文

imageimage

zh-cn:中国大陆

imageimageimage

zh-tw:台湾

imageimageimage

因为设置了region为CN,所以zh-tw的时候,没有找到res\values-zh-rTW的目录,加载了默认的res\values目录下的string.xml

这里只用了Values做例子,其余的Resource都可以,图片了,布局了等等

这里只是简单的介绍了一下多语言对应,剩下的大家自己深入研究吧!

Ubuntu 下面清理无效内核的 脚本

Ubuntu 下面的内核经常升级,一段时间以后就很多了,浪费空间,网上搜索了一个脚本,用了下,感觉还可以。

原文是指定的Shell #!/bin/sh, 这个在Ubuntu下面是不能编译通过的,要要手动指定为bash 才行,主要是默认的sh不同造成的,不是什么大问题.

文件暂时命名成 Linux_Clean.sh吧

首先赋予执行权限

尝试执行

如果没有错误则执行

建议执行脚本之前执行

看看自己有多少Linux内核

执行完成后继续执行

估计会很有成就感的

下面是脚本原文,复制黏贴即可

Eclipse调试应用的时候显示Android源代码

在用Eclipse 调试程序的时候,一旦发生异常,往往在回退栈里面提示找不到源代码.

如下图所示

网 上搜索了一下,发现一个 fix_android_sdk.py 脚本,可以提取完整的java 文件到SDK 目录,尝试了一下,还是蛮有用的,可惜就是源代码只能看,不能设置断点。这个是用来编译ASE的一个脚本,里面的部分涉及到ASE的部分我们是用不到,并 且也没法用的,所以被我万恶的删除了。

1.首先要下载完整的Android源代码,建议下载一下,说不定哪天就用上了。

对 于以前的脚本进行了修改,然后现在可以判断当前的Android 的源代码版本了,如果定义过 "ANDROID_SDK_ROOT"环境变量的话,会使用环境变量中的值拷贝到制定的目录,比如Android 4.1.2 的源代码,现在可以拷贝到 Android-16 目录下面了,不需要再从android-1.5 下面拷贝出来了。 下面贴上最新的源代码脚本,供各位参考。

Linux下编写sh脚本 提示 “not a valid identifier”

编写了一个编译Android 的sh ,执行的适合 提示 "not a valid identifier" ,看了很久也没琢磨明白怎么回事,Google了一阵子才注意到 如下内容

当 在shell编辑脚本时,运行时出现了" ‘: not a valid identifier ",或者会出现(: command not found,许多莫名其妙的符号)很可能你在windows下编辑,在Linux下运行,由于Linux和windows的文本格式不同所导致的。

上面可能是反应之一,有时终端显示" :没有文件…"也是这个原因造成的 大部分由分号开头":"
解决方法:只要用UltraEdit工具转换成Linux格式,重新source运行无错误即可
Linux和windows的文本的区别:

1.Linux的换行:    "n"
2.windows的换行: "rn"(回车,换行)

尽管我没有在Widows下面编译,但是却使用了wine下面的记事本编写,结果自然不用讲了。

简单解决方法 vim 新建一个文件,原文件内容粘贴过去就可以了。

Windows 7 x64 调试 ASP ,"Microsoft.Jet.OLEDB.4.0“ 返回 3706 错误代码

尝试在Windows 7 x64 调试 Z-Blog ,结果总是报告数据库链接错误,跟踪了一下,返回错误代码  3706 ,有些莫名奇妙,网上大多说是没有安装 Jet 引擎导致。按理说,系统应该自带了,Google 了一番,发现是由于"Microsoft.Jet.OLEDB.4.0“是 32位的驱动导致的。

进行如下设置即可解决问题

  • For Windows 2008: Navigate to Server Manager > Roles > Web Server (IIS) > Internet Information Services (IIS) Manager, then look under your machine name > Application Pool.
  • For Windows 7: Navigate to Programs > Administrative Tools > Internet Information Services (IIS) Manager, then look under your machine name > Application Pool.

Express ASP error 0131 - "Disallowed Parent Path" (不能用“..”表示父目录)

提示一下,如果要调试 ASP ,IIS  Express 功能似乎有些不足,配置了半天,就是不能设置断点,最后直接用 Windows 7 x64 的IIS,直接附加进程就可以调试了,具体原因未知。

VS2012 使用 IIS 7.5 Express 调试 ASP 时候 显示 error 0131 - "Disallowed Parent Path" (不能用“..”表示父目录)

这个问题是微软为了规避可能的文件访问异常而屏蔽了".." ,默认是不支持父路径访问的。但是在实际中我们又不可避免的会用到,因为确实比较方便。

用记事本打开"我的文档\IISExpress\config\applicationhost.config",找到如下内容:

修改为:


还有其他的设置选项,提供参考

Android 编译环境设置,赶紧黏贴下来,免得被墙

原始网站https://source.android.com/source/initializing.html强调一下,该设置适用于SDK ,可以避免很多莫名其妙的问题。

Initializing a Build Environment

The "Getting Started" section describes how to set up your local work environment, how to use Repo to get the Android files, and how to build the files on your machine.  To build the Android source files, you will need to use Linux or Mac OS. Building under Windows is not currently supported.

Note: The source download is approximately 8.5GB in size.You will need over 30GB free to complete a single build, andup to 100GB (or more) for a full set of builds.

For an overview of the entire code-review and code-update process, see Life of a Patch.

Choosing a Branch

Some of the requirements for your build environment are determined by whichversion of the source code you plan to compile. SeeBuild Numbers for a full listing of branches you maychoose from. You may also choose to download and build the latest source code(called "master"), in which case you will simply omit the branch specificationwhen you initialize the repository.

Once you have selected a branch, follow the appropriate instructions below toset up your build environment.

Setting up a Linux build environment

These instructions apply to all branches, including master.

The Android build is routinely tested in house on recent versions ofUbuntu LTS (10.04), but most distributions should have the requiredbuild tools available. Reports of successes or failures on otherdistributions are welcome.

For Gingerbread (2.3.x) and newer versions, including the masterbranch, a 64-bit environment is required. Older versions can becompiled on 32-bit systems.

Note: It is also possible to build Android in a virtual machine.If you are running Linux in a virtual machine, you will need atleast 16GB of RAM/swap and 30GB or more of disk space in order tobuild the Android tree.

Detailed instructions for Ubuntu and MacOS follow. In general you will need:

  • Python 2.5 -- 2.7, which you can download from python.org.
  • GNU Make 3.81 -- 3.82, which you can download from gnu.org,
  • JDK 6 if you wish to build Gingerbread or newer; JDK 5 for Froyo or older.  You can download both from java.sun.com.
  • Git 1.7 or newer. You can find it at git-scm.com.

Installing the JDK

The Sun JDK is no longer in Ubuntu's main package repository.  In order to download it, you need to add the appropriate repository and indicate to the system which JDK should be used.

Java 6: for Gingerbread and newer

注意,该网址已经失效

更改为

即可

Java 5: for Froyo and older

Note: The lunch command in the build step will ensure that the Sun JDK isused instead of any previously installed JDK.

Installing required packages (Ubuntu 10.04 -- 11.10)

You will need a 64-bit version of Ubuntu.  Ubuntu 10.04 is recommended.Building using a newer version of Ubuntu is currently only experimentallysupported and is not guaranteed to work on branches other than master.

On Ubuntu 10.10:

On Ubuntu 11.10:

Installing required packages (Ubuntu 12.04)

Building on Ubuntu 12.04 is currently only experimentally supported and is notguaranteed to work on branches other than master.

Configuring USB Access

Under GNU/linux systems (and specifically under Ubuntu systems),regular users can't directly access USB devices by default. Thesystem needs to be configured to allow such access.

The recommended approach is to create a file/etc/udev/rules.d/51-android.rules (as the root user) and to copythe following lines in it. must be replaced by theactual username of the user who is authorized to access the phonesover USB.

Those new rules take effect the next time a device is plugged in.It might therefore be necessary to unplug the device and plug itback into the computer.

This is known to work on both Ubuntu Hardy Heron (8.04.x LTS) andLucid Lynx (10.04.x LTS). Other versions of Ubuntu or othervariants of GNU/linux might require different configurations.

Setting up ccache

You can optionally tell the build to use the ccache compilation tool.Ccache acts as a compiler cache that can be used to speed-up rebuilds.This works very well if you do "make clean" often, or if you frequentlyswitch between different build products.

Put the following in your .bashrc or equivalent.

By default the cache will be stored in ~/.ccache.If your home directory is on NFS or some other non-local filesystem,you will want to specify the directory in your .bashrc as well.

The suggested cache size is 50-100GB.You will need to run the following command once you have downloadedthe source code.

This setting is stored in the CCACHE_DIR and is persistent.

Using a separate output directory

By default, the output of each build is stored in the out/subdirectory of the matching source tree.

On some machines with multiple storage devices, builds arefaster when storing the source files and the output onseparate volumes. For additional performance, the outputcan be stored on a filesystem optimized for speed insteadof crash robustness, since all files can be re-generatedin case of filesystem corruption.

To set this up, export the OUT_DIR_COMMON_BASE variableto point to the location where your output directorieswill be stored.

The output directory for each separate source tree will benamed after the directory holding the source tree.

For instance, if you have source trees as /source/master1and /source/master2 and OUT_DIR_COMMON_BASE is set to/output, the output directories will be /output/master1and /output/master2.

It's important in that case to not have multiple sourcetrees stored in directories that have the same name,as those would end up sharing an output directory, withunpredictable results.

This is only supported on Jelly Bean (4.1) and newer,including the master branch.

Setting up a Mac OS X build environment

In a default installation, OS X runs on a case-preserving but case-insensitivefilesystem. This type of filesystem is not supported by git and will cause somegit commands (such as "git status") to behave abnormally. Because of this, werecommend that you always work with the AOSP source files on a case-sensitivefilesystem. This can be done fairly easily using a disk image, discussed below.

Once the proper filesystem is available, building the master branch in a modernOS X environment is very straightforward. Earlier branches, including ICS,require some additional tools and SDKs.

Creating a case-sensitive disk image

You can create a case-sensitive filesystem within your existing OS X environmentusing a disk image. To create the image, launch DiskUtility and select "New Image".  A size of 25GB is the minimum tocomplete the build, larger numbers are more future-proof. Using sparse imagessaves space while allowing to grow later as the need arises. Be sure to select"case sensitive, journaled" as the volume format.

You can also create it from a shell with the following command:

This will create a .dmg (or possibly a .dmg.sparsefile) file which, once mounted, acts as a drive with the required formatting for Android development. For a disk image named "android.dmg" stored in your home directory, you can add the following to your ~/.bash_profile to mount the image when you execute "mountAndroid":

Once mounted, you'll do all your work in the "android" volume. You can eject it (unmount it) just like you would with an external drive.

Master branch

To build the latest source in a Mac OS environment, you will need an Intel/x86machine running MacOS 10.6 (Snow Leopard) or MacOS 10.7 (Lion), along with Xcode4.2 (Apple's Developer Tools). Although Lion does not come with a JDK, it shouldinstall automatically when you attempt to build the source.

The remaining sections for Mac OS X only apply to those who wish to buildearlier branches.

Branch 4.0.x and all earlier branches

To build android-4.0.x and earlier branches in a Mac OS environment, you need anIntel/x86 machine running MacOS 10.5 (Leopard) or MacOS 10.6 (Snow Leopard). Youwill need the MacOS 10.5 SDK.

Installing required packages

  • Install Xcode from the Apple developer site.We recommend version 3.1.4 or newer, i.e. gcc 4.2.Version 4.x could cause difficulties.If you are not already registered as an Apple developer, you will have tocreate an Apple ID in order to download.
  • Install MacPorts from macports.org.Note: Make sure that /opt/local/bin appears in your path BEFORE /usr/bin.  If not, add

    to your ~/.bash_profile.

  • Get make, git, and GPG packages from MacPorts:

    If using Mac OS 10.4, also install bison:

Reverting from make 3.82

For versions of Android before ICS, there is a bug in gmake 3.82 that prevents android from building.  You can install version 3.81 using MacPorts by taking the following steps:

  • Edit /opt/local/etc/macports/sources.conf and add a line that says

    above the rsync line.  Then create this directory:

  • In the new dports directory, run

  • Create a port index for your new local repository:

  • Finally, install the old version of gmake with

Setting a file descriptor limit

On MacOS the default limit on the number of simultaneous file descriptors open is too low and a highly parallel build process may exceed this limit.

To increase the cap, add the following lines to your ~/.bash_profile:

Ubuntu 12.04 Android SDK Failed to create sdcard in the AVD folder.

比较早期的 SDK 的话,tools 目录是没有执行权限会导致问题,最新安装的不会出现问题的。那关键就是 64位系统不不能运行32位程序的缘故了。

1.对于 64位的 Ubuntu 如果没有安装ia32-libs,在64位下是不能跑32位程序的。使用

2.没有创建一个avd的话,eclipse是不会自动生成R.java的,新建了一个avd之后就会自动生成R.java

3.如果还是不行的话,设置android sdk下的tools权限为可执行权限。

Ubuntu 12.04 Dash 下面当弹出菜单出现时候,截屏不能用的解决方法

Ubuntu 12.04  Dash 下面当弹出菜单出现适合,截屏是不能使用的。

比如此种情况

当这个菜单弹出的时候,灾难就发生了。

据说是一个很古老的BUG 了,没办法只好想办法规避。

在Dash 下面输入 SC 应该能把 Screenshot调出来。这个Screenshot 竟然不能抓取自己的窗口,悲剧啊。

选择里面的"抓取前的延迟" 设置一个延迟时间,就可以了。到时候截屏出现整个屏幕再分割吧。

不过 Screenshot 自己的屏幕怎么抓取,实在是研究不出来。

Ubuntu 12.04 下共享网络给 MAC Mini

淘宝淘到的二手 Mac min中的某快无线网卡天线在拆解的时候被弄坏了,导致无线信号超级不好,只能通过另一台笔记本的有线来共享上网了。

满以为设置会很复杂,结果没想到超级的简单。

点击那个网络图标

弹出菜单

选中编辑连接

选中“编辑” 弹出

选中其中的 IPV4设置,在"方法(M)"中选中 “与其它计算机共享”

搞定。