Difference between revisions of "Talk:LANGGE"

From IHO Nautical Information Processing Working Group
Jump to navigation Jump to search
(New page: ~~~~: Language codes for use in multi-language datasets. See INFOML and Talk:INFOML.)
 
 
(4 intermediate revisions by one other user not shown)
Line 1: Line 1:
 
[[User:Rmm|raphael]] 00:12, 25 August 2009 (UTC): Language codes for use in multi-language datasets. See [[INFOML]] and [[Talk:INFOML]].
 
[[User:Rmm|raphael]] 00:12, 25 August 2009 (UTC): Language codes for use in multi-language datasets. See [[INFOML]] and [[Talk:INFOML]].
 +
 +
[[User:DavidAcland|DavidAcland]] 11:01, 12 August 2011 (UTC) Confusingly the Alpha-2 code is the older standard ISO 639-1.
 +
 +
[[User:Rmm|raphael]] 16:40, 2 December 2011 (UTC): I suggest specifying the 2002 version of ISO 639-1. This is based on the general principle (my own opinion, I do not know whether this is a S-100 modeling convention) that lists of allowed values should be frozen and updates to the list result in a revised version number; this to simplify update management for application software.  (Not that it is likely to have any practical effect for this particular case.)
 +
 +
[[User:DavidAcland|DavidAcland]] 15:22, 5 December 2011 (UTC) Thank you. I have changed the page to "2002".
 +
 +
[[User:Jens|jens]] 06:49, 15 December 2011 (UTC) I agree. But, I recall a SNPWG discussion that the language problem was planned to be solved by TSMAD. We should avoid to develop a second track on that.

Latest revision as of 06:49, 15 December 2011

raphael 00:12, 25 August 2009 (UTC): Language codes for use in multi-language datasets. See INFOML and Talk:INFOML.

DavidAcland 11:01, 12 August 2011 (UTC) Confusingly the Alpha-2 code is the older standard ISO 639-1.

raphael 16:40, 2 December 2011 (UTC): I suggest specifying the 2002 version of ISO 639-1. This is based on the general principle (my own opinion, I do not know whether this is a S-100 modeling convention) that lists of allowed values should be frozen and updates to the list result in a revised version number; this to simplify update management for application software. (Not that it is likely to have any practical effect for this particular case.)

DavidAcland 15:22, 5 December 2011 (UTC) Thank you. I have changed the page to "2002".

jens 06:49, 15 December 2011 (UTC) I agree. But, I recall a SNPWG discussion that the language problem was planned to be solved by TSMAD. We should avoid to develop a second track on that.