Search completed in 1.02 seconds.
Localizing with Mercurial
in mozilla, we use the the
mercurial version control system (hg) to manage our source code and localizations.
...
mercurial allows localizers to work locally (on their machines) and then push (an hg term) changes to a remote repository, which usually is hosted on the mozilla servers (hg.mozilla.org).
... localizing current versions of firefox, thunderbird and seamonkey includes working with
mercurial.
...And 27 more matches
Application Translation with Mercurial
configuring your
mercurial user settings still in the command prompt, go to your home directory in the file system, e.g.
... for a windows user, it looks like c:\users\myname , depending on your windows version: cd /c/users/myname now list all the files here: ls -a if there is no file called .hgrc , create it with > .hgrc this file stores your general
mercurial settings (
mercurial is the tool which manages the source code and its history of changes).
... enabling
mercurial queues (revertable patches) some time will pass between the moment in which you start the localization, finish it, test it, improve it, upload it for review and get review (maybe not approved on first try).
...And 7 more matches
Tamarin mercurial commit hook - Archive of obsolete content
it is highly recommended that all developers enable the
mercurial commit hook for tamarin.
... the hook is located in the tamarin-redux repository in the file utils/hooks/tamarin-commit-hook.py this is a simple
mercurial hook that checks the following filetypes ('.cpp', '.h', '.as', '.abs', '.py') for the following: tabs anywhere in the line trailing whitespace windows line endings (\r\n) "mark_security_change" - looks for this text and warns user as security changes should not be checked into the public tamarin-redux repository.
Localizing with Koala
requirements
mercurial, linux, windows or mac os x.
...koala will check for
mercurial.
... make sure that your
mercurial installation is in your system's $path.
...And 13 more matches
Release phase
we'll primarily focus on getting your release repository setup and the
mercurial commands you'll need to know to use that repository.
...your official release repository now that your locale has been registered, the localization files will live on mozilla
mercurial server at hg.mozilla.org.
...there are two different protocols you can use to connet with your
mercurial repository: http and ssh.
...And 5 more matches
Index
2 application translation with
mercurial android, draft, editing, firefox, lightning, localization,
mercurial, seamonkey, translate, patch, thunderbird first, get the required programs to compile mozilla applications like firefox and thunderbird from build instructions.
... 3 bootstrapping a new locale localization,
mercurial, translate, bit bucket (see also https://developer.mozilla.org/en/create_a_new_localization) 4 encodings for localization files internationalization, localization when creating a localization for mozilla products, it’s important to be aware of the encoding of the files that you generate.
...we'll primarily focus on getting your release repository setup and the
mercurial commands you'll need to know to use that repository.
...And 4 more matches
Localizing with Mozilla Translator
from cvs to
mercurial in mt so, you have a firefox product in mt with a platform neutral and, inside it, several directories (''components'' in mt terminology) more or less like the second sample above, checked out from cvs.
... the first thing to do, once you have your
mercurial local repository up and working, is create a new product...
...with
mercurial, partial checkouts are not possible, so you have your own mozilla repository full copy (there are alternate solutions; read on).
...And 3 more matches
MCD, Mission Control Desktop, AKA AutoConfig - Archive of obsolete content
c.php?t=276014 http://www.mozilla.org/community/dev...er-forums.html http://forums.mozillazine.org/viewto...config#2090731 http://forums.mozillazine.org/viewto...config#1354355 http://forums.mozillazine.org/viewto...toconfig#32783 related bugs bug 295329 bug 222973 bug 225288 bug 178685 bug 272970 bug 206294 bug 302096 bug 502597 bug 674261 thunderbird comm-central_source_code_(
mercurial) below is a method to build from sources in case some feature were missing in public packages based on bug 295329 , since tb 3.0.x autoconfig doesn't work anymore.
... according to the discussion in mozilla.dev.apps.thunderbird , change from cvs to
mercurial and recent changes to the nsldapurl code might have borken autoconfig .
... below we start to debug this by rebuilding a thunderbird from comm-central-source-code (
mercurial).
... build install
mercurial tools [root@b008-02 ~]# yum install
mercurial installed:
mercurial.i586 0:1.2.1-1.fc11 check merge tools in [root@b008-02 ~]# vim /etc/
mercurial/hgrc.d/mergetools.rc get the source comm-central [root@b008-02 moz]# time hg clone http://hg.mozilla.org/comm-central/ commsrc requesting all changes adding changesets adding manifests adding file changes added 2975 changesets with 16793 changes to 7117 files (+3 heads) updating working directory 5644 files updated, 0 files merged, 0 files removed, 0 files unresolved real 0m40.771s user 0m9.284s sys 0m1.304s [root@b008-02 commsrc]# python client.py checkout executing command: ['hg', 'pull', '-r', './.', '-r', 'tip'] pulling from http://hg.mozilla.org/comm-central/ searching for changes no changes found exe...
Tamarin build documentation - Archive of obsolete content
windows 32 and 64 bit mac osx 10.4, 10.5 on ppc mac osx 10.5, 10.6 on intel linux 32 and 64 bit solaris 10 on sparc android 2.2 on arm windows mobile 6.5 mips (linux) sh4 (linux) getting the tamarin source the tamarin source resides in
mercurial at tamarin central.
... use the following command to create a copy of the tamarin repository: $ hg clone http://hg.mozilla.org/tamarin-central tamarin-central tips for working with
mercurial can be found here.
...documentation on how to setup a user repository http://developer.mozilla.org/en/publishing_
mercurial_clones.
...
mercurial repository: give the location of the repository that will be used for the build.
Building Mozilla XForms - Archive of obsolete content
getting started things to know first: the xforms extension has a dependency on the schema-validation extension, so you need to build both (that's done automatically) mozilla switched from cvs to
mercurial starting with firefox 3.5.
...since the switch to
mercurial, the extensions live in separate repositories.
...loped any more last release: 0.8.5ff2 firefox 3.0 gecko 1.9.0 cvs, branch head not developed any more last release: 0.8.5ff3 firefox 3.5 gecko 1.9.1 xforms/schema-validation code does not build with firefox 3.5 any more not supported firefox 3.6 gecko 1.9.2 xforms/schema-validation code does not build with firefox 3.6 any more not developed any more last release: 0.8.6 firefox 4 gecko 2.0
mercurial, repositories mozilla-central xforms schema-validation mostly works upcoming 0.8.7 release if you have your first working firefox build, you can go on with building the xforms extension.
...starting with firefox 3.5, you need to do two more
mercurial checkouts: cd extensions hg clone http://hg.mozilla.org/xforms hg clone http://hg.mozilla.org/schema-validation that's it, you now have everything you need to get started.
Simple Instantbird build
windows build prerequisites gnu/linux build prerequisites mac os x build prerequisites tip: after completing setup for your os, and before you get the source, you can opt to add the progressextension to your
mercurial.ini (for windows) or .hgrc (for *nix / mac) file.
...see: configure
mercurial .hgrc file for progress extension.
... get the latest source code from mozilla's comm-central
mercurial code repository: hg clone http://hg.mozilla.org/comm-central then, get all the repositories it depends on.
...it is faster and more efficient to use
mercurial bundles instead the first time you fetch the complete repo.
Simple SeaMonkey build
this will accomodate visual studio 2013 community edition, the required sdks, the mozillabuild package, the
mercurial source repository and enough free disk space to compile.
... debian linux: # this one-liner should install all necessary build deps sudo aptitude install zip
mercurial libasound2-dev libcurl4-openssl-dev libnotify-dev libxt-dev libiw-dev libidl-dev mesa-common-dev autoconf2.13 yasm libgtk2.0-dev libdbus-1-dev libdbus-glib-1-dev python-dev libgstreamer0.10-dev libgstreamer-plugins-base0.10-dev libpulse-dev ubuntu linux # for ubuntu 12.04 lts (precise pangolin), replace the following line with: sudo apt-get build-dep thunderbird sudo apt-get build-dep seamonkey sudo apt-get install zip unzip
mercurial g++ make autoconf2.13 yasm libgtk2...
....0-dev libglib2.0-dev libdbus-1-dev libdbus-glib-1-dev libasound2-dev libcurl4-openssl-dev libnotify-dev libgstreamer0.10-dev libgstreamer-plugins-base0.10-dev libiw-dev libxt-dev mesa-common-dev libpulse-dev fedora linux centos rhel: sudo yum groupinstall 'development tools' 'development libraries' 'gnome software development' sudo yum install
mercurial autoconf213 glibc-static libstdc++-static yasm wireless-tools-devel mesa-libgl-devel alsa-lib-devel libxt-devel gstreamer-devel gstreamer-plugins-base-devel pulseaudio-libs-devel # 'development tools' is defunct in fedora 19 and above use the following sudo yum groupinstall 'c development tools and libraries' sudo yum group mark install "x software development" mac: install xcode tools.
... run these commands to install the other build tools: sudo port sync sudo port install
mercurial libidl autoconf213 yasm problems?
Python binding for NSS
mozilla source code management (scm) information on march 21, 2013 the nss project switched from using cvs as it's source code manager (scm) to
mercurial, also known as hg.
... all prior cvs information (including release tags) were imported into the new
mercurial repositories, as such there is no need to utilize the deprecated cvs repositories, use
mercurial instead.
... to check out python-nss source code from
mercurial do this: hg clone https://hg.mozilla.org/projects/python-nss the scm tags for various python-nss releases can be found in the release information.
... you may want to review the getting mozilla source code using
mercurial documentation for more information with working with
mercurial.
Getting SpiderMonkey source code
you can get the spidermonkey source code in gzipped form or directly from the
mercurial repository.
... getting the latest spidermonkey source code from
mercurial the
mercurial repository at https://hg.mozilla.org/mozilla-central/ hosts the latest spidermonkey sources.
...
mercurial is also known as hg.
... if you have problems with the instructions above, you can read the full details of using
mercurial to get mozilla code here.
Tamarin Tracing Build Documentation - Archive of obsolete content
supported, acceptance and performance tests automated in buildbot raw image (no os) armv5 supported, acceptance and performance tests not done linux (nokia n810) armv5 supported, acceptance and performance tests not done current build status the current tamarin tracing build status can be found at tamarin tracing build status getting the tamarin source the tamarin tracing source resides in
mercurial at tamarin tracing.
...documentation on how to setup a user repository http://developer.mozilla.org/en/publishing_
mercurial_clones.
...
mercurial repository: give the location of the repository that will be used for the build.
Eclipse CDT
is there a
mercurial plugin for eclipse?
... there is
mercurialeclipse, but probably most mozilla developers will just prefer to use the command line.
... if you think we need our own documentation on
mercurialeclipse, please consider adding a separate page for that tool since this page is already pretty long.
Obsolete Build Caveats and Tips
from source_code/
mercurial mozilla-2.0 (firefox 4.0) code for the firefox 4.0 (gecko 2.0) release lives in releases/mozilla-2.0.
...the default application is now firefox, so you can build firefox by simply doing configure && make (for standalone source tarballs) or make -f client.mk (for code from the
mercurial repository); this will build something roughly the same as the shipped version of firefox corresponding to the code you have.
... this setting is ignored by most mozilla project branches, which now use
mercurial instead of cvs for source control.
Bootstrapping a new locale
in mozilla, we use the the
mercurial version control system (hg) to help manage our localizations.
... installing
mercurial depending on your operating system, you will need to install the correct version of hg on your machine.
... clone the source code the next step is to download a copy of the source code to your local system, using
mercurial.
Localizing without a specialized tool
before we start, did you make sure to install
mercurial and confirm that you have set up the proper build environment on your local machine?
...assuming that you have installed
mercurial, issue the following command: $ hg clone http://hg.mozilla.org/releases/mozilla-1.9.2 this will pull the mozilla 1.9.2 sources from the remote repository and create a
mercurial clone in mozilla-1.9.2 inside your working directory.
...depending on your case, you can do it in one of the following ways: if no localization exists yet, create an empty folder and create a
mercurial repository in it: $ mkdir x-testing $ cd x-testing $ hg init if there is a bitbucket repository with localization files, you can pull from it.
Initial setup
hg (
mercurial)
mercurial is the revision control environment that houses the main mozilla source code as well as localized code for each official mozilla localization.
... hg (
mercurial) as noted above, we use
mercurial for maintaining mozilla source code and localized code.
...you can find everything you need to know about installing and configuring
mercurial for your localization work here.
Uplifting a localization from Central to Aurora
so, here are the
mercurial steps to reproduce.
...i use kdiff3; you may choose your own based on what you read at http://
mercurial.selenic.com/wiki/mergeprogram a clone of your central repo.
...because
mercurial suggests that you didn't.
How to Write and Land Nanojit Patches - Archive of obsolete content
for tracemonkey, use the "make update-nanojit" target (it requires that
mercurial's "convert" extension be enabled; add "hgext.convert =" to your .hgrc file under "[extensions]").
...if you ever want to "undo" revisions you copied from nanojit-central, you can backout copied revisions using the existing
mercurial "backout" command in your target repository.
Tamarin Build System Documentation - Archive of obsolete content
tamarin-redux
mercurial builds are displayed in the top 3 sections: compile, smoke, test sandbox builds are displayed in next 3 sections: sandbox compile, sandbox smoke, sandbox test tamarin-central is considered a "sandbox" and will appear under sandbox phase what are the build phases?
... create a user repository, instructions are https://developer.mozilla.org/en/publishing_
mercurial_clones go to the request a sandbox build page http://tamarin-builds.mozilla.org/build_trigger/requestbuild.cfm enter the repository url, revision number, email address, and description.
XML in Mozilla - Archive of obsolete content
the code for most the core xml can be found in the following directories on the mozilla
mercurial repository: content/xml/, parser/expat/ and parser/htmlparser/.
...most of the core xml test documents on the
mercurial repository are located in content/xml/tests.
Old Thunderbird build
get the latest source code from mozilla's comm-central
mercurial code repository: hg clone https://hg.mozilla.org/comm-central then, get all the repositories it depends on.
...it is faster and more efficient to use
mercurial bundles instead the first time you fetch the complete repo.
Simple Sunbird build
ubuntu linux: sudo apt-get build-dep sunbird sudo apt-get install
mercurial libasound2-dev libcurl4-openssl-dev libnotify-dev libiw-dev autoconf2.13 cvs fedora linux: sudo yum groupinstall 'development tools' 'development libraries' 'gnome software development' sudo yum install
mercurial autoconf213 glibc-static libstdc++-static yasm wireless-tools-devel mesa-libgl-devel mac: install xcode tools.
...run these commands to install the other build tools: sudo port sync sudo port install
mercurial libidl autoconf213 problems?
Simple Thunderbird build
get the latest mozilla source code from mozilla's mozilla-central
mercurial code repository, and check it out into a local directory source/ (or however you want to call it).
... then, get the latest thunderbird source code from mozilla's comm-central
mercurial code repository.
L10n Checks
once python is installed, the easiest way to install l10n checks (on mac or linux) is to just run: $ sudo easy_install -u l10n-checks or, if you're on windows: $ easy_install -u l10n-checks installation (development versions) l10n checks needs to be installed, and it requires that you have python and
mercurial installed on your machine.
... the easiest way is to just run: $ hg clone http://hg.mozilla.org/users/akalla_aviary.pl/silme-patched/ $ cd silme-patched/ $ sudo python setup.py install or, if you're on windows: $ hg clone http://hg.mozilla.org/users/akalla_aviary.pl/silme-patched/ $ cd silme-patched/ $ python setup.py install running it
mercurial source (source) mode l10n checks gathers the directories to compare from an ini file, usually found in $app/locales/l10n.ini.
Localization prerequisites
zip 2.3 (or higher)
mercurial 1.2 or higher recommended.
...let’s try our entry points: $ hg --version
mercurial distributed scm (version 1.3.1) copyright (c) 2005-2009 matt mackall <mpm@selenic.com> and others this is free software; see the source for copying conditions.
QA phase
note: you must have
mercurial configured before you begin.
...enter the following command: hg push http://hg.mozilla.org/l10n-central/x-testing
mercurial will connect to your repo and ask you to provide your account information (i.e., the username and the password).
Localization technical reviews
here is a detailed overview of what a technical review is and who it's meant for: a technical review: is performed as a qa measure on a revision pushed to a new locale's l10n aurora repo in
mercurial.
...once they are fixed, push your fix to your repo, attach it to the corresponding bug using the same
mercurial revision number as before, and then request another review.
What every Mozilla translator should know
going on, it's also a good idea to read the planet mozilla l10n when you have a problem use the above mailing lists the person in charge of the mozilla l10n is axel hecht (l10n at mozilla.com), pike on irc another interesting way of getting help is the irc channel #l10n at irc.mozilla.org useful tools the l10n dashboard pontoon narro translate toolkit koala 0.1 mozillatranslator
mercurial the hg is organized into several repositories, sometimes called branches.
...once you have made some changes in
mercurial, as soon as the next build is done you can check the tinderbox and see if something was wrong.
Build instructions
build instructions for recent versions (
mercurial) clone the nspr and nss repositories.
... check out nspr and nss: cvs co -r nspr_4_9_5_rtm nspr cvs co -r nss_3_14_2_rtm nss set environment variables as described in the
mercurial-based instructions.
jpm - Archive of obsolete content
using .jpmignore to ignore files using .jpmignore is similar to using .gitignore with git, .hgignore with
mercurial, or .npmignore with npm.
jpmignore - Archive of obsolete content
using .jpmignore to ignore files and directories using .jpmignore is similar to using .gitignore with git, .hgignore with
mercurial, or .npmignore with npm.
Index of archived content - Archive of obsolete content
e tests running tamarin acceptance tests running tamarin performance tests tamarin build system documentation tamarin releases tamarin-central rev 703:2cee46be9ce0 tamarin roadmap tamarin build documentation tamarin
mercurial commit hook the download manager schema the life of an html http request the new nsstring class implementation (1999) tracevis transforming xml with xslt:mozilla xslt transforming xml with xslt:the netscape xslt treehydra treehydra build instructions treehyd...
Merging TraceMonkey Repo - Archive of obsolete content
inspecting the files at those two changesets can be helpful: hg cat -c changeset filename once all the conflict markers are removed, you've performed the manual resolution, which you tell to
mercurial by running hg resolve -m filename.
Venkman - Archive of obsolete content
source code the source code for venkman may be found in
mercurial at the following url: http://hg.mozilla.org/venkman/summary community view mozilla forums...
Building XULRunner - Archive of obsolete content
for instance, in firefox 2.0.0.9 you will get : mozilla/5.0 (windows; u; windows nt 5.1; en-us; rv:1.8.1.9) gecko/20071025 firefox/2.0.0.9 therefore the xulrunner version for this firefox version is : 1.8.1.9 fetching sources from
mercurial as with all other mozilla products, one would fetch recent sources from
mercurial.
Configuring Build Options
adding the following line to your mozconfig allows you to change the objdir: mk_add_options moz_objdir=@topsrcdir@/obj-@config_guess@ it is a good idea to have your objdir name start with obj so that
mercurial ignores it.
ESLint
vcs hooks hooks are available for
mercurial & git, see using a vcs hook for more details.
Eclipse CDT Manual Setup
select "general > workspace" and select "refresh using native hooks or polling" and "refresh on access" to prevent eclipse giving you annoying "resource is out of sync" messages when files change from under it due to
mercurial or other external activity.
Reviewer Checklist
whitespace can be fixed easily in
mercurial using the checkfiles extension.
Translation phase
note: if you are starting a new localization and decide to use an offline tool for localizing mozilla applications, you will need to become familiar with using
mercurial (hg).
Localization sign-off reviews
once they are fixed, push your fix to your repo, attach it to the corresponding bug using the same
mercurial revision number as before, and then request another review.
Mozilla Development Tools
mozilla source code (
mercurial and cvs) "trunk" development for gecko 1.9.1/firefox 3.5 and beyond uses the
mercurial source code version control system.
NSPR build instructions
build the libraries build the test programs for example, # check out the source tree from
mercurial hg clone https://hg.mozilla.org/projects/nspr # create a build directory mkdir target.debug cd target.debug # run the configure script ../nspr/configure [optional configure options] # build the libraries gmake # build the test programs cd pr/tests gmake on mac os x, use make, which is gnu make.
Building NSS
get the source nss and nspr use
mercurial for source control like other mozilla projects.
Index
227 migration to hg the nspr, nss and related projects have stopped using mozilla'a cvs server, but have migrated to mozilla's hg (
mercurial) server.
JSS
as of april 6, 2018, jss has been migrated from
mercurial on mozilla to git on github.
JSS 4.4.0 Release Notes
bugs fixed in jss 4.4.0 this bugzilla query returns all the bugs fixed in nss 4.4.0: https://bugzilla.mozilla.org/buglist.cgi?product=jss&target_milestone=4.4&target_milestone=4.4&bug_status=resolved&resolution=fixed documentation build instructions for jss at https://hg.mozilla.org/projects/jss/file/tip/readme platform information you can check out the source from
mercurial via hg clone -r 055aa3ce8a61 https://hg.mozilla.org/projects/jss jss 4.4.0 works with openjdk versions 1.7 or higher we suggest the latest - openjdk 1.8.
NSS sources building testing
if you are a software developer and intend to contribute enhancements to nss, you should obtain the latest development snapshot of nss using
mercurial/hg (a distributed source control management tool).
Migration to HG
the nspr, nss and related projects have stopped using mozilla'a cvs server, but have migrated to mozilla's hg (
mercurial) server.
Index
at a high level, there are three issues to be aware of: 8 getting spidermonkey source code guide, spidermonkey you can get the spidermonkey source code in gzipped form or directly from the
mercurial repository.
SpiderMonkey 1.8.5
spidermonkey 1.8.5 includes a new configure-based build system, introduced shortly after active development on the engine moved from cvs to
mercurial.
Mozilla technologies
these services include:viewing and searching mozilla source code onlinesource code for all mozilla projects hosted in the
mercurial repositories can be searched and viewed online using searchfox, a fast indexed search engine that runs on aws.xml extrasthe xml extras module contains several features that allow developers to treat xml as data i.e.
Using the Mozilla source server
couple of simple steps you can also have the source code served to you for debugging without a local build what you'll need windbg or visual studio (note: express editions will not work, but windbg is a free download) a nightly build that was created after april 15, 2008; go to the /pub/firefox/nightly/latest-mozilla-central/ folder and grab the installer for builds predating the switch to
mercurial, you'll need cvs.exe, added to your path (the cvs.exe from mozillabuild has problems, use this one instead) note: do not use the cvs from mozillabuild, it will not work!
Firefox user agent string reference - HTTP
firefox os version number gecko version number 1.0.1 18.0 1.1 18.1 1.2 26.0 1.3 28.0 1.4 30.0 2.0 32.0 2.1 34.0 2.2 37 2.5 44 it's easy to find the correspondences by looking at the
mercurial repository names: repositories starting by mozilla-b2g are the release repositories for firefox os, and have both firefox os and gecko versions in their names.