X-Git-Url: http://source.jalview.org/gitweb/?a=blobdiff_plain;f=help%2Fhtml%2FwhatsNew.html;h=d1d141d30b133f0a400e7fb369ebe9cce029c4d5;hb=47fd498a6fe7d2e3350a9e87c526bf1e59d00be5;hp=a016a3514c48a7c2bd43d6f5df8e86690504f265;hpb=3c9a109fe89504b4713bfaf612275edc8c07e433;p=jalview.git diff --git a/help/html/whatsNew.html b/help/html/whatsNew.html index a016a35..d1d141d 100755 --- a/help/html/whatsNew.html +++ b/help/html/whatsNew.html @@ -1,52 +1,78 @@ + --> What's new ? -

- What's new ?
Jalview 2.8.1 includes a range of new features developed in the last 12 months.
As usual you can find the - highlights below, and the comprehensive list is given in the Jalview 2.8.1 Release Notes. -

- Internationalisation -

- In August 2013, David Róldan-Martinez took on the task of - internationalising Jalview's user interface. He also recruited Sara - Hernández Díaz and Laura Ferrandis Martinez who created Jalview's - first spanish user interface translation.
If you notice any - problems, or would like to help translate Jalview's user interface - into other languages, head over to issues.jalview.org - and put in a feature request describing the translations you can - provide to the i18n - component.
- David has also put together some documentation about getting started with i18n translations -

- Enhancements and new features - - Bug fixes - +

+ What's new in Jalview 2.10.1 ? +

+

+ Jalview 2.10.1 was released on 29th November 2016. Full details are + in the Jalview 2.10.1 + Release Notes, but the highlights are below. This is also the + first release to include contributions from Kira Mourão, who + joined Jalview's core development team in October 2016. +

+ + +

+ Warning dialog about updating + your configured URL links
In the desktop prior to Jalview + 2.10.1, the only way to configure custom links for a particular + database cross-reference for a sequence was to give it a name that exactly + matched the database source, and a regular expression for filtering + out any spurious matches generated when the custom linked was tested + against the Sequence's ID string. Since the introduction of the + $DB_ACCESSION$ token, however, $SEQUENCE_ID$ will not be used for + database cross-reference accession strings, and if you have custom + links configured, Jalview will raise a warning message so let you + know that you may need to update your links to use $DB_ACCESSION$. +